Windows Installer CleanUp Utility - Not available anymore! and now 0x643 what?

Question

Hi All: 

Have you noticed that this tool (msicuu2.exe) is not available for download anymore? 

I understand that MS discontinued the tool without replacing it with its corresponding substitute (one of the new "Fix It" solutions). Therefore, there are (at least as of todate) still some non-updated KB's (KB923100 for example) indicating it as a solution to a particular error case and showing broken or inoperative links to the pulled out tool.

I could only find one article that has been recently (June 29) reviewed in this respect (KB290301). I would point out however, that more than a "review", this KB has been completely "changed", because its original title was: "Description of the Windows Installer CleanUp Utility" with the description, etc.. and a link to the msicuu2.exe file, while it is now: "How do I uninstall Office 2003, Office 2007 or Office 2010 suites if I cannot uninstall it from Control Panel?"  referring to Office only and including its new "Fix it" solution buttons to uninstall Office only.  Quite a difference, isn't it?

The only mention to the removed tool is a NOTICE at the first paragraph of the article which reads as follows:

"This article previously contained a link to the Windows Installer Cleanup utility (MSICUU2.exe). If you were directed to this article to solve a problem installing a product other than Microsoft Office, please contact your software manufacturer for installation support on the product.

While the Windows Installer Cleanup utility resolved some installation problems, it sometimes damaged other components installed on the computer. Because of this, the tool has been removed from the Microsoft Download Center. The Fix it Solutions in this article provide the ability to fully remove Office 2003, 2007 and 2010 suites without damaging other Windows components."...

Such a small paragraph included into a totally different subject matter article, appears to be sufficient to MS? As it seems it will take them longer to develop individual "Fix it Solutions" to replace wherever the removed tool might have been used before, suppose there won't be updated KB's until then.

Meanwhile, some people are having trouble with Windows Updates installation errors like 0x643...for example...

I would like to know if any member of this community has some further info on this subject matter and what is MS doing to speed up NOT ONLY on solutions BUT on the update of KB articles.

Regards,

RickCP

Windows XP Home SP3

---

RickCP Windows XP SP3

Answer 1

IN RE 643 errors & .NET Framework updates:

First run the Fix It in this KB article & see if the update will install after doing so:

How to fix MSI software update registration corruption issues

http://support.microsoft.com/kb/971187

If no joy, see...

When installing updates using Windows update or Microsoft Update you may receive Error 0x643 or 0x80070643

http://support.microsoft.com/kb/976982

Then proceed per the following:

=====================

Step #1 => Before doing anything else, write down what .NET Framework versions are currently installed:

    How to determine which versions of the .NET Framework are installed and whether service packs have been applied

    http://support.microsoft.com/kb/318785

   [As of this post, KB318785 hasn't been revised since November 2008 so you may not find the pertinent information in it.]

Step #2 => Now see Resolution Method 2 in this related KB article: http://support.microsoft.com/kb/923100

After running the .NET Framework Cleanup Tool (not the discontinued Windows Installer Cleanup utility), reinstall all .NET Framework versions (but only the ones you wrote down in #1 above) manually using the download links on the page then run Windows Update manually to install security updates for same.

Download links for .NET Framework Cleanup Tool:

• http://cid-27e6a35d1a492af7.skydrive.live.com/self.aspx/Blog_Tools/dotnetfx_cleanup_tool.zip

• http://blogs.msdn.com/cfs-file.ashx/__key/CommunityServer-Components-PostAttachments/00-08-90-44-93/dotnetfx_5F00_cleanup_5F00_tool.zip

NB: If you remove .NET Framework 3.5 (SP1) using the tool, reinstalling .NET Framework 3.5 will also install .Net Framework 2.0 SP2 and 3.0 SP2; then Windows Update will offer .NET Framework 3.5 SP1.

IMPORTANT! => If you remove .NET Framework 3.5 (SP1), reinstall your .NET Framework versions in the following order:

1. .Net Framework 3.5, then...    2. .Net Framework 1.1, then...    3. .Net Framework 1.1 SP1

NB: KB923100 references this page: http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx.  Please read ALL of it as well as the related page http://blogs.msdn.com/astebner/pages/8904493.aspx before using the .NET Framework Cleanup Tool.

Step #3 => Check-in at Windows Update and install any critical security updates offered.

---

~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

Answer 2

Yes, I did so... and also previously started a Windows Update Support incident email request (13-07-2010) and received a "case closed" answer with no explanation the two times I tried to reopen it stating it wasn't even attended.

In view of recent Windows Help and Support Center vulnerability as per CVE-2010-1885, I rather leave it that way, although I had installed the update KB2229593 (MS10-042) that same day...but you never know - Am I being paranoic?

Cheers,

RickCP

 

---

RickCP-Windows XP Home Edition SP3

Answer 3

Yes, I did so... and also previously started a Windows Update Support incident email request (13-07-2010) and received a "case closed" answer with no explanation the two times I tried to reopen it stating it wasn't even attended.

In view of recent Windows Help and Support Center vulnerability as per CVE-2010-1885, I rather leave it that way, although I had installed the update KB2229593 (MS10-042) that same day...but you never know - Am I being paranoic?

Cheers,

RickCP

---

RickCP-Windows XP Home Edition SP3

Answer 4

Why MS pulled out the tool (msicuu2.exe) without simultaneously updating KB's wherein it was (or still is) advised as a solution?...and...When can we expect these updated KB's? or the new "Fix it Solutions"? 

I dunno. (Read my sig.)

Perhaps you can ask MS yourself via the Feedback section at the bottom of this page? =>http://support.microsoft.com/kb/290301 

---

~Robear Dyer (PA Bear) ~ MS MVP (IE, Mail, Security, Windows & Update Services) since 2002 ~ Disclaimer: MS MVPs neither represent nor work for Microsoft

Answer 5

Thanks PA Bear your prompt reply which noted but it only refers to the error 643 I put in my post as an example, and no mention made in respect of main querry which is ... Why MS pulled out the tool (msicuu2.exe) without simultaneously updating KB's wherein it was (or still is) advised as a solution?...and...When can we expect these updated KB's? or the new "Fix it Solutions"? 

In my post I only mentioned two particular KB's as an example, but you know there are a few more, and that this situation has resulted in these forums being collapsed with participants asking for a solution to a very same question, different titles of course, but still same or very similar thread/topic: Updates Install/Uninstall, etc..  issues...

To avoid this confusion, woudn't it be wiser to previously have had Microsoft/Windows Update Errors Index updated? so that error 643 (following the same example) pointed to KB976982 (which as you certainly advised in your reply above is the solution) and NOT to KB923100? which as not updated is now obsolete. As this wasn't done (or is going very slow) we are all extra-working to get out of this fussy situation because of the lack of info. You can even see people looking for non-MS tools (like "Revo Uninstaller" for example) which believe might complicate the problem?.

I know you aren't a MS employee, but as an experienced MVP, guess you're much closer to MS than the majority inhere, so perhaps you or anyone of your partners could enlighten us a little more on this subject matter. I also note you are not even a Moderator here, but have done as if, a very very GOOD AND PRICELESS WORK...Congratulations!!!

Await your comments with interest.

Cheers,

RickCP

---

PD: In order to not continue messing the forums, I'm posting my personal "new" querries I.R.O. error 643 (which I did resolved with Aaron's tool) separately. However, can you tell me beforehand, how did you know I was dealing with .NET problems by just the mention of this error? Is this applicable to .NET problems only? Thanks.

---

---

RickCP Windows XP SP3