Error 0x1900101 WIn 11 24H2 I Am Clueless

Anonymous
2025-03-16T17:39:06+00:00

Tried many times to update WIn11 23H2 to 24H2. Gets to a certain point and rolls back. Error 0x1900101. Tried so many things online, but this seems to be a generic error and it does not help. No clue where to turn to fix it at this point. Can someone help?

Windows for home | Windows 11 | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

112 answers

Sort by: Oldest
  1. Anonymous
    2025-03-20T02:28:58+00:00

    There was a BSOD during the upgrade.

    1. Please read this link on Windows Driver Verifier (WDV):

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    1. Create a new restore point:

    https://www.elevenforum.com/t/create-system-restore-point-in-windows-11.3602/

    1. Learn the methods to recover from BSOD caused by WDV by booting into safe mode and running one or more of these commands:

    verifier /reset

    verifier /bootmode resetonbootfail

    https://www.elevenforum.com/t/boot-to-advanced-startup-winre-in-windows-11.425/

    1. Plan to run the tool with various customized test settings.

    a) Test all non-Microsoft drivers

    b) Test no Microsoft drivers

    c) For the first run of WDV select the 3 customized tests displayed in the TF tutorial

    1. Whenever the WDV tool is started if there is no immediate BSOD then open administrative command prompt and copy and paste:

    verifier /querysettings

    Post a share link.

    Customized tests will then be posted for the next run of WDV.

    WDV can run continuously during the testing.

    For any BSOD post a new V2 share link into the newest post.

    0xC1900101, 0x2000D

    BugCheck 3B

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-03-20T20:22:58+00:00

    What is TF tutorial?

    And am I reading this correctly, you want the first run to be the last item on the list of customized test settings?

    I probably will not have the time to start this until the weekend.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-03-20T20:35:07+00:00

    Also, the link for Bot to Adv Startup WinRE seems pretty dire. Could these tests cause this much damage. I mean, hell, my computer seems to work fine, and if it won't update Window 11 (which in my opinion is the worst release MS has ever made - because I have had nothing but headaches on two PCs running WIndows 11), I'm not sure I want to chance not having access to what I now use every day.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-03-21T03:11:24+00:00

    These were the posted tutorials:

    https://www.tenforums.com/tutorials/5470-enable-disable-driver-verifier-windows-10-a.html

    https://www.elevenforum.com/t/boot-to-advanced-startup-winre-in-windows-11.425/

    Ten Forums = TF

    Eleven Forum = EF

    This is an index of the TF tutorials:

    Windows 10 Tutorial Index | Tutorials

    Windows Driver Verifier = WDV

    WDV has approximately 20 customized tests.

    The first run has 3 specified customized tests as per the tutorial.

    The WDV tool has commands to turn it on and off.

    The commands run in Windows Recovery Environment (RE).

    The advanced startup has the methods to boot into Windows RE.

    Booting into Windows RE opens command prompt to turn off WDV.

    The commands in step #3 are used to turn off the tool.

    Misbehaving drivers can be uninstalled or uninstalled and reinstalled.

    The same or new customized tests can be selected to check for more misbehaving drivers.

    System restore points are created as an additional method to recover from WDV BSOD's.

    System restore should not be used to turn off the tool unless the commands fail to turn off the tool.

    The tool can run during the weekend.

    Was this answer helpful?

    0 comments No comments