@Johnny_55, @CrazyKats,
Here is the link to the FBH report:
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Has anybody seen this problem trying to do a OOBE clean install with Build 25227?
Both the MS official ISO 25227 and the one downloaded from UUP-DUMP have this new issue causing a BSOD during OOBE procedure.
Stop code SYSTEM SERVICE EXCEPTION
What failed win32kfull.sys
I could repeat the same problem on a desktop and a laptop. This is a new bug with latest Build 25227.
Same procedure works fine with previous ISO 25217 or any older Dev one.
Easy to reproduce every time with Shift +F10 and regedit just trying to modify any registry.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi fg,
Unable to reproduce it but I'm not clean installing from USB so that might be a factor.
I think it only happens after you boot from the installation media.
It is definitely a new bug added with this Build 25227. 😝
Good afternoon fg,
Yes, I can confirm same issue attempting to do a clean install into my test vm. I also had one vm that just would not upgrade with the Official ISO. The other vm did upgrade with the ISO. There is no way to start fresh with this useless ISO.
Regards,
Thanks Johnny,
for confirming the same bug. At first, I thought I had a bad ISO from MS, but I got the same issue with the one downloaded from uup-dump
Your snapshot is much cleaner than my fuzzy unreadable picture. 🤣😎
I had no problem doing the upgrades with the ISO on Desktop or Laptop.
Just got the problem solid with clean install when I wanted to use Shift + F10 and regedit.