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
- :
- The installation package could not be opened.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 01, 2009
04:16 PM
The installation package could not be opened.
I have a small number of users who get the following error message downloading using our Web Install.
1st. The publisher could not be verified are you sure you want to run this MSI
2nd. After they click yes. They get
The installation package could not be opened. Conatct the application vendor to verify that this is a valid Windows installer package.
And before anyone asks, YES THE MSI IS SIGNED. I grabbed the file directly from the web server and it I can verify the signiture and works correctly everywhere I test it. Most people have no problem downloading it, its only a handful of people.
I tried different security settings and different vesions of windows installer.
1st. The publisher could not be verified are you sure you want to run this MSI
2nd. After they click yes. They get
The installation package could not be opened. Conatct the application vendor to verify that this is a valid Windows installer package.
And before anyone asks, YES THE MSI IS SIGNED. I grabbed the file directly from the web server and it I can verify the signiture and works correctly everywhere I test it. Most people have no problem downloading it, its only a handful of people.
I tried different security settings and different vesions of windows installer.
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Oct 03, 2009
08:46 PM
Hate to reply to my own thread, but looks like it may have been a problem on the web server