Hi fg,
Unable to reproduce it but I'm not clean installing from USB so that might be a factor.
BSOD. Stop code SYSTEM SERVICE EXCEPTION. What failed win32kfull.sys. Build 25227.1000 OOBE clean install from USB media.
![](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)
Anonymous
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.
Windows Insider program | Windows Insider preview | Install, activate, and Windows update
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.
52 answers
Sort by: Newest
-
Anonymous
2022-10-20T18:03:46+00:00 -
Johnny55 5,155 Reputation points Volunteer Moderator2022-10-20T18:00:01+00:00 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,