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. Ramesh 181.2K Reputation points Volunteer Moderator
    2025-03-26T10:31:21+00:00

    SetupLogs.zip

    Thanks. Please share the Farbar scan logs as well.

    1. Download Farbar Recovery Scan Tool 64-bit (FRST64.exe)

    https://downloads.malwarebytes.com/file/mbst-frst64

    Note: If Microsoft Edge or Chrome mislabels the Farbar Scanner executable as PUA/malware, choose to keep it by tapping … in the bottom bar, choosing Keep, and then choosing Keep anyway in the dialog that appears.

    See this screenshot: https://learn.microsoft.com/en-us/deployedge/media/microsoft-edge-security-download-interruptions/dowload-was-blocked.png. It's a safe tool used in most antimalware forums.

    1. If the OS language is not English, rename FRST64.exe to FRST64English.exe.
    2. Run the program. Don't check or uncheck any options. Click "Scan".
    3. Add the two logs, FRST.txt and Addition.txt, to a Zip archive, upload them to your OneDrive and share the link here.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-03-26T20:13:36+00:00

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-03-26T23:27:29+00:00

    Please update the progress with the prior steps:

    1. Restart WDV with all customized tests except:

    [ ] 0x00000004 Randomized low resources simulation.

    Test all non-Microsoft drivers except:

    kfeco11x64.sys

    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.

    1. Open administrative command prompt and copy and paste:

    dism /online /get-drivers /format:table >C:\drivers.txt

    Dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

    Post a share link

    1. Open device manager > click view > click show hidden devices > manually expand all rows

    (look for any displaying a yellow triangle with black exclamation mark or unknown device; identify rivetnetworks)

    right click > click properties > click details tab > from the property drop-down choose hardware ids > the vendor ID and device ID for that particular device will be listed.

    Post a share link

    https://www.howtogeek.com/193798/how-to-find-drivers-for-unknown-devices-in-the-device-manager/

    https://www.pcworld.com/article/2089404/how-to-easily-find-drivers-for-unknown-devices-in-windows.html

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-03-27T20:09:26+00:00

    I will run this on the weekend. Thanks.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-03-28T22:35:50+00:00
    1. Restart WDV wih all customized tests except:

    [ ] 0x00000004 Randomized low resources simulation.

    Test all non-Microsoft drivers except:

    kfeco11x64.sys

    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.

    My PC would not boot; stopped at Dell logo. Used the restore point to boot up.

    Here is the V2 link: SOUNDCHASER-(2025-03-28_17-14-06).zip

    1. Open administrative command prompt and copy and paste:

    dism /online /get-drivers /format:table >C:\drivers.txt

    Dism /online /get-drivers /format:table > "%userprofile%\desktop\drivers.txt"

    Link: drivers.txt

    ^^^ weirdest thing happened when I ran #2. Windows was telling me it couldn't find the file even though I could see it and copy it.

    Was this answer helpful?

    0 comments