Could not install .NET Framework 2.0

kcchenkd · Post by **kcchenkd** » Fri Apr 21, 2006 1:27 pm

Hi

When we use InstallAware to install our application which required .NET Framework 2.0. , on a clean machine(Window XP Profession Version 2002 Service Pack 2). Installaware detects that system need to install .NET Framework 2.0, then when we try to install it, it pop up a error message:
".NET Framework 2.0 could not be installed. Please use Window Update to manually install this update on your system."

Please Help! Thanks

Gizm0 · Post by **Gizm0** » Fri Apr 21, 2006 5:35 pm

Can you try runing the setup.exe by hand and tells us what the message says exactly?You can locate the setup.exe in the Uncompressed folder->Data->DotNet Framework 2.0
I guess something is missing and you get that error message..

MichaelNesmith · Post by **MichaelNesmith** » Sat Apr 22, 2006 4:59 am

Make sure you are not unchecking any required prereqs...uncheck and recheck the .NET 2.0 item, this way the IDE will re-check any dependencies.

MarkRichards · Post by **MarkRichards** » Wed Apr 26, 2006 8:48 am

I'm having a similar problem installing MSI 3.0 on a clean WinXP machine.

"Windows Installer 3.0 could not be installed. Please use Windows Update to manually install this update on your system."

It's critical that I understand the precise cause of this problem. Should I engage additional logging within InstallAware to do this?

- MR

MarkRichards · Post by **MarkRichards** » Wed Apr 26, 2006 9:05 am

I see another problem here that I'd like to get some feedback on.

After the installation of MSI 3.0 fails, as per my message above, the machine must reboot in order to proceed with any additional MSI installations. This means that if the user immediately fires up Windows Update to download MSI 3.0 manually (as they were instructed), it will fail because they haven't yet rebooted.

So, my question is this: why is a restart necessary when the installation actually failed? Shouldn't InstallAware essentially "back out" the changes and not require a reboot at that point?

Further, if a reboot is required after a failed pre-requisite, then InstallAware should prompt for it in the error message that I posted earlier. This would avoid a certain degree of confusion, in my opinion.

- MR

MichaelNesmith · Post by **MichaelNesmith** » Wed Apr 26, 2006 2:27 pm

What you should do is run the stand alone MSI 3.0 installer and see what the cause of failure is. I don't believe a reboot is necessary after a failed prereq install but you can add a reboot command to your script if you believe that will help.

GordonS · Post by **GordonS** » Fri Jun 15, 2007 10:09 am

I too have twice now had the message:

".NET Framework 2.0 could not be installed. Please use Window Update to manually install this update on your system."

In both cases I ended up doing or being asked to do a system restart and in both cases after a fairly long wait (a few minutes on old-ish PCs), the installation completed, apparently successfully, without the PC actually restarting. I say "apparently successfuly", because I haven't yet had an opportunity to prove that everything works as expected.

I don't presently have any more information than that.

This is InstallAware Express Version 6.6 Build istambul_rtm.060107

GordonS · Post by **GordonS** » Wed Jun 20, 2007 5:42 am

This is an early attempt at this install and the problem may be happening on the first install attempt on XP.

I now have a third instance.

I've suggested Run-as admnistrator, but I'm not sure that anyone has yet done that, because the Restart happens first.

ekramer17 · Post by **ekramer17** » Thu Jun 28, 2007 9:18 am

Has anyone found an answer to this problem? I installed the plug-in update but am still experiencing an error when trying to install the .NET Framework 2.0.

GordonS · Post by **GordonS** » Thu Jul 12, 2007 9:16 am

GordonS wrote:....the problem may be happening on the first install attempt on XP.

This isn't just on a first install.

A system today installed fine the first time and gave the problem the second time. The second install was just straight over the first one. No uninstall or other cleanup.

These are only instances I've seen here. I don't know how many times it may have happened in the field.