Solved Potentially bad news installing on unsupported hardware with latest Dev build

I have Win 11 Dev Channel Insider Build running in a VM using the pre-release VMware Workstation Tech Preview. When I attempted to upgrade to build 25179, it fails with a green screen BSOD during installation reporting an unsupported processor.

As a test, I downloaded the ISO for this build directly from Microsoft and tried a clean install. No go, same thing (except that it is a blue screen rather than green).

So, I tried again, this time entering "reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f" at the first static screen to bypass the CPU check. Bad news - it fails again.

I should point out that the underlying physical machine does have a fully supported CPU.

I'm wondering if anyone has tried to install the dev build on a real physical computer that does not meet the CPU requirements to see if the workarounds still work on physical hardware. I'll try this in the morning, but was just curious to see if anyone has already tried this.

hsehestedt said:

I have Win 11 Dev Channel Insider Build running in a VM using the pre-release VMware Workstation Tech Preview. When I attempted to upgrade to build 25179, it fails with a green screen BSOD during installation reporting an unsupported processor.

As a test, I downloaded the ISO for this build directly from Microsoft and tried a clean install. No go, same thing (except that it is a blue screen rather than green).

So, I tried again, this time entering "reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f" at the first static screen to bypass the CPU check. Bad news - it fails again.

I should point out that the underlying physical machine does have a fully supported CPU.

I'm wondering if anyone has tried to install the dev build on a real physical computer that does not meet the CPU requirements to see if the workarounds still work on physical hardware. I'll try this in the morning, but was just curious to see if anyone has already tried this.

Click to expand...

Note - NOT for Unattended installs as there's a bit of manual stuff needed here.

I tried on Intel laptop with GEN 6 i5 processor (not supported)

What I did was install on VM with KVM/ QEMU on Arch Linux (also works on Debian Bookworm or any other distro where you can install package swtpm / swtpm-tools for a TPM v2 emulator -- the IBM one and can "poodlefake the CPU" on the VM to one that IS supported) and package ovmf for sec boot /uefi for the VM.

Then simply image it with macrium and restore to appropriate real system. Update the drivers via WU, also "Install from this computer" - from drivers (physical) from either a working W10 real install image or vhdx file mounted as a disk and update each missing driver from the other systems system32/Driverstore directory. If the system won't boot ist time round boot any windows install media or other media that gives access to windows command mode and re-install the bootloader via bcdboot (point to the windows directory of the system you want to install and ensure the EFI partition is mounted as a separate partition - diskpart is the tool needed there.

In KVM this is the CPU I'm using that restores to a Real machine -- the dropdown also allows you to select a whole different set of them - the best one is to say "Hypervisor Default" which in my case came out as qemu64.



Have fun !!! Its a bit long winded this way but so far it's still working.

Cheers
jimbo

Thanks, Jimbo. I should be sleeping, but this was bugging me way too much. So, I just performed a clean install on an 11 year old laptop. No TPM, no UEFI BIOS, so that also means no secure boot, and an intel i5 M 450 CPU. It installed flawlessly.

Time to file another report with VMware.

I guess I'll also test this on Hyper-V in the morning.

Phew! Was getting a bit worried!

Check the following. It's a sweet lil utility. Yes I know there many ways to bypass the sys checks.

MediaCreationTool.bat/bypass11 at main · AveYo/MediaCreationTool.bat · GitHub

Works great.
Tim

---

Get 11 on 'unsupported' PC via Windows Update or mounted ISO (no patching needed)​

Step 1: use Skip_TPM_Check_on_Dynamic_Update.cmd to automatically bypass setup requirements
It's a set it and forget it script, with built-in undo - v7 using more reliable /Product Server trick
V9 rebased on cmd due to defender transgression; skips already patched media (0b)

Step 2: use OfflineInsiderEnroll to subscribe to the channel you want
while on 10, use BETA for Windows 11 22000.x builds (release), DEV for Windows 11 225xx.x builds (experimental)

Step 3: check for updates via Settings - Windows Update and select Upgrade to Windows 11

Get 11 on 'unsupported' PC via MediaCreationTool.bat​

MediaCreationTool.bat creates 11 media that will automatically skip clean install checks
Auto Upgrade preset, or launching auto.cmd from the created media will automatically skip upgrade checks
Running setup.exe from the created media is not guaranteed to bypass setup checks (it should for now)
To NOT add bypass to the media, use MCT Defaults preset or rename the script as def MediaCreationTool.bat

Regarding the bypass method, for a more reliable and future-proof experience,
clean installation is still handled via winsetup.dll patching in boot.wim
upgrade is now handled only via auto.cmd with the /Product Server trick
Just ignore the 'Windows Server' label, please!
NEWS: temporarily added back my old-style 0-byte bypass as it still works on release

