error code 643

I am trying to install "Security Update for Microsoft .NET Framework, Version
1.1 Service Pack 1 (KB929729). I keep getting error code 643. Could someone
help me. I have Windows Vista on my computer
gdayment

Posted to the microsoft.windowsupdate via crosspost

--
Peter

Please Reply to Newsgroup for the benefit of others
Requests for assistance by email can not and will not be acknowledged.

"gdayment" <gdayment@discussions.microsoft.com> wrote in message news:606B9E1A-033F-4427-9A51-B7E49E99D230@microsoft.com...
>I am trying to install "Security Update for Microsoft .NET Framework, Version
> 1.1 Service Pack 1 (KB929729). I keep getting error code 643. Could someone
> help me. I have Windows Vista on my computer
> gdayment

"gdayment" <gdayment@discussions.microsoft.com> wrote ...
>I am trying to install "Security Update for Microsoft .NET Framework,
>Version
> 1.1 Service Pack 1 (KB929729). I keep getting error code 643. Could
> someone
> help me. I have Windows Vista on my computer


Thanks and kudos to Chris Rowat, who first provided this solution over in
the MSDN forums :-

1) Download and run the Windows Installer Cleanup Utility. Use it to remove
the .NET Framework 1.1 from the machine.

Windows Installer Cleanup Utility
http://support.microsoft.com/kb/290301


2) Download .NET Framework 1.1 from the Microsoft website (don't download
via Windows Update), and save it to your hard disk (file name dotnetfx.exe).

..NET Framework 1.1
http://www.microsoft.com/downloads/d...displaylang=en


3) Download .NET Framework 1.1 Service Pack 1, and save it to your hard disk
(file name NDP1.1sp1-KB867460-X86.exe)

..NET Framework 1.1 Service Pack 1
http://www.microsoft.com/downloads/d...displaylang=en


4) Run the downloaded dotnetfx.exe to install .NET Framework 1.1.

5) Reboot your machine.

6) Run NDP1.1sp1-KB867460-X86.exe to install .NET Framework 1.1 SP1.

7) Reboot your computer again.

8) Now run Windows Update again, to install post SP1 hotfixes.

Not all the reboots maybe necessary, but ... better safe than sorry.

Caveat: I have not used this myself (I never got the 643 error). But many
folks in MSDN forums have confirmed this procedure has fixed the "643" error
for them. There may be other solutions, too.

Hope this helps,
--
Andrew McLaren
amclar (at) optusnet dot com dot au