Page 1 of 1

Windows Update Error 800B0001

PostPosted: 28.07.2012, 00:19
by hk1
I'm getting an error on a Windows 7 Pro 32 bit machine after using the wsusoffline updater to update the machine.

The computer is joined to a Windows domain but we are not using WSUS. Windows Updates are turned off but if I manually try to run Windows/Microsoft Update I get error 800B0001.

You can see more on this error here:
http://social.technet.microsoft.com/For ... a982dd95f/

Any idea how to fix this?

Re: Windows Update Error 800B0001

PostPosted: 28.07.2012, 08:15
by aker
As a First step I would try to cleanup Windows Update Cache and reinstall WUA.
You have to Start the Cmd
Click Start -> Run -> Type "Cmd" and press Enter
The stop Windows Update using
Code: Select all
net stop wuauserv

In the Windows Explorer go to c:\windows\softwaredistribution and delete its content
Then reinstall wua
Code: Select all
Cd /d N:\wsusoffline\client\wsus
WindowsUpdateAgent30-x86.exe /wuforce

Just replace N:\wsusoffline through you wsusoffline path.
then reboot

If it doesn't work try Running this command
Code: Select all
wuauclt /detectnow /resetauthorization


@WSUSUpdateAdmin
Die Root-Zertifikate stehen im verdacht diesen Fehler auszulösen, kann man das irgendwie testen?

Re: Windows Update Error 800B0001

PostPosted: 15.10.2012, 16:42
by eshornock
The answer accepted here solved the issue for me: http://superuser.com/questions/431067/w ... -is-not-ru

  • Go to c:\windows\softwaredistribution\datastore\logs.
  • Find the file edb.log.
  • Rename or delete the file.
  • You may encounter the following File In Use message, "The action can't be completed because the file is open in Application Experience." If you do, reboot the PC in Safe Mode. Then, browse back to the log file and try to rename or delete it again. It should work this time.
  • Once the file is renamed or deleted, reboot windows in normal mode.
  • Try to run Windows Update again. It will work normally.


I had the problem on two systems with an older version of offline update. I do not know if it's still a problem. (I'll try it in a fresh Win7 installation in a few days)