Answered Windows update error 643

  • Thursday, October 11, 2007 6:37 PM
     
     

    I am getting the following error with windows update and cannot get the update to install.

     

     

    Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903)

    Installation date: ‎10/‎11/‎2007 3:10 AM

    Installation status: Failed

    Error details: Code 643

All Replies

  • Friday, October 12, 2007 7:01 PM
     
     Answered

     

    This KB may be able to help with your issue:

     

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

  • Saturday, December 01, 2007 6:10 PM
     
     
    I had the same problem.  This was being caused by Bitdefender (My antivisrus software) stopping the update of the registry.  When I tried again BitDefender gave me the option of allowing the update - this option was selected and the update applied successfully.

     

  • Wednesday, April 23, 2008 7:27 PM
     
     

    Ok, I have just managed tofix this error after many attempts. Here it is.

    First, I downloaded "windows install cleanup" tool.

    next goto "add remove programs" and manually remove .NET Framework, Version 1.1 Service Pack 1

    If like me it appears not to work you need to run the Cleanup tool you just downloaded and remove the service pack.

    After this you need to manually download and Install the service pack direct from the microsoft website, use the following url    http://www.microsoft.com/downloads/details.aspx?familyid=A8F5654F-088E-40B2-BBDB-A83353618B38&displaylang=en.

    After you have installed this you will need to restart your pc and then goto windows update and run it.

    Hope this works for you, it worked for me and I was really getting fed up with this error, I cant believe Microsoft have not put out a patch for this problem.

    Good hunting

  • Thursday, December 11, 2008 10:22 PM
     
     
    thanks Paul
    it works. one thing to add.
    before installing the .net framework 1.1 service pack 1. you might want to install the .net framework 1.1 package first.
    or there is an error coming out when you try to install the service pack 1.
  • Friday, October 15, 2010 2:25 AM
     
     

    ola eu estava com mesmo problema eu retirei net framework 1.1 baixei  atualizaçao e depois baixei o net framework 1.1 deu certo 

     

  • Friday, August 12, 2011 3:41 PM
     
     

    I am getting the following error with windows update and cannot get the update to install.

     

     

    Security Update for Microsoft .NET Framework, Version 1.1 Service Pack 1 (KB886903)

    Installation date: ‎10/‎11/‎2007 3:10 AM

    Installation status: Failed

    Error details: Code 643


  • Monday, August 15, 2011 4:08 PM
     
     
    It hasn't worked for me. I went through the first stage and downloaded the windows install cleanup" tool and removed .NET Framework, Version 1.1 Service Pack 1(at least I think I did). But when I tried to install the  .net framework 1.1 package it failed. I went on and installed the service pack and that seemed to work. But after restarting my pc it still won't load several of the updates and I get the same failure code.
  • Wednesday, August 24, 2011 7:36 AM
     
     

    Hi,

    The Windows update error code 643 in Windows 7 Operating System could be resolved by the two methods.

    The first one is to fix the MSI software update registration corruption issues.

    For this you have to first confirm whether the product is affected or not.

    Then you have to re-create software update cache registry details and should delete the remaining software update references.

    If the problem is not solved then, you are advised to repair the .NET Framework using the .NET Framework Cleanup Tool.

     

    Get more information to fix windows update error 643 :

    http://supportformicrosoft.iyogi.com/windows-7/windows-7-error-code-643.html

     

    Hope this information helps you.

     

  • Monday, February 20, 2012 10:33 AM
     
     
    I had the same problem.  This was being caused by Bitdefender (My antivisrus software) stopping the update of the registry.  When I tried again BitDefender gave me the option of allowing the update - this option was selected and the update applied successfully.

     

    Hi,

    I also had this problem being caused by bullguard which I heard once used bitdefenders av engine. dont know how true this is but disabling bullguard fixed the problem, im going to reinstall it anyway 'cos disabling the av everytime i want 2 update isnt ideal

  • Monday, April 29, 2013 5:51 AM
     
     

    Fixed it!

    This is for those of you who have tried the methods here: http://support.microsoft.com/kb/923100/ and still failed. No guarantees this will work for you, but this is what worked for me n Win7 64bit.

    After extensive research, the problems seems to be caused by any combination of the following issues:

    1. Installing to the wrong drive (intentionally or not; always install in C:, i.e. root)
    2. Permissions issues
    3. Remaining files after uninstall (probably b/c of permissions issues)

    So, to address all three issues:

    1. Unmount all drives except your system root (c:)
    2. Set ownership of C:/Windows/Microsoft.NET to yourself (administrator), make sure you click the "Subfolders and files" checkbox so it affects all of the .NET files and folders.
    3. Set the permissions for administrator (or whatever owner you set) to full access
    4. Open up the Microsoft.NET folder and make sure Administrator has full access to those as well. If not, repeat steps 2 and 3 on each folder.
    5. The real fix here is going to this page, reading it carefully, and then downloading and running the .net cleanup tool: http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx
    6. Reboot and install .NET 4 from the dotNetFx40_Full_x86_x64 file you probably already have.

    Unless permissions and ownership makes sense to you, google it, or see here: http://helpdeskgeek.com/windows-7/windows-7-how-to-delete-files-protected-by-trustedinstaller/

    After step 5, you may want to click the View Log button on the cleanup tool and give it a scan for any lines that say *****Error!*****. They will likely point you to a file that needs to have its permissions changed so the tool can remove it. I found several of these on my first attempts.

    Good luck!