Can't install any Canary build past 25915

Trying to install any Canary build past 25915 will no longer work for me. The typical result is that after the first reboot, it hangs at the blue Windows logo (Zero HDD activity, but significant CPU activity, and it will persist in this state indefinitely until the system is manually rebooted).

After manual reboot, the system will automatically roll-back, and display the error:



Official builds, Release Preview builds, Beta builds, Dev Builds, and Canary builds (25915 and earlier) all install and run great.

Not a big deal obviously, given the nature of what Canary builds are and how they can be somewhat unstable. However there have now been a handful of builds released after 25915 and none of them will install. As more and more builds continue to exhibit the same behavior, I can't help but wonder if this is not a bug or fluke, but instead the result of some actual intended change.

Does anyone know what might have been changed after 25915 that could explain why none of the newer builds will install anymore?

Still having this same issue even with 25947. I can't be the only one.

Is your PC supported, what CPU do you have?

Microsoft is blocking old CPUs and chipsets from installing newer insider builds.
Microsoft might soon block force-installing Windows 11 on unsupported CPUs via bypass

To quickly check this burn a insider build on a stick and try to boot, if you get stuck at logo then your CPU might be blacklisted and there is nothing you can do for now.

Jack07 said:

Is your PC supported, what CPU do you have?

Click to expand...

I'm mainly testing new builds in a VM at this point, using Oracle VM VirtualBox. It has Windows 11 support now, with SecureBoot and TPM 2.0. Host CPU is a 5800X3D, with hardware virtualization enabled. I can install all Official builds, Release Preview builds, Beta builds, Dev Builds, and Canary builds (25915 and earlier) without using any bypass. Just nothing after 25915.

For anyone else using who is having this issue with Virtualbox, the solution is to change the chipset to ICH9. Apparently the other chipset option is no longer supported. It's running fine now with chipset set to ICH9.

Jack07 said:

Is your PC supported, what CPU do you have?

Microsoft is blocking old CPUs and chipsets from installing newer insider builds.
Microsoft might soon block force-installing Windows 11 on unsupported CPUs via bypass

To quickly check this burn a insider build on a stick and try to boot, if you get stuck at logo then your CPU might be blacklisted and there is nothing you can do for now.

Click to expand...

Hi folks
If using a VM the CPU can be set to a Virtual CPU that will work on W11 -- however even if it doesn't I still say the quickest and most fail safe way of installing windows from scratch is simply


boot up an install disk -->repair system-->command line

assign the efi (boot) partition to say S

now run this



reboot the PC and you'll be in the initial OOBE where your Windows install will complete.
Really "Seeeemplees" !! and fast too. (run the dism/Apply-image from the sources directory from the install media ) after about 5 - 7 mins of "getting ready"



You should then get the OOBE screen and be able to continue. It works also without TPM / Secure boot or even emulated TPM / sec boot.



I really can't understand why so many people think this method of install is so complicated !!!!.

Works perfectly every time on HYPER-V Windows host or KVM/QEMU on a Linux Host. Should in theory work on vmware and vbox too - but if using a Windows host and if you have W11 pro HYPER-V is streets ahead of vmware or vbox.

You can then if you like clone the VM to a physical disk - you'll need to add the Real W11 drivers but that won't be an issue normally. Just have W11 drivers from any W11 system and update manually via control panel-->system--->device manager.

When you need a NEW windows build just clone the physical machine back to the VM run WU to update and clone back to the physical disk.

Update works perfectly then via WU

e.g Dev Build




Cheers
jimbo

I had already tried a couple of bypass methods. I tried putting the Windows 10 version of the "appraiserres.dll" file into the Sources folder of the Windows 11 install files, which has been my go-to bypass method so far. I also tried copying the "install.wim" file from the Windows 11 install files into the Windows 10 install files, which has been my backup bypass method. Neither one worked.

But once I switched the chipset in Virtualbox to ICH9, it now works fine, both with the VM configured "correctly" for Windows 11 (no bypass needed) as well as with the VM configured as legacy hardware (No UEFI, No Secure Boot, No TPM) and using a bypass.

I like to have versions of the VM using legacy BIOS and a bypass because one of the things I want to keep track of is if/when Microsoft is going to crack down on installing Windows 11 on older hardware. Right now, for most people, even something like a 17 year old Q6600 computer can still make a decent office system if it has an SSD and enough RAM. A 12 year old overclocked 2500k can still play most games if it has a decent GPU, etc. But with Windows 10 support set to expire in 2025, soon the fate of these old computers will be tied to whether or not Windows 11 can still be made to work on them.

GotNoRice said:

I had already tried a couple of bypass methods. I tried putting the Windows 10 version of the "appraiserres.dll" file into the Sources folder of the Windows 11 install files, which has been my go-to bypass method so far. I also tried copying the "install.wim" file from the Windows 11 install files into the Windows 10 install files, which has been my backup bypass method. Neither one worked.

