Sorry for the late reply. I'm already running Win 11 in a VM in VMWare - I don't think VMWare is as configurable for virtual processors unfortunately :(
I'm getting the unsupported processor gsod again with this update (even with the override registry key). Looks like MS are finally killing off any kind of support for older processors as of the previous build (25179) :(
It looks like the issue was that you can only edit within 60 mins of your post.
The real problem is the GSOD during update (this is the first update with this issue) - does anyone have any ideas?
Sorry for the double post (can't find a way to edit the one above).
Just to add, I've been keeping up with the dev builds on the VM for a long time and this is the first update with this issue.
My guess (just a guess though) is if MS suddenly get a load of error feedback, but pretty much all from group B of A/B (even though its doesnt appear to be related to the new features), theyll have a abetter idea of what broke.
I'm getting exactly the same steps on VMWare. (Also tried with firewall and AV disabled).
Also my green screen is blue, even though I'm on dev channel - is this a setting somewhere?
I hadn't tried the iso method but mine too failed (at the last minute like some others are reporting) for the 22598 series but this update went without a hitch. Oddly I briefly spotted the (blue) BSOD for one attempt - I thought these were supposed to be green for the dev builds.
Also are the...