We have a Windows Service that talks to the cloud and knows when an update is available. When an update is available the Service invokes update.exe with the proper command line to update itself. For the most part this works, but we have a handful of customers in which this does not work.
My investigation first revealed that AVG classified update.exe as a threat and threw it into the vault. Sigh. I restored it and tried again but still no luck (both with AVG enabled and disabled). update.exe just sits in the task manager seemingly doing nothing. Does update.exe emit a log so I can check where it's stuck?
I then took the command line our service issues to update.exe and it works on the command line. Is there are reason why service's invocation of update.exe doesn't work? The Windows account type is administrator.
OS: Windows 7 Home Premium 64-bit SP1
AVG: 2012.0.2221 (LinkScanner version: 1390)
FOLLOW US
Get the latest news in Application Packaging