Is this chipset blocking also present on current Dev Channel builds? If not, then this is Win12-specific.
I don't think the block is on chipsets, but rather on CPUs (which in turn means chpisets), but everything is possible It's what's written on the title of this thread, anything above 259xx is blocked, anything below isn't.
Nope. Only on 25921 (that's where we saw it happen) and up. Check that thread for correct information.
Ooops... Sorry to those who replied to this topic/thread. Thanks... for replying. Just made a flight over the comments.. My main system is a Asrock G41C-GS R2.0 with Intel G41... yes... ancient... BUT WINDOWS 11 does run fine. I did refurbish a laptop recently... It has another ancient chipset.... the laptop make/model is Acer Aspire 5930G... intel PM45/ICH9M. Both systems have cheap SSDs which make them fast. I also have another system based on intel G41 and it has build 25357... which needs upgrading as well. Build 22621 does run fine on these computers. I did not upgrade from 22621 to 25393 right away. My upgrade path was... 22621 -> 22622 -> 25352 -> 25357 -> 25393 -> can't install 25398 no Professional SKU (possibly no timebomb). I can't rollback. If I try to upgrade from build 25393 to build 25398, it will see my system has Pro sku while 25398 has server sku... It will offer to clean install just. I MOVED TO build 253xx because apparently Microsoft fixed a bug with nvidia gpus... where we let the screen sleep because we step away and when we use these system, the screen gets frozen.... we need to use CTRL+ALT+DELETE and then press ESC to get back the screen. During my testing, none of builds 259xx will allow me to boot from ISO nor allow in-place upgrade sucessfully (It will do the install inside windows and then reboot but it won't show the circle and we need to press reset button). The builds 235xx do work fine but I can not downgrade. I tend to reuse my old systems because they work just fine. Microsoft is making us spend more money on newer hardware and God knows if they will last years or just weeks. Yes, should buy a brand new system BUT i'm not ready yet.
I been reading the thread from the link you posted but I'm lost. Not sure what should I do. I currently have build 25393 installed, it has a timebomb. The build 25398 has no Pro.sku, just 2 skus for server and azure something. Should I turn build 25393 from pro to server and upgrade and then switch to pro again? I'm not dumb. I'm just not so aware of the magic of sku switching.
just switch to a non timebombed edition, Azure HCI is perfect for the scope. Practically same capabilities of server, no online activation needed, and persistent activation
So are you saying that I should turn the installed Professional edition into Azure, upgrade from 25393 to 25398, and then turn it back to Pro? os: Microsoft Windows 11 Pro 64 bits (10.0.25393.1) up: 3hrs 21mins 11secs cpu: Intel(R) Core(TM)2 Duo CPU P8800 @ 2.66GHz (x64) at 2667MHz (4% Load) ram: 2603/4090.9MB (63.64%) ██████░░░░ gfx: Generic PnP Monitor on NVIDIA GeForce 9600M GT 512MB res: 1280x800 32bit 60Hz hdd: C:\ 75.7GB/107.78GB net: Marvell Yukon 88E8071 PCI-E Gigabit Ethernet Controller - 1000MB/s 0B In 0B Out osinstall: Wed Jun 14 23:19:43 2023 (9wks 3days 16hrs 38mins 45secs ago)
There is some misunderstood somewhere. According to the specs of this machine I am typing on, Windows 11 Professional build 25393 was installed over 2 months ago. I can not move to build 25398. The iso file only comes with 2 editions. I would somehow need to turn my windows 11 pro into azure or server and then after upgrade, downgrade to pro. I do not wish to use a server edition. Never intented to do so. Back then, none of us didn't know that this build would lead to a server edition.
Couldn't install any recent Canary builds on MBR disk. Converted it to GPT and install went flawlessly. They must've blocked it from installing on disks with MBR partitioning. I'm afraid you can't do an in place conversion without losing your data
Yeh.. converting MBR to GPT is dangerous. I do not want to lose my data. Only thinking about it and then recoverying it and then reinstall everything... it would be a big big pain. You are not telling what specs are your PC nor builds. It must not be the MBR/GPT thing. I started a VM with efi and a blank vdi, it didn't show the spinning circle. It has to be some chipset/cpu blockage like some said posts above. Unfortunatelly it is/will not easy to fake a real hardware.
Why would you even decide to run a Canary build on your only machine with all your important stuff on it in the first place?? That's simply insane!
changing MBR to GPT is not fixing the issue preventing 259xx to boot on old hardware (Q9650/25393 here)
I wanted to try a newer build and I saw that it also fixed the screen freeze with nvidia gpus. I don't remember if back at 25352 there was the 234xx... Now it's a bit later.
I am not sure why freaking MS added Pro skus to 253xx... if it was for a server release. System1: Build 25393 / Asrcok G41C-GS R2.0 / Intel Q9550 / 8GB RAM DDR3-1333 at 1Ghz / 120GB SSD+HDDs / Ati Radeon Hd 4650 System2: Build 25393 / Acer Aspire 5930G / Intel P8800 / 4GB DDR2-800 / 120GB SSD / Nvidia 9600M System3: Build 25357 / MSI G41TM-E63 / Intel Q6700 / 4GB DDR2-800 / 120GB SSD+HDDs / Nvidia 8500 GT All Windows 11 Professional All these systems need to move on before the timebomb explodes. I do have other unsupported PCs ... all of them are on 22631 build. I do have a mini pc with x5-z8350 from intel and it does seem to boot with 259xx, it has GPT on the emmc... but I think if I blank the emmc, it would boot from the pendrive created by rufus anyways.