This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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.
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,
Hi fg,
Unable to reproduce it but I'm not clean installing from USB so that might be a factor.
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.
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. 😝
I could never get that far on clean install which was on a compliant vm. The upgrade that failed was on a non-compliant vm. I did add the bypass and still no go.
MS has introduced a few new blocks this week. On the upgrade in RP 22621.754 it detected a non-compliant system and put the branding in bottom right corner.
We first seen this back in March Remove System requirements not met watermark. The same reg edit cleared this concern and WU proceeded as normal on non-compliant vm.
Regards,