“What the security bulletin doesn’t say is that the change in Windows Installer repair operations means that application repair attempts will be met with a User Account Control credential window each time. However, the credentials required are administrator access.”
– Bug or Feature? KB2918614 Alters Windows Installer Behavior
Should your application install use Active Setup, to say, personal per-user settings, then this MS14-049 security patch causes a UAC prompt as well.
The current workaround, courtesy of happysccm, is as follows:
- Uninstall the application and reinstall it with the security update installed. (sourcehash file generated with security update)
- Manually copy the sourcehash file to c:\windows\installer folder. As the sourcehash file is generated based on the application files, the sourcehash file generated on computer A can be used on computer B.
Not scalable if, say, you have 500 packaged applications deployed to customers.
Related posts:
My user account is trying to logon another system and I don’t know why!
‘Plan now to eliminate “power users”; from your domains’ – or face the consequences.
"This advertised application will not be installed because it might be unsafe. Contact your administrator …"
Powered by YARPP.