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

112 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2025-03-22T06:10:58+00:00

    Hi UtterlyBaffled,

    Please open a separate thread.

    In the new thread enter information about the problems.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-22T05:41:10+00:00

    Lord help me! I'm 82 and I don't think I have enough time left on this planet to work out all all these solutions. I appreciate these are all volunteers trying to help, but why on earth doesn't Microsoft help??

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-22T04:11:20+00:00

    Open administrative command prompt and type or copy and paste:

    fltmc

    manage-bde -status C:

    Post a share link.

    Restart WDV with these groups of customized tests:

    Group 1

    [ ] 0x00000010 I/O verification.

[ ] 0x00000200 Force pending I/O requests. 

[ ] 0x00002000 Invariant MDL checking for stack. 

[ ] 0x00004000 Invariant MDL checking for driver. 

[ ] 0x00000100 Security checks. 

[ ] 0x00000800 Miscellaneous checks. 

[ ] 0x00200000 NDIS/WIFI verification.

    Group 2

    [ ] 0x00000020 Deadlock detection. 

[ ] 0x00000080 DMA checking. 

[ ] 0x00020000 DDI compliance checking. 

 [ ] 0x00080000 DDI compliance checking (additional). 

[ ] 0x00040000 Systematic low resources simulation.  

[ ] 0x00800000 Kernel synchronization delay fuzzing.

    Group 3

    [ ] 0x00008000 Power framework delay fuzzing. 

[ ] 0x00010000 Port/miniport interface checking. 

[ ] 0x00000002 Force IRQL checking. 

[ ] 0x00000008 Pool tracking. 

[ ] 0x01000000 VM switch verification. 

[ ] 0x02000000 Code integrity checks.

    For each group if there is no immediate BSOD then open administrative command prompt and copy and paste:

    verifier /querysettings

    Post a share link.

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

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-21T21:03:13+00:00

    I have no clue if I did this correctly. I set the verifier for all non-MS drivers. Did querysettings.

    Got this: https://www.dropbox.com/scl/fi/erwp3nyezvrowaplg736a/Non-MS-Drivers-Querysettings.txt?rlkey=ocbx43be4tvdwadqf97923lor&st=xwsr535e&dl=0

    Regarding BitDefender, if I remember correctly, it was turned on when I received the PC from Dell. I went in and made sure it was turned off on all drives. That was about a year ago at this point.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-03-21T13:57:40+00:00

    WDV is a tool that has menu settings.

    It will run once customized tests and drivers are selected to stress test the selected drivers.

    The driver column can be sorted so that all non-Microsoft drivers are selected.

    Each time the tool is launched it may cause a BSOD.

    If it causes a BSOD > run V2 > post a share link

    If it does not cause a BSOD > run verifier /querysettings > post a share link

    The tool runs indefinitely until it is turned off.

    Please learn the methods to turn off the tool.

    Customized tests will be posted for the next run of the tool to perform more tests on the non-Microsoft drivers.

    Was this answer helpful?

    0 comments