Taking 9 weeks to get a second laptop upgraded from 23h2 to 24h2 using either the ISO method and the rest. This time Microsoft bless them have changed the installation using a secure booting feature of Windows 11 in the upgrade process, if it fails the process you get an error code and masses of posts to look through on help screens. Support posts all the same stuff, which doesn't work....
If you started on this early, the idea of just waiting for Microsoft to sort it out hadn't come up, and I doubt they will for tricky machines unless they tell you the secret to be covered that I found, after nine weeks, in a small corner of the internet was the solution....
Story so far, it's easy to update relatively old unsupported hardware using the server method.
www.seatcupra.net
On Windows 11 compliant hardware it is more tricky, you don't use that method, if you are lucky then it's plain sailing which it was on this laptop HP Spectre x360 2-in-1 Laptop 15-eb0xxx using the Windows 11 Installation Assistant:
The Windows 11 Installation Assistant that shouldn't lead into any nasty first stage driver issues but may not complete giving a more vague error, or it could work first time.
Known issues are posted here:
You are supposed to wait to get the update invite but if you have a mixture of old hardware and new, the unsupported hardware will never get an invite so after doing them you get on with the ones using the official download page... should say at this stage since the bugs came to light in the update Microsoft would prefer you to wait...
If you don't and want to sort it out yourself as far as possible, then you enter the fun world if it goes wrong.
support.microsoft.com
You are likely to hit this bank of codes:
You only see those if you run the ISO. Running the ISO you don't take the preferred driver update that can land you with 0xC1900101 - 0x20017 which is an incompatible driver, and you end up in the boot screen. Multiple boots... going in and finding the correct old one and getting rid of the new one. You might be fortunate and never see that.
0xC1900101 - 0x40017 is the one you might see, which means you have a non-compliant driver or a non Microsoft virus program that needs uninstalling.
You get rid of the latter first. There are techniues to find them.
Here's the secret to find the non-compliant drivers in the second boot that Microsoft's hand out don't give to staff, so it seems. Appears in here:
Second post:
>>The following tool should tell us which driver(s) is/are causing the problem:<<
It's the memory integrity readiness Microsoft tool. That which easily exams the drivers, which will lead to difficulty on the second stage boot of the upgrade. There are two versions, AMD and ARM. Pick the one for your hardware.
Worked example:
Go to CMD and run as
hvciscan_amd64.exe > output.txt
Open in notebook:
>> 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 listed....
Google gave: https://answers.microsoft.com/en-us...ble-with/1122bd64-57a7-41f7-a762-b13dac158562
Adobe DVD driver, try removing 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.
Then run the update again. In this instance, it went on to full 24h2 installation
.
The troublesome machine was HP Spectre x360 2-1 Laptop 16-f0051na, how the driver PxHlpa64 got in there pass, might have been part of the Adobe Lightroom software. Mystery. Out of 65 or so drivers, a bit tricky to find otherwise.
Essentially, as the tool throws up candidates, you check what they are from Google and try to work out why they are there. Then remove, like the example.
Best of luck, or just wait for Microsoft to sort it out... reckon it may take a time for troublesome setups.
If you started on this early, the idea of just waiting for Microsoft to sort it out hadn't come up, and I doubt they will for tricky machines unless they tell you the secret to be covered that I found, after nine weeks, in a small corner of the internet was the solution....
Story so far, it's easy to update relatively old unsupported hardware using the server method.
Windows 11 22H2/23H2/24H2 Upgrade on unsupported 64bit hardware - link
It's that time again with Windows 11 unsupported hardware. The annual release is out 22H2 so to do it you have to do the workaround. This changed from the one I put up last year, although there are others which got you from Windows 10 to Windows 11. Last years link...
www.seatcupra.net
On Windows 11 compliant hardware it is more tricky, you don't use that method, if you are lucky then it's plain sailing which it was on this laptop HP Spectre x360 2-in-1 Laptop 15-eb0xxx using the Windows 11 Installation Assistant:
The Windows 11 Installation Assistant that shouldn't lead into any nasty first stage driver issues but may not complete giving a more vague error, or it could work first time.
Known issues are posted here:
Windows 11, version 24H2 known issues and notifications
View announcements and review known issues and fixes for Windows 11, version 24H2
learn.microsoft.com
You are supposed to wait to get the update invite but if you have a mixture of old hardware and new, the unsupported hardware will never get an invite so after doing them you get on with the ones using the official download page... should say at this stage since the bugs came to light in the update Microsoft would prefer you to wait...
If you don't and want to sort it out yourself as far as possible, then you enter the fun world if it goes wrong.
Get help with Windows upgrade and installation errors - Microsoft Support
See some of the most common upgrade and installation errors for Windows 10 and Windows 11, and what you can do to try to fix them.
support.microsoft.com
You are likely to hit this bank of codes:
- 0xC1900101 - 0x2000c
- 0xC1900101 - 0x20017
- 0xC1900101 - 0x30018
- 0xC1900101 - 0x3000D
- 0xC1900101 - 0x4000D
- 0xC1900101 - 0x40017
You only see those if you run the ISO. Running the ISO you don't take the preferred driver update that can land you with 0xC1900101 - 0x20017 which is an incompatible driver, and you end up in the boot screen. Multiple boots... going in and finding the correct old one and getting rid of the new one. You might be fortunate and never see that.
0xC1900101 - 0x40017 is the one you might see, which means you have a non-compliant driver or a non Microsoft virus program that needs uninstalling.
You get rid of the latter first. There are techniues to find them.
Here's the secret to find the non-compliant drivers in the second boot that Microsoft's hand out don't give to staff, so it seems. Appears in here:
WinSetupMon.Sys Missing
Hi Group, Sorry if this post is in the wrong group or if someone has posted before. I've been trying to activate core isolation but when I activate it says it cannot do it due to incompatible drivers but does not show which driver. I've checked and updated all System Drivers to make sure that...
www.sysnative.com
Second post:
>>The following tool should tell us which driver(s) is/are causing the problem:<<
Download Memory integrity system readiness scan tool from Official Microsoft Download Center
HVCIScan is a tool that can be used to check a system for compatibility with memory integrity.
www.microsoft.com
It's the memory integrity readiness Microsoft tool. That which easily exams the drivers, which will lead to difficulty on the second stage boot of the upgrade. There are two versions, AMD and ARM. Pick the one for your hardware.
Worked example:
Go to CMD and run as
hvciscan_amd64.exe > output.txt
Open in notebook:
>> 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 listed....
Google gave: https://answers.microsoft.com/en-us...ble-with/1122bd64-57a7-41f7-a762-b13dac158562
Adobe DVD driver, try removing 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.
Then run the update again. In this instance, it went on to full 24h2 installation
.The troublesome machine was HP Spectre x360 2-1 Laptop 16-f0051na, how the driver PxHlpa64 got in there pass, might have been part of the Adobe Lightroom software. Mystery. Out of 65 or so drivers, a bit tricky to find otherwise.
Essentially, as the tool throws up candidates, you check what they are from Google and try to work out why they are there. Then remove, like the example.
Best of luck, or just wait for Microsoft to sort it out... reckon it may take a time for troublesome setups.