Click to expand...

Skip_TPM_Check_on_Dynamic_Update.cmd acts globally and skips setup.exe upgrade checks as well
regardless of mounted iso / usb media already having a bypass added or not

Already have a 11 ISO, USB or extracted Files and want to add a bypass​

Use Quick_11_iso_esd_wim_TPM_toggle.bat from the confort of right-click - SendTo menu


Switches installation type to Server skipping install checks, or back to Client if run again on the same file, restoring hash!
directly on any downloaded windows 11 iso or extracted esd and wim, so there's no iso / dism mounting
defiantly quick

Works great with business / enterprise media since it comes with ei.cfg so setup won't ask for product key at start
for consumer / core media you can add a generic EI.cfg to the media\sources yourself with this content:

[Channel]
_Default

if setup still asks for product key, input retail or gvlk keys found in media\sources\product.ini
gvlkprofessional=W269N-WFGWX-YVC9B-4J6C9-T83GX gvlkcore=TX9XD-98N7V-6WMQ6-BX7FG-H8Q99
gvlkenterprise=NPPR9-FWDCX-D2C8J-H872K-2YT43 gvlkeducation=NW6C2-QMPVW-D7KKK-3GKT6-VCFB2 etc.

Skip_TPM_Check_on_Dynamic_Update.cmd acts globally and skips setup.exe upgrade checks as well
regardless of mounted iso / usb media already having a bypass added or not

Offline local account on 11 Home / Pro​

MediaCreationTool.bat creates media that re-enables the I dont have internet OOBE choice (OOBE\BypassNRO)
It does so via AutoUnattend.xml, inserted into boot.wim to not cause setup.exe issues under windows
More conveniently can be placed at the root of 11 media, along with auto.cmd to use for upgrades
Should work with any 11 Release (22000.x) or Dev (22xxx.x) media - and it hides unsupported PC nags as a bonus
If you have already connected at OOBE, can try email: a password: a to switch to local account

Manage and troubleshoot Windows Update on any windows version and edition​

Use windows_update_refresh.bat to clear pending updates (including sneaky feature upgrades)
Use windows_drivers_update_toggle.bat to block driver updates even on Home editions
Use windows_feature_update_toggle.bat to block feature upgrades on 1507 - 21H2 even on Home editions!

---

hsehestedt said:

I have Win 11 Dev Channel Insider Build running in a VM using the pre-release VMware Workstation Tech Preview. When I attempted to upgrade to build 25179, it fails with a green screen BSOD during installation reporting an unsupported processor.

As a test, I downloaded the ISO for this build directly from Microsoft and tried a clean install. No go, same thing (except that it is a blue screen rather than green).

So, I tried again, this time entering "reg add HKLM\System\Setup\LabConfig /v BypassCPUCheck /t reg_dword /d 0x00000001 /f" at the first static screen to bypass the CPU check. Bad news - it fails again.

I should point out that the underlying physical machine does have a fully supported CPU.

I'm wondering if anyone has tried to install the dev build on a real physical computer that does not meet the CPU requirements to see if the workarounds still work on physical hardware. I'll try this in the morning, but was just curious to see if anyone has already tried this.

Click to expand...

I have vmWare workstation pro and i run win 11 just fine and my pc specs have Celeron G540, 12 gb ram and i run it too on my other pc with Core i3 3220 and 8 gb ram. Since i put it on hdd it slowed down but on ssd perfomance bumped up a little.

iWishPc said:

I have vmWare workstation pro and i run win 11 just fine and my pc specs have Celeron G540, 12 gb ram and i run it too on my other pc with Core i3 3220 and 8 gb ram. Since i put it on hdd it slowed down but on ssd perfomance bumped up a little.

Click to expand...

Yeah, that quote from me was over a year ago. That issue has long ago been addressed

iWishPc said:

I have vmWare workstation pro and i run win 11 just fine and my pc specs have Celeron G540, 12 gb ram and i run it too on my other pc with Core i3 3220 and 8 gb ram. Since i put it on hdd it slowed down but on ssd perfomance bumped up a little.

Click to expand...

hsehestedt said:

Yeah, that quote from me was over a year ago. That issue has long ago been addressed

Click to expand...

If you have unsupported physical hardware - then :

Easy enough if you can create a VM first -- then simply clone it to the real machine and update drivers. If necessary update bootloader via bcdboot.exe - epending on what VM system you are using this step might not be necessary.

Still working on all latest insider builds - running (as real mainstalls) on a laptop with unsupported CPU.

Running dism.exe /Apply-Image also is still working whether on a rteal or VM. If you use this method then you will need to install the boorloader too (bcdboot.exe)

Cheers
jimbo