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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2025-03-22T20:07:37+00:00

    V2 is the log collector.

    Please post a new link.

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

    BSOD - Posting Instructions - Windows 10 Forums

    BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)

    Restart WDV with these groups:

    Group a

    [ ] 0x00008000 Power framework delay fuzzing.

    [ ] 0x00010000 Port/miniport interface checking.

    [ ] 0x00000008 Pool tracking.

    Group b

    [ ] 0x01000000 VM switch verification.

    [ ] 0x00000002 Force IRQL checking.

    Group c

    [ ] 0x02000000 Code integrity checks.

     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
  2. Anonymous
    2025-03-22T20:32:09+00:00

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-22T20:50:39+00:00

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-22T22:13:19+00:00

    After I ran Group b, I was running the querysettings and I got a BSOD. After I rebooted I tried running the V2, got partially through that and then another BSOD. I have included what was saved when that happened, not sure if that is useful. Right now I have the verifier disabled. Waiting to see if you want me to run V2 now and post, or just go to group c? Here is what was saved from V2 before the second BSOD:

    https://www.dropbox.com/scl/fi/tt5gsdjf2mtxv4ufzpwck/SOUNDCHASER-2025-03-22_17-10-53.zip?rlkey=nnrsiwg9ra55jg1ec7aklfrk2&st=eo61hsqy&dl=0

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-03-23T00:53:43+00:00
    1. Find a replacement driver then reinstall:

    kfecosvc KfeCoSvc c:\windows\system32\drivers\rivetnetworks\killer\kfeco11x64.sys

    1. Create a new restore point.
    2. Restart WDV with the same customized tests > post querysettings or V2

    Group b

    [ ] 0x01000000 VM switch verification.

    [ ] 0x00000002 Force IRQL checking.

    1. Test the next group of customized tests post a new share link.

    Group c

    [ ] 0x02000000 Code integrity checks.

    1. Run all customized tests except:

    [ ] 0x00000004 Randomized low resources simulation.

    All steps (1 - 5) can be performed for your next post.

    Was this answer helpful?

    0 comments