-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error 1603 when installing Prey node.js on Windows (HS:node-1603) #58
Comments
Windows 7
|
Windows 8.1
|
Windows XP
|
@fanuneza have you received any extra reports related to this issue or was it v1.3.2 specific? |
It's still happening. This log was sent by a user 14 minutes ago:
|
I'm seeing this as well. Same result with install location of prey-windows-1.3.6-x64.exe
|
I'm not sure, but this could be caused by changing the default |
I ran into this both with the default path and with a different one @fanuneza |
Crap. This bug is the most difficult to replicate that I've seen on Prey. We're still trying to figure out what's wrong 😐 |
Well, I have a machine with the issue if you have any theories you'd like me to try. |
I have a log from my most recent attempt on a TW700 where I took all the defaults, including the install path (C:\Windows\Prey) @fanuneza I have to wonder if there is some commonality in the devices the install is failing on. TW700 looks to me like it is running some non-standard install of Windows 8.1 - but I don't know enough to say anything more... except that they cram it into quite a small System drive. [quote] MSI (s) (9C:F4) [11:47:08:851]: Windows Installer reconfigured the product. Product Name: Prey Anti-Theft. Product Version: 1.3.6. Product Language: 1033. Manufacturer: Prey, Inc.. Reconfiguration success or error status: 1603. |
Thanks for the log, @PeteCress! For testing purposes, can you install Prey 0.6.4? |
Done. Install went a-ok, threw a couple of "Problems..." dialogs when connecting to my Prey account, but eventually connected. I used prey-0.6.4-win.exe, and installed to D:\Prey - because C: is low on space. You want C:, I will uninstall and reinstall to C:. Only .log file I could find was empty, or I would post it. Logged into the Prey account, sent an Alarm and a test Text Message, but they have not hit the TW700 yet. "Actions will be executed once the device reconnects to the Prey servers." I'll reboot the TW700, give it an hour and report back. |
It has not been an hour yet... but I did re-boot and my suspicion is that Prey is either not running for, for some reason, is not connecting to the server. OTOH, the Prey account page says "Last seen 32 minutes ago", so something happened... What should I look for to confirm that Prey is running? Processes? Services? Something else. |
I have the same problem with the 1.3.6 installer, Windows 7 x64. I installed the 0.6.4 version and it works like a champ. I checked my devices on the web page and it came up. |
@logankoester @PeteCress @erikburd Could you please try these instructions for unattended installs? First the same EXE you're already trying, and if that fails, please try the MSI installers available here. Do any of those methods work? Thanks! |
I already tried the x86 and x64 MSI and EXE installers for 1.3.6 and they bombed. Same problem. I'll try the unattended install later and let you know. |
Tried the unattended install, still fails with the same error. |
I was having this problem while attempting to install it in c:\program files\prey but then tried to install it on c:\windows\prey and it worked fine... |
Interesting - now that you mention that the old version was installed to C:\Prey (default) while the new one was installed elsewhere. I'll try that later. The space shouldn't be throwing it off but then again who knows? |
According to the Microsoft support website, these are the reasons why you might receive the error.
Can you guys please verify if any of these is true in your case? |
@lemavri - none of those three apply on my system. Good thinking though. I'm trying something else here on my end. Will report soon. |
Doing some "googling" I found that the error code 1603 is quite generic and can mean a lot of things, like:
Please, can you try running the Microsoft Fix-it tool ? |
Here's something amusing. I used the 1.3.6 x64 MSI installer. The "default" folder is C:\Windows\Prey. I changed it to "C:\Prey", which was the previous default. Good news - now the installer runs just fine and finishes without any errors
|
Terrific feedback, @erikburd! Hopefully @lemavri will get something from it. For now:
|
For item 2 - those files were installed with the 1.3.6 installer. Before I did the install, I made sure that I cleaned everything out, rebooted, and double checked that no existing files were there. As for items 1 and 3 - that's fine. I'm just used to the old 0.6.4 installer. :) |
I just started working on this bug. According to different log files, it seems that the problem is related to the installation of the CronService service and perhaps there's also a relation on where Prey is installed. I'll check the installer code and also run some tests to try to replicate the issue. |
Windows 10 x64 error log: === Logging started: 24.08.2015 11:19:15 === MSI (s) (68:94) [11:19:43:216]: Установщик Windows выполнил установку продукта. Продукт: Prey Anti-Theft. Версия: 1.4.1. Язык: 1033. Изготовитель: Prey, Inc.. Установка завершена с состоянием: 1603. === Logging stopped: 24.08.2015 11:19:43 === |
Cron Service for Prey marked as hight risky as malware. |
Hey @stepProgrammer, thanks for your report. It might very well be the cause for this issue. What AV software are you using?. |
Doctor Web. This is not problem of my antivirus. Installer for Cron Service placed to global malware database. But disable antivirus software is interesting idea. I try it. Now. I think that we have workaround to temporarily solve the problem. Stay turned. |
Nothing, but I find this in prey.log: ████████████████ ████████████████ ████████████████ ██ ██ PREY 1.4.1 spreads its wings! notice Wed, 14 Oct 2015 15:36:23 GMT [updater] New version found: 1.4.2
I tried 1.4.2. Now. |
Which version Node.js are you using for development? My version is 4.0.0 |
Check the event viewer. In Windows logs under Application check the recent error. If it contains this error Then the problem can be easily fixed. hit enter and it will give you the success message |
On Windows x64 10 Russian I've only succeded with 0.9.6.2 x64 |
Dear Developers, can you please provide MSI install script as it was in pre 1.0 version's source. I'd like to find out the trouble. |
I've currently succeded with 0.9.6.2 at Win 10 russian, but LOCK won't work. |
Hello @r3code. Here you can find the Also, there's a fix for the lock in windows 10 that will be included in the 1.4.3 release being launched later this week. @stepProgrammer I'm using 0.12.7 for now. |
@lemavri I was poiting to the MSI source code not the MSI binarry installer. There is no MSI script which builds the installer binary in the source of prey-node-client. It was here https://github.com/prey/prey-node-client/releases/tag/v1.0.0 in the folder dist/windows. |
Any action on this lately? The 0.6.4 installer is no longer available. I would love to get a version of Prey, any version, installed. |
Confirmed, same issue on windows 10 Russian x64. |
Guys I've found the sollution, try to change local language from Russian to English (USA) and there it is! Works fine for me. Change the language back to Russian after the installation. |
@serge555 What do you mean by "local language"? Change keyboard language or change system wide language with MUI? |
@r3code language for programs that not support unicode codepage. Панель управления - Язык и региональные стандарты - Дополнительно - Язык программ не поддерживающих юникод - Изменить язык системы. |
Fixed on new Prey version 1.6.2 :) |
I don't know why this has been closed. With v1.6.3, I am still getting an error if you choose a directory other than "C:\Prey". It not says "Something went wrong when installing Prey. Please make sure no other installations are ongoing." Error log:
It's the same "CAQuietExec: Error 0x80070002" error. |
Hi @electronicsguy, I just re-open the issue. This is the one I've been able to replicate and solved:
I'm pretty sure that the others are in the same spot, so i'm gonna be trying to solved it. To do that i might need some help trying out some other windows installation packages. So I hope I can count with your help and other users with this problem. |
Sure. Let me know what you need. |
Hi just thought I'd add to this thread-I was getting the 1603 error code when trying to install Prey on my new Win 10 Pro laptop-but I changed the default install dir from \Windows\Prey to \Program Files\Prey. After reading this thread I switched it back to \Windows\Prey and it installed fine. So I'd venture to say it's some permissions issue with changing the default install dir maybe? HTH! |
Hi @keltraine, thank you for let us know, along the way I detected several reason for this error and I've been able to fix couple of them but it's still there for some users. Gonna test the case you're telling us and try to fix it if I'm able to replicate it. Thanks again :) |
Several users have reported errors during the installation of Prey for Windows. The
prey-install.log
file located in thetemp
folder outputs this on every case:v1.3.2 on Windows 8.1
According to Microsoft,
This is not the case for any of the affected users. It also affects Windows 7, both in the 64 and 32 bits versions.
The text was updated successfully, but these errors were encountered: