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.
I just tried the 22623.875 ISO just downloaded from uup-dump and that is still good, could not reproduce the BSOD I get on Dev 25231.
Perhaps they did not pick up the bug yet. 🤣🤣🤣🤷♂️
We'll see what happens with next Dev build next week. 😎
Good news. 👍
Looks like they are propagating the bugs to the other builds, but they seem to forget to propagate the fixes. 🤣🤣
I have not seen that BSOD on 22623 because normally I don't use a third-party utility for backup and restore.
Hi fg,
Maybe not.
I think it goes much deeper, something to do with the latest WinPE (Windows Preinstallation Environment) thus affecting latest builds.
I will give the old Windows Image Backup program a go myself if this problem continues.
I just tried the 22623.875 ISO just downloaded from uup-dump and that is still good, could not reproduce the BSOD I get on Dev 25231.
Perhaps they did not pick up the bug yet. 🤣🤣🤣🤷♂️
We'll see what happens with next Dev build next week. 😎
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more