Decompression errors on Windows 8

[arrigob]

Hi There,

I have a client update installer that workstations run to update their local client software. My installer simply copies files from the server driver to the local disk.

This installer is on 120+ customers. Customers running Windows 7 or XP never have an issue. Customers running Windows 8 receives decompression errors on half of the workstations in office. I have tried running it as administrator and turning off antivirus but it still happens. Have you seen anything similar to this before? Thanks,

Brandon

[linder]

Brandon,

This is not related to a SetupBuilder issue. If you can provide the error code (I think it's not really a decompression error but a file access / shared file error returned from the decompression library) then I can tell you exactly what causes this in your project. BTW, make sure that you code-sign your application files and installer executable. And enable the archive integrity check to make sure that they have received/downloaded the complete install file. You can also send your .sb8 project file and we'll review it for you to see if you are doing something wrong.

Friedrich

[linder]

BTW, here are some interesting "decompression error" threads:

http://www.lindersoft.com/forums/showthread.php?p=69313
http://www.lindersoft.com/forums/showthread.php?p=68845
http://www.lindersoft.com/forums/showthread.php?p=65597
http://www.lindersoft.com/forums/showthread.php?p=62330
http://www.lindersoft.com/forums/showthread.php?t=32104

Friedrich

[Unregistered]

Hi Friedrich,

Thanks for the information! I did figure my issue out shortly after I created the thread. My issue ended up being caused by my installer trying to place a file in the Windows folder on a Windows 8 machine. Once I stopped trying to place the file into the Windows folder, decompression errors stopped. I noticed it always referenced the same file in my installer for the decompression error and removed it. So apparently Windows 8 does not like installing files into the Windows directory, or at least not for me. I run as invoker, would that be why? Anyways, thanks for your help as always,

Brandon

[linder]

Brandon,

Yes, you can't write to protected Windows areas (e.g. the "Program Files" folder tree, the Windows folder tree, the HKEY_LOCAL_MACHINE registry branch, etc.) from a non-elevated running "asInvoker" manifested application. In other words, you can only do "per-user" operations from your install, not any "per-machine" task. You can't register OCX files, you can't write to the standard "Program Files" folder or the Windows folder, you can't add machine-wide uninstall entries, etc. You need a standard "requireAdministrator" manifested setup to handle this.

Friedrich