P
Patrick Philippot
Hi,
This is an old bug showing up again. Although the official solution
involves reinstalling the framework after manipulating the registry with the
installer cleanup tool, there's a much simpler way to fix this:
1. Instead of using Windows Update, download the KB928366 package from here:
http://www.microsoft.com/downloads/...CD-C715-4F05-A01F-0455D2D9EBFB&displaylang=en
Do not install yet.
2. Download the .Net framework 1.1 redistributable package from here
http://www.microsoft.com/downloads/...FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3
3. Use Winzip or a similar utility to unpack dotnetfx.exe in a folder of
your choice. You should get the following files:
netfx.msi
install.exe
InstMsi.exe
InstMsiW.exe
netfx1.cab
4. Launch the KB928366 installer. It will soon complain that it can find the
installation CD-ROM (don't ask me why). Browse to the folder where you
unpacked the dotnetfx files.
That's it.
This procedure can be applied to any similar situation regarding .Net
framework updates. I'm using it since years (that is, since this Windows
Update bug exists).
Good luck.
This is an old bug showing up again. Although the official solution
involves reinstalling the framework after manipulating the registry with the
installer cleanup tool, there's a much simpler way to fix this:
1. Instead of using Windows Update, download the KB928366 package from here:
http://www.microsoft.com/downloads/...CD-C715-4F05-A01F-0455D2D9EBFB&displaylang=en
Do not install yet.
2. Download the .Net framework 1.1 redistributable package from here
http://www.microsoft.com/downloads/...FamilyID=262d25e3-f589-4842-8157-034d1e7cf3a3
3. Use Winzip or a similar utility to unpack dotnetfx.exe in a folder of
your choice. You should get the following files:
netfx.msi
install.exe
InstMsi.exe
InstMsiW.exe
netfx1.cab
4. Launch the KB928366 installer. It will soon complain that it can find the
installation CD-ROM (don't ask me why). Browse to the folder where you
unpacked the dotnetfx files.
That's it.
This procedure can be applied to any similar situation regarding .Net
framework updates. I'm using it since years (that is, since this Windows
Update bug exists).
Good luck.