After 1803 to 1809 upgrade, Windows Update no longer works

Page 1 of 2 12 LastLast

  1. Posts : 66
    Windows 10 Pro 1809 x64
       #1

    After 1803 to 1809 upgrade, Windows Update no longer works


    On Friday, I upgraded a VirtualBox VM 1803 Professional x64 to 1809. When the upgrade was complete, I ran Windows Update, but it errored out after a long delay with ERROR_TIMEOUT (0x800705b4).

    I have tried a clean boot and resetting the Windows Update components. That did not fix the problem, and neither did SFC /SCANNOW or the Windows Update troubleshooter.

    Can anyone advise?
      My Computer


  2. Posts : 1,750
    Windows 10 HOME 64-BIT
       #2

    Hmmmm.... maybe resetting Windows Update?

    Code:
    Script Reset Windows Update Agent
    
    1.    Open a command prompt.
    2.    Stop the BITS service, the Windows Update service, and the  Cryptographic service. To do this, at a command prompt, type the  following commands. Make sure that you press Enter after you type each  command.
    •    net stop bits
    •    net stop wuauserv
    •    net stop appidsvc
    •    net stop cryptsvc
    3.    Delete the qmgr*.dat files. To do this, at a command prompt, type the following command, and then press Enter:
    Del "%ALLUSERSPROFILE%\Application Data\Microsoft\Network\Downloader\qmgr*.dat"
    4.     If this is your first attempt at resolving your Windows Update issues  by following the steps in this article, you should skip step 4 and go to  step 5. You should follow step 4 at this point in the troubleshooting  only if you cannot resolve your Windows Update issues after you follow  all steps except step 4. (Step 4 is performed by the "Aggressive" mode  of the Fix it Solution that was mentioned earlier.)
    a.    Rename the  softare distribution folders backup copies. To do this, at a command  prompt, type the following commands. Make sure that you press Enter  after you type each command.
    •    Ren %systemroot%\SoftwareDistribution SoftwareDistribution.bak
    •    Ren %systemroot%\system32\catroot2 catroot2.bak
    b.     Reset the BITS service and the Windows Update service to the default  security descriptor. To do this, at a command prompt, type the following  commands. Make sure that you press Enter after you type each command.
    •     sc.exe sdset bits  D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
    •     sc.exe sdset wuauserv  D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)
    5.    At a command prompt, type the following command, and then press Enter:
    cd /d %windir%\system32
    6.     Reregister the BITS files and the Windows Update files. To do this, at a  command prompt, type the following commands. Make sure that you press  Enter after you type each command.
    Note: ignore if any of the following command not run, just continue....
    •    regsvr32.exe atl.dll
    •    regsvr32.exe urlmon.dll
    •    regsvr32.exe mshtml.dll
    •    regsvr32.exe shdocvw.dll
    •    regsvr32.exe browseui.dll
    •    regsvr32.exe jscript.dll
    •    regsvr32.exe vbscript.dll
    •    regsvr32.exe scrrun.dll
    •    regsvr32.exe msxml.dll
    •    regsvr32.exe msxml3.dll
    •    regsvr32.exe msxml6.dll
    •    regsvr32.exe actxprxy.dll
    •    regsvr32.exe softpub.dll
    •    regsvr32.exe wintrust.dll
    •    regsvr32.exe dssenh.dll
    •    regsvr32.exe rsaenh.dll
    •    regsvr32.exe gpkcsp.dll
    •    regsvr32.exe sccbase.dll
    •    regsvr32.exe slbcsp.dll
    •    regsvr32.exe cryptdlg.dll
    •    regsvr32.exe oleaut32.dll
    •    regsvr32.exe ole32.dll
    •    regsvr32.exe shell32.dll
    •    regsvr32.exe initpki.dll
    •    regsvr32.exe wuapi.dll
    •    regsvr32.exe wuaueng.dll
    •    regsvr32.exe wuaueng1.dll
    •    regsvr32.exe wucltui.dll
    •    regsvr32.exe wups.dll
    •    regsvr32.exe wups2.dll
    •    regsvr32.exe wuweb.dll
    •    regsvr32.exe qmgr.dll
    •    regsvr32.exe qmgrprxy.dll
    •    regsvr32.exe wucltux.dll
    •    regsvr32.exe muweb.dll
    •    regsvr32.exe wuwebv.dll
    7.    Reset Winsock. To do this, at a command prompt, type the following command, and then press Enter:
    netsh winsock reset
    8.     If you are running Windows XP, you have to configure the proxy  settings. To do this, at a command prompt, type the following command,  and then press Enter:proxycfg.exe -d
    If you are running other versions of Windows, at a command prompt, type the following command, and then press Enter:
    netsh winhttp reset proxy
    9.     Restart the BITS service, the Windows Update service, and the  Cryptographic service. To do this, at a command prompt, type the  following commands. Make sure that you press Enter after you type each  command.
    •    net start bits
    •    net start wuauserv
    •    net start appidsvc
    •    net start cryptsvc
    10.    Windows Vista only: Clear the BITS queue. To do this, at a command prompt, type the following command, and then press Enter:
    bitsadmin.exe /reset /allusers
    11.    Install the latest Windows Update Agent (http://support.microsoft.com/kb/949104).
    12.    Restart the computer.
    EDIT: Oops, you already done that...
      My Computer


  3. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #3

    Not all of those commands work, but stopping the services and the two renames, followed by restarting the services, appears to have worked. Windows Update now concludes its check normally, without displaying an error code.

    Thanks!
      My Computer


  4. Posts : 1,750
    Windows 10 HOME 64-BIT
       #4

    YAY! Happy updating!
    Katanga said:
    Not all of those commands work, but stopping the services and the two renames, followed by restarting the services, appears to have worked. Windows Update now concludes its check normally, without displaying an error code.

    Thanks!
      My Computer


  5. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #5

    I am still getting errors.

    CSI 00000001@2019/1/14:19:13:40.933 WcpInitialize: wcp.dll version 10.0.17763.164 (WinBuild.160101.0800)
    CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
    CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
    CBS NonStart: Set pending store consistency check.
    CBS Session: 30714941_1115766820 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    CBS Session: 30714941_1115766821 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    Any idea how these can be fixed?
      My Computer


  6. Posts : 1,750
    Windows 10 HOME 64-BIT
       #6

    Katanga said:
    I am still getting errors.

    CSI 00000001@2019/1/14:19:13:40.933 WcpInitialize: wcp.dll version 10.0.17763.164 (WinBuild.160101.0800)
    CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
    CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
    CBS NonStart: Set pending store consistency check.
    CBS Session: 30714941_1115766820 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    CBS Failed to OpenPackage using worker session [HRESULT = 0x800f0805]
    CBS Session: 30714941_1115766821 initialized by client WindowsUpdateAgent, external staging directory: (null), external registry directory: (null
    CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    CBS Failed to create open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]

    Any idea how these can be fixed?
    Guys..? Guys...? Little help here...
      My Computer


  7. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #7

    And, the error code (0x800705b4) is back.

    I am thinking the most prudent move at this point is to roll back the 1809 update.
      My Computer


  8. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #8

    Hmm ... it seems that the Windows Update service is crashing due to
    Windows.Devices.Sensors.dll.
    Faulting application name: svchost.exe_wuauserv, version: 10.0.17763.1, time stamp: 0xb900eeff
    Faulting module name: Windows.Devices.Sensors.dll, version: 10.0.17763.1, time stamp: 0xc76a188d
    Exception code: 0xc0000005
    Fault offset: 0x0000000000004dc2
    Faulting process id: 0x3710
    Faulting application start time: 0x01d4ac4bb519bfce
    Faulting application path: C:\WINDOWS\system32\svchost.exe
    Faulting module path: C:\Windows\System32\Windows.Devices.Sensors.dll
    Report Id: 8fa1d696-dff0-41cd-b94c-93bed1c7ccbc
    Faulting package full name:
    Faulting package-relative application ID:
      My Computer


  9. Posts : 56,825
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #9

    I use VMWare, not Virtual Box, but could it be the Host Software? Virtual Box? No problems with VMWare.
      My Computers


  10. Posts : 66
    Windows 10 Pro 1809 x64
    Thread Starter
       #10

    I have another VirtualBox VM which doesn't have these problems.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 00:29.
Find Us




Windows 10 Forums