This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- .Net Service installation fails after installation of Windows 7 hotfix
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎May 12, 2015
05:28 AM
.Net Service installation fails after installation of Windows 7 hotfix
We have an MSI that installs two .Net Services. This installs fine most of the time but one of our customers is telling us that after installation of a set of Microsoft hotfixes for Windows 7, if they install our MSI, the .Net Services do not get installed. I know it is a long shot but does anyone know of any Microsoft hotfixes (for Windows 7 x64) that might be upsetting msiexec or causing our services not to install?
Just thought I'd ask. the customer has given me a list of about 50 different patches and he is not sure which one is causing the problem.
Just thought I'd ask. the customer has given me a list of about 50 different patches and he is not sure which one is causing the problem.
(2) Replies
‎May 12, 2015
11:19 AM
There were a couple of 'Updates' back in the spring of 2014 that were causing problems for our installer. Ironically our install would fail when running Microsoft's C++ 2005 runtime redistributable.
We had to go through and ask customers to uninstall the update, run setup, and then reinstall the update. The updates touched something for security in the MSI service.
We do not get any calls on this any longer so I suspect that Microsoft had fixed the problem.
I forget the exact KB number for our particular issue.
We had to go through and ask customers to uninstall the update, run setup, and then reinstall the update. The updates touched something for security in the MSI service.
We do not get any calls on this any longer so I suspect that Microsoft had fixed the problem.
I forget the exact KB number for our particular issue.