But once I switched the chipset in Virtualbox to ICH9, it now works fine, both with the VM configured "correctly" for Windows 11 (no bypass needed) as well as with the VM configured as legacy hardware (No UEFI, No Secure Boot, No TPM) and using a bypass.

I like to have versions of the VM using legacy BIOS and a bypass because one of the things I want to keep track of is if/when Microsoft is going to crack down on installing Windows 11 on older hardware. Right now, for most people, even something like a 17 year old Q6600 computer can still make a decent office system if it has an SSD and enough RAM. A 12 year old overclocked 2500k can still play most games if it has a decent GPU, etc. But with Windows 10 support set to expire in 2025, soon the fate of these old computers will be tied to whether or not Windows 11 can still be made to work on them.

Click to expand...

You can continue running VM's until almost "The end of the Universe" for legacy hard and software.

XP running perfectly with an old (Pro standard so not drm'ed) minidisc recorder --MD simple burner)




I prefer also any day the old XP interface with the lunar black theme and curved title bars. The menu system is also streets ahead of W11 --and as a VM this thing just flies even on a modest laptop.

W11 pro IMO is somewhat doggy as an OS - runs a bit like trying to swim in a pool of molasses when you are also used to a lean and mean linux distro. That said Windows isn't all bad - but Ms does IMO seem to be concentrating on the wrong things rather than concentrating improving the performance of the OS and eliminating defects.

They also seem to be totally failing in any sort of sensible regression testing as sometimes a fix to one defect causes an other earlier one to re-appear.


cheers
jimbo

Bumping this thread due to same issues:

I have tried everything suggested, but the last 3 or 4 Canary versions of Windows Insider builds have failed to boot on VirtualBox, whether it's booting from the DVD ISO itself, or trying to boot after using DISM to image Windows onto the drive as outlined by Jimbo above. I've tried using legacy BIOS as well as UEFI, I've tried messing with so many settings but it just doesn't boot now. It will freeze at the "VirtualBox" logo when using UEFI and the Windows 11 logo when using Legacy BIOS. There is then no disk activity showing on the virtual LEDs in the bottom right. I've also tried with the ICH9 chipset (which a few weeks back did fix this issue, but now even that doesn't work either)

The host system is an i7-10700F with 32GB RAM.

Any ideas? Thanks

That's odd. I'm running two Canary VMs on VirtualBox at the moment. One is configured "correctly", with UEFI, TPM, etc, so that I can install new versions directly from Windows Update with no bypass. The other is installed with legacy bios and mainly used to test and see if Microsoft is working on any changes to the ability to install Windows 11 on older hardware (via bypass). Ever since they broke the "appraiserres.dll" bypass, I've been using the "/product server" bypass without issue.

I'm just curious, have you tried an upgrade instead of doing a fresh install? Install Windows 10 or an earlier version of Windows 11 and then upgrade to the latest Canary build instead of doing a fresh install (use bypass if necessary).

My host system is a lot different; running a Ryzen 5800X3D

Also, very occasionally one of the VMs will seem to freeze. If I pause the VM, wait 10-15 seconds, and then unpause the VM, it will usually "unfreeze". Not sure if that is applicable to your situation though.

GotNoRice said:

That's odd. I'm running two Canary VMs on VirtualBox at the moment. One is configured "correctly", with UEFI, TPM, etc, so that I can install new versions directly from Windows Update with no bypass. The other is installed with legacy bios and mainly used to test and see if Microsoft is working on any changes to the ability to install Windows 11 on older hardware (via bypass). Ever since they broke the "appraiserres.dll" bypass, I've been using the "/product server" bypass without issue.

I'm just curious, have you tried an upgrade instead of doing a fresh install? Install Windows 10 or an earlier version of Windows 11 and then upgrade to the latest Canary build instead of doing a fresh install (use bypass if necessary).

My host system is a lot different; running a Ryzen 5800X3D

Also, very occasionally one of the VMs will seem to freeze. If I pause the VM, wait 10-15 seconds, and then unpause the VM, it will usually "unfreeze". Not sure if that is applicable to your situation though.

Click to expand...

Thanks for getting back to me.

This is odd then, I just can't get it going. It was a good idea of yours to try it as an upgrade, so I tried downloading the latest Canary build ISO and running "setup.exe /product server" (which I hadn't used before but which I heard about the other day) and although setup ran, on the first boot it again hangs at the VirtualBox UEFI logo screen, with no spinning wheel to show it's loading. Upon resetting the VM, it then did start Windows 11, but only to do the rollback process.

I also tried from my new installation of 11 on VirtualBox to enrol on the Insider Programme and the Canary builds. Windows Update starts to download the latest Canary build, but at 8% comes up saying the PC is not supported due to no secure boot and no TPM. This is where I'd usually copy "appraiserres.dll" to the Windows.~BT sources folder and re-run Windows Update, but now this doesn't work either.

alex_ncfc said:

