You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so , join our community today!

If you have any problems with the registration process or your account login, please contact us.

microsoft.public.windowsupdate

{This message was prepared in Sep 2007 and kept apart in hope of improvement from MS. Short of any actual cure I finally and reluctantly post it, after updating it}.

A large part of users have apparently been hit for months with the never-fixed bug in the installation, update, uninstallation, of various items (versions, updates, patches) in the dotNetFW ("Microsoft .NET Framework"). Obviously there is an accumulation of problems in the teams in charge of dotNetFW, MSI (Microsoft Installer), MU (Microsoft Update), NGs (NewsGroups), who apparently have become too self-confident, static, formalist, administrative and complication-addict; and above all, in the management over them, who seems become unable to resolve inter-team disputes, whatever their parts of statism or personal rivalries.

Instead of the habit (now a majority) in these newsgroups of recklessly posting myriad-times the same boilerplate unhelpful "answers", I am trying (like in good old MS NGs) to post just once, just in one case (mine - probably similar to many), but complete enough to be understandable without too much ambiguity.

D)) Finally, what MS (altogether staff, "volunteers", and various MS aficionados) would like me to do is:

- uninstalling 7 items, with all the reboots and other time losses involved, and all the according risks (what if one item then fails to reinstall? etc...);
- then complete the uninstall with a particular tool;
- then reinstall all the items
- then probably redo it all using another different particular tool
- then most probably check that the Microsoft Update of dotNetFW has NOT been fixed - but that this failure doesn't impair any function of your computing in the real world.

All this chore for which result? Just be able to suffer the next bug in the dotNetFW×MSI×MU×NGs combination and their 4 mismanaged complication-addict teams?

I checked the C:\WINDOWS\WindowsUpdate.log and tried msiexec with the "{x}" number but it did not work. It complained that it could not find the package.

I found and clicked on:
C:\WINDOWS\SoftwareDistribution\Download\Install\n etfx30-kb932471-x86.exe
and it produced this popup useful error message:

Windows Installer

/!\ The upgrade patch cannot be installed by the Windows
Installer service because the program to be upgraded
may be missing, or the upgrade patch may update a
different version of the program. Verify that the program
to be upgraded exists on your computer and that you
have the correct upgrade patch.

I obtained the file using the Microsoft Automatic Updates website so it is not my fault if it tries to download and install an incorrect update.