Windows 11 23H2 installation fails

Anonymous
2023-11-09T20:12:14+00:00

I have been trying, unsuccessfully, to update my Lenovo Thinkpad T490 to Windows 11. Last resort before going to some kind of paid solution is to throw this out to the community. Here's a summary of what I have tried already.

Windows has been not-so-gently nagging me to upgrade from Windows 10 to Windows 11 for at least 18 months and assures me that my computer can run it. There is about 32 GB free space on the hard drive. Drivers are up to date.

When I use the Update function from the Settings the update downloads and I am prompted to reboot. During the reboot, I can see the screen indicating the progress of the installation, but in the end the system is still in Windows 10. The message below is displayed in the Windows Update screen "There were some problems installing updates, but we’ll try again later. If you keep seeing this and want to search the web or contact support for information, this may help: (0x8007001f)"

When I use the Windows 11 Installation Assistant the update also downloads successfully, but the computer still boots back into Windows 10. The only difference is that the message in the Windows Update page in settings now references the code 0xc00000f0.

Similarly, if I use the media creation tool to create a .ISO file, the update downloads, but the installation still fails.

I have also tried updating from a clean reboot, removing the laptop from the docking station to ensure that no external devices (other than Logitech wireless mouse and keyboard) are connected, and uninstalled the McAfee antivirus program that my ISP provides.

I have also tried all of the suggested fixes and scans from this YouTube video: https://www.youtube.com/watch?v=1Pz52tUWNPU.

I'm out of ideas. If anyone can suggest further steps, I'd love to hear them.

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
Answer accepted by question author
Ramesh 181.6K Reputation points Volunteer Moderator
2023-11-25T19:06:44+00:00

There are a lot of unwanted/invalid profiles. Download and run del_unwanted_profiles.reg. Click Yes to confirm.

(As you've already backed up the key to "Profilebad.hive", go ahead and run the above registry fix without any hesitation.)

Re-run the Windows setup now.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

77 additional answers

Sort by: Newest
  1. Anonymous
    2023-11-19T01:50:38+00:00

    Please reinstall Synaptics Pointing Device Driver using the Lenovo website.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-11-18T13:30:45+00:00

    The computer was left on overnight with no further BSOD. I have therefore stopped WDV. Here's the zipped memory dump file.

    I'll continue the troubleshooting later today.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-11-18T09:28:45+00:00

    WDV can be turned off.

    Open administrative command prompt (ACP) and copy and paste:

    PowerShell $D=(New-Object -ComObject Wscript.Shell).SpecialFolders(4);Compress-Archive "%WinDir%\MEMORY.DMP" "$D\Memory_dmp"
    

    Post a share link with only the compressed memory dump.

    Microsoft deprecated backup imaging.

    Please use free or pay backup imaging during the troubleshooting.

    After troubleshooting has been completed it can be deleted or you can continue using backup imaging.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-11-18T00:22:41+00:00

    I set msconfig to a normal start up and loaded the same that reduced set of programs that I have been using during this testing. Then started WDV with full set of tests except for "Randomized low sources simulation", rebooted, and got a BSOD. Message on the blue screen was IRQL NOT LESS OR EQUAL. The computer rebooted normally subsequent to this; possibly took a bit longer than usual for the Windows sign-in page to become responsive but not too much.

    Here is the V2 log. I also ran verifier/querysettings after successful start up.

    The computer seems to be stable now with WDV running. Will let it run until tomorrow morning.

    Was this answer helpful?

    0 comments No comments