Windows Update starts to download the latest Canary build, but at 8% comes up saying the PC is not supported due to no secure boot and no TPM. This is where I'd usually copy "appraiserres.dll" to the Windows.~BT sources folder and re-run Windows Update, but now this doesn't work either.

Click to expand...

Yes, that workaround last worked with Canary build 25951.1000. MS have stopped it working for the newer Canary builds, 'setup /product server' is now the last remaining known workaround, and you can't use that one with Windows Update.

The appraiserres workaround still works for the latest Dev, Beta, Release Preview, and RTM builds.

Bree said:

Yes, that workaround last worked with Canary build 25951.1000. MS have stopped it working for the newer Canary builds, 'setup /product server' is now the last remaining known workaround, and you can't use that one with Windows Update.

The appraiserres workaround still works for the latest Dev, Beta, Release Preview, and RTM builds.

Click to expand...

Thanks for the heads up.

Looks like my hobby of testing Canary Insider builds on VirtualBox have come to an end then. For whatever reason, as soon as it reboots after the first phase of setup (so when I upgrade a standard Windows 11 install using the latest Canary ISO, using the /Product server switch), it just hangs at the logo screen. It's so strange how this was also happening 3 or 4 weeks ago with Canary builds, but when changing the chipset to ICH9 in settings, it fixed it. Now that doesn't work either.

Very weird.

These are the settings that I'm using that still work with the /product server bypass.

GotNoRice said:

Very weird.

These are the settings that I'm using that still work with the /product server bypass.

Click to expand...

Thanks @GotNoRice , my settings are all identical apart from you have the PAE/NX enabled (which I didn't) and the VT-x box disabled, or should I say greyed out, but mine enabled. I've also mainly been trying this with EFI BIOS enabled, so will try using legacy BIOS.

Edit: Nope, still doesn't work. Not a clue why.

On 25977 i had to use setupprep.exe /product server

setup.exe /product server ...did not work this time.

Whackbag said:

On 25977 i had to use setupprep.exe /product server

setup.exe /product server ...did not work this time.

Click to expand...

Very weird. For me, in an administrator Powershell window, I typed "./ setup.exe /product server" (without the quotes) and it worked. Were you using powershell (with admin privileges) or the regular command prompt?

Very strange. I have had issues installing the last two versions of win can 25977 It says must secure secure boot. I have secure boot and its on via the bios. I just upgraded to Rufus 4.3 and ran with removing all restrictions like always. I can install older versions not the last two. It looks like I am not the only one. I see a lot about VM but I stopped using any type of VM a long time ago. Would this be the same issue I read above about the CPU being black listed? I only get one message, not a list like I used to.

GotNoRice said:

Very weird.

These are the settings that I'm using that still work with the /product server bypass.

View attachment 74799View attachment 74800View attachment 74801

Click to expand...

Back to this again, I've still been trying to get this figured out using all sorts of different combinations of options in VirtualBox, and I've found one which (sort of) works, which is odd as I'm pretty sure I've tried it before, but basically I have it set to ICH9 for the chipset (as already suggested) but have to turn off both "Enable Nested VT-x/AMD-V" under the Processor tab, and untick "Enabled Nested Paging" under the Acceleration tab. So no boxes under the Processor or Acceleration tab are ticked. Now rather than just a Windows logo with no spinning loading wheel upon booting the 25977 build ISO, I get the spinning wheel and it starts to load the installer.

Great.

Apart from it is horrendously slow and all manner of random errors seem to happen - sometimes it locks up on the spinning wheel, sometimes it goes to a BSOD with the face (and a different error each time) and sometimes it does actually reach setup, but locks up after selecting which edition of Windows 11 to install.

So I thought I'd solved it but the speed is awful with those two tick boxes disabled, and these errors seem so random. Also, it's not due to it being a Canary build, as I've tried this method (with those CPU options disabled in settings) for the latest 23H2 ISO of Windows 11, and exactly the same thing happens - slow, with a multitude of errors or lockups.

Is there anything else I can try for this? I did think of trying to get it going in QEMU, but the frontend tool QtEMU just doesn't work at all for me, and when using the command line to launch QEMU with the various options, I can get the ISO to show the boot logo and spinning wheel, but when it fades out, it just stays on a black screen.

GotNoRice said:

Very weird.

These are the settings that I'm using that still work with the /product server bypass.

View attachment 74799View attachment 74800View attachment 74801

Click to expand...

Hi guys, sorry for my ignorance... but this software... i view in the past but not remember... how, when why... part of package... What software should I look for? Windows Can? My memory is corrupted... too many write/read :)

PS: Stupid question i made... VM forms, time i not use, i add all Canary to my live PC and i play games, software etc... and about me the configuration of VM... probably 2 years i not view...

Anyway, my case is RISKY... using Canary on live machine... IS A RISK WORK... yes, i have all backup READY from latest "normal release channel" and all software, passwords & C. but i prefer in this way. Risk job yes but in this way i add various variables to OS, having installed games, softwares of various types, etc... in case FEEDBACK.