Windows 11, version 24H2 won't install

I've tried to update to the W24H2 version numerous times I've the last 2 weeks. Sometimes from the usage offered through the Windows updates and some times via the downloaded ISO file.

Fails every time.

Error message is 0xc1900101 -- 0x20017. "The installation failed in the SAFE_OS phase with an error during BOOT operation.

I've tried the disk and SFC options often suggested. Cleared the update cache, disabled my antivirus (Norton 360), and always get the same result. Update goes right through too 100% completed, then restarts showing the error above.

I've looked on

In the setup error log file in windows_bt\sources\panther folder, along with most of the other logging files created.

No clue there apart from an entry saying unable to delete the registry key which contains the update....... Subjects.

Hklm\something.

All the advice suggests updating your third party drivers since this is the usual cause of the error listed.

Unfortunately I have updated all the drivers I can, but it would be really helpful if the loss told me WHICH driver was the cause of the problem.

I've given up trying now until Microsoft can sort out a decent update version which either works or can give more useful logging into.

Not going to try a clean install from the iso because I'm not convinced it would work either, and can't face the hassle of reinstalling all my apps

That's because they tightened up on security on the second boot and it's a complete re-install like Windows 7/8 to 10. Getting the drivers right for the migration to work.

Joel above says its not the users job etc. From all the posts Microsoft think it is. They bit off more than they can chew with 24h2. The Insider programme identify 24h2 installation issues earlier in the year. You see people stuck on test versions not being able to get off 24h2 onto the next for the very same reasons they can't get onto the "final" release now. All the solutions being offered up as now.

There seem to be a few Microsoft people and hobbyists that can read the error logs generated which you zip up and publish for them to look at or you become an expert yourself in these. That solution I posted above is the second boot solution of driver issues they don't talk about widely which hones in on the suspect drivers. Well worth running it. Fixed my issue by pointing exactly to the non compliant driver.

Personally as far as the 24h2 upgrade is concerned given Microsoft’s re-engineering Windows in this release, either the upgrade will work or not. I can't see them automating the process of finding the non compliant drivers that fail the second boot. You got to sort that out yourself. It's a design issue in what they have done. You can use that tool which identifies candidates and sort it out yourself but does need a level of computer skills for the rest you have to find an expert. The problem with not upgrading is that support will eventually run out. Suspect your local PC place will do a fresh install and say job done. Others may do it properly.

The old saying in the UK it is, what it is. Which means you just got to get on with it and make a job of it given the tools. It took me nine weeks to install it on one laptop, whilst another it went straight in. Pesky drivers you need to find if you have already removed all traces of non Microsoft virus programs. Do that first.

The problems with the drivers in the ISO method of recommended ones, you don't take the recommended ones (toggle off), that can mess up the first boot and you end up in a blue screen boot. Been there, done that, causes the heart to race. Assistant method is the safest but doesn't give you the full error codes. You then get the eventual correct drivers once you pass the second boot. A number of trip wires to cross. Match the first boot drivers and for second secure boot you must ditch the ones that will fail the second boot security check. That tool I posted up, will tell you what they are.

Updating all drivers to the most recent can introduce problems on the first boot. This I ended up with, but my solution I found on line with this:

》》

I figured out the issue with my specific machine way back in January, It was a driver issue.

The driver in question was "Intel RST VMD Managed Controller 09AB" v20.0.0.1037 (13-Oct-23). With this driver the updates would always rollback, I've reproduced this issue several times on multiple cnanary builds.

If I roll back the driver to the last one which in my case is v19.5.7.1058 (29-Jun-23) the updates install fine.

《《

Basically I did the same which corrected the first boot. The duff driver had got introdused. That issue was detected in the Insider programme but not corrected. Funny enough when it's finally installed it ends up on the most recent release of "Intel RST VMD Managed Controller 09AB". Hoping 25h2 will update fine, otherwise I have a copy of the good driver.

So it's possible that going mad with updating all drivers isn't totally wise. If it's going as far as the second boot then gets an issue with the first boot you have introduced a duff driver so you need to unravel that.

I installed the big 24H2 update on my computer (HP 470 G9 laptop, Windows 11 Pro).

It failed several times at first, when I tried to install it in several different ways!

Here are the different steps:

1) It originally appeared for download on Windows Update on Nov 22. I tried to download it 2 times – the download always stopped at 8%

2) It appeared again on Windows Update on Dec 15. Now the download and installation proceeded to the end – but then the installer started automatically undoing the changes made to the computer --> reverted back to v. 23H2

3) I then tried installing from the ISO file --> failed (for some reason it reported a problem with the installation language (?) --> could not select the option at all: “Keep my files and apps”

**4) The update finally went well and without any problems with this method:**💻👍👍

Windows 11 Installation Assistant

I would like to emphasize that this is one of the three official installation methods recommended by Microsoft!

Microsoft: This is the best option for installing Windows 11 on the device you’re currently using.

https://www.microsoft.com/en-us/software-download/windows11/

Note! It is important to note that in order to proceed the installation process, everyone must first pass the WindowsPCHealthCheck (which can be launched from the link at the top of the downloaded Windows 11 Installation Assistant -application window)

Again, with all due respect, no one should have to do that. All these backward, mystery solving, multi stepped processes only prove that Microsoft and its update are useless. Do this, then do that, then take this, then take that, now do this etc. No. Microsoft has caused unknown damage to millions of computers with no explanation and surely no help. They must be held accountable. It is completely unacceptable to attempt to fix their update. If it was not ready, it should not have been released. It’s a marketing ploy to get people to buy new systems. Inexcusable.