Win 11 Version 24H2 Install Failed

Anonymous
2025-05-08T01:25:37+00:00

I tried to install Win 11 Version 24H2 for the second time, and it failed for a second time. The first BSOD message gave the following info:

Your device ran into a problem and needs to restart.

Stop code: INACCESSIBLE BOOT DEVICE

After a couple of restarts, the update was backed out. I'm back on Windows 11 Pro Version 23H2.

I checked the update history and saw the Install error code - 0xc1900101.

Before I tried the 24H2 update, I did the following:

Unplug unnecessary USB devices

Drivers were updated

No issues in Device Manager

I have 30GB of free space on the drive

Any help would be appreciated,

sms1295

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

104 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2025-05-15T22:03:39+00:00

    Was this answer helpful?

    0 comments
  2. Anonymous
    2025-05-15T20:55:17+00:00

    What do you mean be 'new V2 share link'

    Was this answer helpful?

    0 comments
  3. Anonymous
    2025-05-15T20:06:07+00:00

    Please post a new V2 share link into the newest post.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2025-05-15T20:00:57+00:00

    Ramesh,

    Here is what I've done:

    1. Reset the network using the "Network Reset" feature in Settings. This removes all network adapters, adapter settings, and re-installs them. Your Wi-Fi profiles may be deleted and need to be configured again. Restart Windows.
    2. Uninstall Intel(R) Extreme Tuning Utility.
    3. Certain 3rd party driver packages can be deleted using these commands:

    All deleted except the ones below, which came back with the message :Failed to delete driver package: One or more devices are presently installed using the specified INF.

    pnputil /delete-driver oem51.inf /uninstall /force

    pnputil /delete-driver oem68.inf /uninstall /force

    pnputil /delete-driver oem83.inf /uninstall /force

    rundll32.exe c:\windows\system32\pnpclean.dll,RunDLL_PnpClean /DEVICES /MAXCLEAN

    pnputil /enum-devices /problem /ids

    1. Share the contents of "C:\Windows\Minidump". The last minidump was probably created on May 10.

    Anything else before I try again.

    sms1295

    Was this answer helpful?

    0 comments
  5. Anonymous
    2025-05-15T18:58:46+00:00

    If you're considering a clean install then it's a test drive opportunity.

    If there is no misbehaving driver then WDV does not typically cause BSOD crashes.

    If there is a misbehaving driver then WDV typically cause BSOD crashes.

    To recover from a WDV BSOD > hard reboot > safe mode > type verifier /reset and / or verifier /bootmode resetonbootfail

    Once you hard reboot and recover to the desktop > logs are collected > a misbehaving driver may be uninstalled.

    Then it's a "rinse and repeat" process for other customized tests.

    If a dump file is created it can be debugged.

    WDV is designed to cause repetitive crashes until the tool is turned off.

    The tool cannot cause crashes while in safe mode.

    So it's learning how to hard boot (the power switch) to boot into safe mode.

    Boot to Advanced Startup Options in Windows 10 | Tutorials

    (Option six or five)

    If you want me to be available then let's schedule a time.

    Was this answer helpful?

    0 comments