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 No comments

104 answers

Sort by: Newest
  1. Ramesh 181.2K Reputation points Volunteer Moderator
    2025-05-15T17:57:39+00:00

    Hi sms1295#,

    Thanks. There are many issues, starting from Cryptographic services not starting, and hence the VSS service is crashing with error 0x80070006. There are remnants of VirtualBox and VMware in network bindings. Microsoft Defender is crashing with the errors 0x80070006 and 0xc0000005.

    Harddisk5 is going bad ("The driver detected a controller error on \Device\Harddisk5\DR5."), But that may not be related to the original issue.

    System Restore Point can't be created unless the VSS and Cryptographic Services are fixed.


    If you're willing to attempt the setup one more time, please try the following:

    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 the driver packages have been backed up to C:\Drivers already.)

    • pnputil /delete-driver oem134.inf /uninstall /force
    • pnputil /delete-driver oem2.inf /uninstall /force
    • pnputil /delete-driver oem51.inf /uninstall /force
    • pnputil /delete-driver oem61.inf /uninstall /force
    • pnputil /delete-driver oem68.inf /uninstall /force
    • pnputil /delete-driver oem75.inf /uninstall /force
    • pnputil /delete-driver oem77.inf /uninstall /force
    • pnputil /delete-driver oem80.inf /uninstall /force
    • pnputil /delete-driver oem83.inf /uninstall /force
    • pnputil /delete-driver oem88.inf /uninstall /force
    • pnputil /delete-driver oem89.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.
    2. You may retry the setup using the ISO with dynamic updates turned off and internet connection enabled.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2025-05-15T17:21:16+00:00

    questions,

    Thanks for the info, but doing these steps is out of my comfort zone. I need to take a step back and consider a clean install.

    Thanks again,

    sms1295

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2025-05-15T16:02:30+00:00

    There was another BSOD today.

    WDV is used multiple times per day in threads.

    When possible start the tool with the 3 customized tests in this link:

    Enable and Disable Driver Verifier in Windows 10 | Tutorials

    Boot to Advanced Startup Options in Windows 10 | Tutorials

    (Option six or five)

    For each test:

    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.

    BSOD - Posting Instructions - Windows 10 Forums

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2025-05-15T15:39:37+00:00

    Ramesh,

    driver.txt added to the shared drive.

    Link below:

    https://drive.google.com/drive/folders/1pAkm8Z6XBzIzfItGsqtEctSxFMpbP4UR?usp=drive_link

    Was this answer helpful?

    0 comments No comments
  5. Ramesh 181.2K Reputation points Volunteer Moderator
    2025-05-15T15:11:59+00:00

    It failed again. I've uploaded the results and logs to the shared drive. FYI, the CrashDumps folder was empty. I created the folder as >> C: CrashDumps.

    Shared link below:

    https://drive.google.com/drive/folders/1pAkm8Z6XBzIzfItGsqtEctSxFMpbP4UR?usp=drive_link

    Let me know the next steps.

    sms1295

    Hi sms1295,

    The Setup didn't crash this time. Anyway, we can turn off the setuphost.exe dump creation later.

    Please run:

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

    Share c:\drivers.txt.


    Edit:

    Looks like there was a crash (not the user mode crash like the last time), but no dump was generated. Many services terminated as well.


    Log Name: System

    Source: volmgr

    Date: 5/15/2025 7:44:26 PM

    Event ID: 46

    Task Category: None

    Level: Error

    Keywords: Classic

    User: N/A

    Computer: XPS-720

    Description:

    Crash dump initialization failed!

    Event Xml:


    Was this answer helpful?

    0 comments No comments