Home » .Net FrameworkRSS

Preventing the "This program might not have installed correctly" warning when (not) installing .NET

Hi all,

I am trying to create an installer using Installshield 2009 Pro, which needs to include .NET Framework 3.5 SP1 (the full version or the web downloader, depending on the deployment method). I am using the built-in prerequisites and everything works fine on XP and Vista.

However, on Windows7 the installation causes the "This program might not have installed correctly" warning to appear in installer versions that include the .NET Framework prerequisite; I need to prevent this.

I understand that Windows7 already includes .NET Framework 3.5 SP1 (and that the .NET setup does not support Windows7), however I cannot find a way to prevent the prerequisite from attempting to install on that OS (the built-in checks seem not to prevent it, either). Either that, or the failure to install is what actually prompts the error message in the first place.

So can anybody offer any guidance on how to prevent this warning on Windows7? So far the only choice I can think of is to have a separate installer for Windows7 that does not include the .NET prerequisite, however because it is a requirement for the CD version to include the full .NET installer rather than just the downloader, space is already at a premium.

Thanks in advance.
 

6 Answers Found

 

Answer 1

Hi Zild,

Thank you for your post.

As you mentioned, for Windows 7, .NET Framework 3.5 with SP1 is shipped with it as one of OS component.
For .NET Framework 3.5 with SP1, it includes .NET 2.0 with SP2 and .NET 3.0 with SP2 as prerequisite.
This means, you have the .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 plus a few post 3.5 SP1 bug fixes on Windows 7. They are OS components. We don't need to manually install it.

For your concern, could you please check whether this scenario will happen if you turn on the windows feature of .NET Framework 3.5.1 before you try to install the installer  using Installshield 2009 Pro?
Please go to Control Panel -> Programs and Features -> Turn Windows features on or off -> Check the box next to Microsoft .NET Framework 3.5.1.

After the windows feature has been turned on, it means that .NET Framework 3.5 with SP1 is well installed  on Windows 7.
If the problem still exists, could you please help me to check whether this scenario will happen on other Windows 7 machine?
This would be helpful to eliminate some possible cause of this machine specific.

For more information on this warning  message, please check: http://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx

Hope this helps! If you have any concern, please feel free to let me know.

Best regards,
Yichun Chen
 

Answer 2

Thank you for the advice. I have now tried enabling the .NET Framework 3.5 SP1 component prior to installation on three different PCs, however it makes no difference.

Do you have any other suggestions? I realise it is as much an InstallShield problem as a .NET installer  problem - the former should know not to try to install the latter, but the latter should ideally not give this error.
 

Answer 3

Hi Zild,

Thank you for your post.

Thank you for the advice. I have now tried enabling the .NET Framework 3.5 SP1 component prior to installation on three different PCs, however it makes no difference.

Do you have any other suggestions? I realise it is as much an InstallShield problem as a .NET installer  problem - the former should know not to try to install the latter, but the latter should ideally not give this error.

I don't have InstallShield installer on my machine so I cannot re-produce the scenario that you came across. Sorry for that!

When I install some .NET 3.5 application or software on my Windows 7 machine, it seems that I have never noticed such a kind of warning  message. So, I would suspect that your issue seems to incline to InstallShield product.

Since .NET Framework 3.5 has been well installed  but the problem still exists, you might try InstallShield forum to get more useful help.

Thank you for your understanding.

Hope this helps! If you have any concern, please feel free to let me know.

Best regards,
Yichun Chen

(This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.)

Please remember to mark the replies as answers if they help and unmark them if they provide no help.
Welcome to the All-In-One Code Framework! If you have any feedback, please tell us.
 

Answer 4

Thank you - I did post the question to their forums yesterday but the people at InstallShield have never proven to be particularly helpful!

I do agree the problem is really an InstallShield issue (I suspect it may even be intentional to force users to upgrade to the latest version); the .NET Framework 3.5 SP1 installation is quite clear about what versions of Windows it will work with and I fully understand Windows 7 not being one of them.

While I do not expect to resolve the issue here, for the sake of completeness and clarity I would like to point out the following: If you attempt to install .NET Framework 3.5 SP1 on its own under Windows 7 you get the issue I have described. It would be handy if the installation were updated to support Windows 7 (i.e. not install anything but not give the warning  message), but then why should Microsoft have to work to counter the deficiencies of third party software? ;)

Thanks again for the help.
 

Answer 5

Hi Zild,

Thank you for your reply.

To be honest, I'm not quite sure the reason.

Microsoft continues to improve the product as well as the third party software. The goal is the same - to provide better user experience to use the products. I think it would be improved in the future. :)

Have a nice day!

Best regards,
Yichun Chen
 

Answer 6

Thank you - I did post the question to their forums yesterday but the people at InstallShield have never proven to be particularly helpful!

I do agree the problem is really an InstallShield issue (I suspect it may even be intentional to force users to upgrade to the latest version); the .NET Framework 3.5 SP1 installation is quite clear about what versions of Windows it will work with and I fully understand Windows 7 not being one of them.

While I do not expect to resolve the issue here, for the sake of completeness and clarity I would like to point out the following: If you attempt to install .NET Framewrk 3.5 SP1 on its own under Windows 7 you get the issue I have described. It would be handy if the installation were updated to support Windows 7 (i.e. not install anything but not give the warning  message), but then why should Microsoft have to work to counter the deficiencies of third party software? ;)

Thanks again for the help.

It's good for reference, Thanks for your analysis! I understand this part.
 
 
 

<< Previous      Next >>


Microsoft   |   Windows   |   Visual Studio   |   Follow us on Twitter