Forum Discussion

ManamanaTheReal's avatar
ManamanaTheReal
Copper Contributor
Mar 13, 2022

Update to Insider Preview 10.0.22572.100 (ni_release) causes rollback and 0xc1900101

I am currently using Windows version 22H2 build 22567.ni_release.220225-1325 and have tried to update to 10.0.22572.100 twice since yesterday. However, the update is aborted at 60% after a restart and a rollback is performed. The error 0xc1900101 was then displayed in the event log.

 

 

Here is the XML of the error.

 

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
<Provider Name="Microsoft-Windows-WindowsUpdateClient" Guid="{945a8954-c147-4acd-923f-40c45405a658}" />
<EventID>20</EventID>
<Version>1</Version>
<Level>2</Level>
<Task>1</Task>
<Opcode>13</Opcode>
<Keywords>0x8000000000000028</Keywords>
<TimeCreated SystemTime="2022-03-13T00:19:21.4634004Z" />
<EventRecordID>8507</EventRecordID>
<Correlation>
<Execution ProcessID="8076" ThreadID="6612" />
<Channel>System</Channel>
<Computer>ManamanaTheReal</Computer>
<Security UserID="S-1-5-18" />
</System>
- <EventData>
<Data Name="errorCode">0xc1900101</Data>
<Data Name="updateTitle">Windows 11, version 22H2 Insider Preview 10.0.22572.100 (ni_release)</Data>
<Data Name="updateGuid">{d6b85d8c-3901-40b5-9808-ecb600badea0}</Data>
<Data Name="updateRevisionNumber">1</Data>
<Data Name="serviceGuid">{8b24b027-1dee-babb-9a95-3517dfb9c552}</Data>
</EventData>
</Event>

 

Any suggestions for solutions?

Thanks in advance 🙂

 

 

4 Replies

  • SouravLinkuna's avatar
    SouravLinkuna
    Copper Contributor
    Mar 29, 2022
    I am also facing the exact same issue. Please let us if there is a solution to this problem
    • KevConlon's avatar
      KevConlon
      Copper Contributor
      Apr 01, 2022
      Also having the same problem.....seems exactly same problem.
      Update installs.....Restart PC...update appears to complete to 60%.....then fails to complete.
      Error code is : 0xc1900101

      Have repeated several times....no luck.
      sfc /scannow doesn't help.....and neither does running the Windows Update Troubleshooter.