Windows 11, version 24H2 won't install

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.

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

24h2 doesn't install I've tried everything multiple times. Also it uaed 10gb data trying to update to 24h2 and didn't work. Microsoft is their own little climate change monstrosity by the looks of it. There's literally millions of people trying to upgrade to 24h2 and they are unable to yet Microsoft is using billions of gb of data with these failed attempts. Thanks for the global warming and climate change Microsoft.

It’s not published more because that’s Microsoft’s job to NOT have users do that. With all due respect, you wrote five miles of instructions and expect people to do that? There are operating systems crashing everywhere, “ Oh, let me basically rebuild my entire computer because of Microsoft’s ineptitude.” No, this is wrong. If you bought a car and the dealership told you to remove all four tires, wait 2 hours and put them back on for it to run correctly, would you do that? I appreciate your knowledge and sharing, but this is Microsoft’s mess and surely a class action suit to follow.

Hello, Fonzeh

Welcome to the Microsoft Community.

Hello, thank you for your feedback on your issue here, it seems that your current attempts to update win11 24H2 are not installing properly.

First of all, thank you for your feedback here, it seems that your current attempts to install manually using the ISO have also failed.

There may be some system issues, you can try to fix your system and drivers by following the steps below:

1. Clear Windows Update Cache

Sometimes corrupted update files can cause the installation to fail, and clearing the Windows Update cache may help:

Stop the Windows Update service:

Open Command Prompt as an administrator (right-click the Start menu > select Command Prompt (Administrator) or PowerShell (Administrator)).

Enter the following command:

net stop wuauserv

Delete the update cache:

Go to the C:\Windows\SoftwareDistribution\Download folder and delete all files in it.

Restart the Windows Update Service:

Enter the following command:

net start wuauserv

2. Run DISM and SFC scans

Corrupt system files may prevent the update from installing. Running a DISM (Deployment Image Service and Management Tool) and SFC (System File Checker) scan can help fix these issues:

DISM:

Open a command prompt as administrator.

Enter the following command:

DISM /Online /Cleanup-Image /RestoreHealth

This may take some time, please be patient.

SFC:

After DISM is complete, type:

sfc /scannow

Let it finish and then try the update again.

Disclaimer: Running Microsoft Safety Scanner can help you check if the system is disturbed or malicious software exists. To avoid any trouble for you, please back up all your personal files first to ensure you do not lose data.  

 

3. Updating Drivers

Make sure your drivers, especially the graphics card and chipset drivers, are up to date. Outdated drivers may prevent the update from installing. You can visit the official website of the brand of your computer to download them.

After that you can try the override installation method to repair your system and install 24H2.

Let’s try performing an in-place install or in-place upgrade which will refresh your Windows files and operating system without removing files or applications. That being said, we always recommend that if you have important data, you should back it up before making large system changes. If you want to back up your data first, please do so. Once you are done backing up, you can follow the steps in the following guides: How to run In-place upgrade in Windows 11 - Microsoft Community 

Best regards

Bobhe | Microsoft Community Support Specialist

3. is not very good. I been reading fixes for 9 weeks to one of my laptop issues.

Essentially you got the safe boot issues on the first boot and Microsoft pushes drivers that don't work. Had that. The ISO where is says select defaults... no don't update them you get duff ones. Always change this setting not to recommended.

Then the failed second boot with suspect drivers or virus program. Endless do this that and the other as fixes. There is a simple Microsoft tool that can be used to identify duff drivers in the second boot. You just run it and pipe out the results and look at the drivers and Google them.

That tool is this:

Memory integrity system readiness scan tool

>> Version: 10.0.25884.1000 Date Published: 6/15/2023 File Name: hvciscan_amd64.exe hvciscan_arm64.exe File Size: 41.9 KB 21.9 KB The memory integrity system readiness scan tool, hvciscan_amd64.exe and hvciscan_arm64.exe, is used to check a system for compatibility with memory integrity. Memory integrity is a virtualization-based security (VBS) feature available in Windows 10, Windows 11, and Windows Server 2016 or higher. Memory integrity and VBS improve the threat model of Windows and provide stronger protections against malware trying to exploit the Windows kernel. VBS uses the Windows hypervisor to create an isolated virtual environment that becomes the root of trust of the OS that assumes the kernel can be compromised. Memory integrity is a critical component that protects and hardens Windows by running kernel mode code integrity within the isolated virtual environment of VBS. Memory integrity also restricts kernel memory allocations that could be used to compromise the system, ensuring that kernel memory pages are only made executable after passing code integrity checks inside the secure runtime environment, and executable pages themselves are never writable. The memory integrity system readiness scan tool notifies you if the device has any known compatiblilty issues. For more information about the types of issues that the tool may report, see https://learn.microsoft.com/windows-hardware/design/device-experiences/oem-hvci-enablement. <<

It worked a dream.

This my worked example that fixed it for me:

We downloaded hvciscan_amd64.exe

Go to CMD and run as hvciscan_amd64.exe > output.txt

Open in notebook and gave: >> VbsGetIssues: 0x00000000 VbsIsRecommended: 1 HVCI incompatible driver scan start... HVCI: "C:\WINDOWS\System32\Drivers\PxHlpa64.sys" failed with compliance failure mask 00000202 HVCI: Driver scanning complete HVCI: scan get result failed. <<

PxHlpa64.sys was the only troublesome driver....

Google gave: https://answers.microsoft.com/en-us/windows/forum/all/new-pc-has-pxhlpa64sys-driver-incompatible-with/1122bd64-57a7-41f7-a762-b13dac158562

Adobe DVD driver decided to remove it:

From an Admin Command Prompt, run: reg export "HKLM\SYSTEM\CurrentControlSet\Services\PxHlpa64" C:\PxHlpa64.reg

You should see the message "The operation completed successfully."

Then, run these two commands: sc.exe delete PxHlpa64

ren C:\WINDOWS\system32\drivers\PxHlpa64.sys PxHlpa64.sys.old

Restart Windows.

The do the 24h2 update again. This exams the failed second boot drivers.

I don't why this isn't published more !.