No successful Win10 updates for months — error 1900101

Page 1 of 2 12 LastLast

  1. Posts : 35
    Windows 10
       #1

    No successful Win10 updates for months — error 1900101


    My PC has been unable to successfully update for a long time. Here's the update history:

    Feature Updates (7)
    Feature update to Windows 10, version 1903 Failed to install on 8/1/2019 - Oxc1900101 See what's new in this update
    Feature update to Windows 10, version 1809 x64 2019-07B Failed to install on 7/16/2019 - Oxc1900101 See what's new in this update
    Feature update to Windows 10, version 1809 x64 2019-0600B Failed to install on 7/8/2019 - Oxc1900101
    See what's new in this update
    Feature update to Windows 10, version 1903 (2) Last failed install attempt on 7/7/2019 - Oxc1900101
    See what's new in this update
    Feature update to Windows 10, version 1809 x64 2019-06B (2) Last failed install attempt on 6/16/2019 - Oxc1900101 See what's new in this update
    Feature update to Windows 10, version 1809 amd64 2019-03 Failed to install on 3/23/2019 - Oxc1900101
    See what's new in this update
    Feature update to Windows 10, version 1809 (2) Last failed install attempt on 2/17/2019 - Oxc1900101 See what's new in this update

    My C: drive often has less than 20 GB free space, so I made sure that, before rebooting for today's attempted update, I had about 30 GB free. Same error.

    Often, after rebooting I'll be left with a black screen with a low-res ish mouse pointer, which responds to mouse movements.

    What should I do? Thanks.
      My Computer


  2. Posts : 13,301
    Windows 10 Pro (x64) 21H2 19044.1526
       #2

    Try running the update troubleshooter
    The error your listing is for a device driver error Check your Device Manager for any
    malfunctioning devices.

    Attachment 242633
      My Computers


  3. Posts : 35
    Windows 10
    Thread Starter
       #3

    Thanks for your suggestion; there are no exclamation marks in Device Manager. I showed hidden devices and expanded every section.
      My Computer


  4. Posts : 13,301
    Windows 10 Pro (x64) 21H2 19044.1526
       #4

    After running the trouble shooter try rebooting then try windows update

    What version of Windows are you running?

    run Winver.exe
      My Computers


  5. Posts : 9,788
    Mac OS Catalina
       #5
      My Computer


  6. Posts : 1,604
    Win 10 home 20H2 19042.1110
       #6

    Was this version of Windows a "Genuine Windows® 7 Home Premium", that you've been trying to upgrade to Windows 10?
      My Computers


  7. Posts : 35
    Windows 10
    Thread Starter
       #7

    • My current Windows version is 1803 build 17134.885.

    • I believe my old Win7 was Home Premium, but am not 100% sure. I upgraded to Win10 years ago.

    • DISM displayed:
    Code:
    Version: 10.0.17134.1
    
    Image Version: 10.0.17134.885
    
    [==========================100.0%==========================] The restore operation completed successfully.
    The operation completed successfully.
    • The only CBS.log line not tagged "Info" is:
    Code:
    2019-08-09 08:58:02, Warning               CBS    Current tick count: 800 lower than last tick count: 922. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
    • And the CBS log summary is:
    Code:
    Summary:
    Operation: Detect and Repair 
    Operation result: 0x0
    Last Successful Step: Entire operation completes.
    Total Detected Corruption:	0
    	CBS Manifest Corruption:	0
    	CBS Metadata Corruption:	0
    	CSI Manifest Corruption:	0
    	CSI Metadata Corruption:	0
    	CSI Payload Corruption:	0
    Total Repaired Corruption:	0
    	CBS Manifest Repaired:	0
    	CSI Manifest Repaired:	0
    	CSI Payload Repaired:	0
    	CSI Store Metadata refreshed:	True
    
    Total Operation Time: 229 seconds.
    Ensure CBS corruption flag is clear
    Ensure WCP corruption flag is clear
    All CSI corruption was fixed, ensure CorruptionDetectedDuringAcr is clear
    Failed to clear CorruptionDetectedDuringAcr store corrupt flag (slow mode trigger). [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
    Count of times corruption detected: 0
    Seconds between initial corruption detections: -1
    Seconds between corruption and repair: -1
    Reboot mark cleared
    Winlogon: Simplifying Winlogon CreateSession notifications
    Winlogon: Deregistering for CreateSession notifications
    Exec: Processing complete, session(Corruption Repairing): 30756529_2371245998 [HRESULT = 0x00000000 - S_OK]
    Session: 30756529_2371245998 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
    Session: 30756530_372617882 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
    Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
    TiWorker signaled for shutdown, going to exit.
    CbsCoreFinalize: ExecutionEngineFinalize
    Execution Engine Finalize
    Execution Engine Finalize
    Ending the TiWorker main loop.
    Starting TiWorker finalization.
    CbsCoreFinalize: ManifestCacheFinalize
    CbsCoreFinalize: ExecutionEngineFinalize
    CBS Engine already deativated
    CBS Engine already deativated
    CbsCoreFinalize: ComponentAnalyzerFinalize
    CbsCoreFinalize: PackageTrackerFinalize
    CbsCoreFinalize: CoreResourcesUnload
    CbsCoreFinalize: SessionManagerFinalize
    CbsCoreFinalize: CapabilityManagerFinalize
    CbsCoreFinalize: PublicObjectMonitorFinalize
    CbsCoreFinalize: Enter vCoreInitializeLock
    CbsCoreFinalize: WcpUnload
    CbsCoreFinalize: DrupUnload
    CbsCoreFinalize: CfgMgr32Unload
    CbsCoreFinalize: DpxUnload
    CbsCoreFinalize: SrUnload
    CbsCoreFinalize: CbsEsdUnload
    CbsCoreFinalize: CbsTraceInfoUninitialize
    CbsCoreFinalize: CbsEventUnregister
    CbsCoreFinalize: AppContainerUnload
    CbsCoreFinalize: WdsUnload, logging from cbscore will end.
    Ending TiWorker finalization.
    Ending the TrustedInstaller main loop.
    Starting TrustedInstaller finalization.
    Winlogon: Stopping notify server
    Winlogon: Unloading SysNotify DLL
    Ending TrustedInstaller finalization.
    • Windows Update Troubleshooter reported, at the end:

    Code:
    Potential Windows Update Database error detected [Not fixed]
    Windows could not automatically detect this network's Proxy settings [Detected]
    Windows Update components must be repaied [Fixed]
    Check for pending updates [Fixed]
    • System File Checker reported some corruption in update components. I didn't record the message.
    _____

    I rebooted and updates were installed. After logging in, the result was the same:

    Code:
    Feature update to Windows 10, version 1903 (3) Failed to install on 8/9/2019 - Oxc1900101
    What next? Thanks.
      My Computer


  8. Posts : 9,788
    Mac OS Catalina
       #8

    I would try a Repair Install with the ISO. If that fails, you will have to do a Clean Install.
      My Computer


  9. Posts : 1,604
    Win 10 home 20H2 19042.1110
       #9

    Windows could not automatically detect this network's Proxy settings [Detected]
    You're running proxy settings on purpose?
      My Computers


  10. Posts : 1,604
    Win 10 home 20H2 19042.1110
       #10

    This article has your error......... Windows 10, version 1903 Failed to install- Oxc1900101
    FIX: Windows 10 Update 1903 failed to install (Solved) - wintips.org - Windows Tips & How-tos

    You could also try this: open an elevated command prompt (run as Administrator) and enter the following lines:

    net stop wuauserv
    regsvr32 %windir%\syswow64\wups2.dll
    net start wuauserv
      My Computers


 

  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 02:05.
Find Us




Windows 10 Forums