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.
Most users may not do Shift + F10 but scrolling to pick the drive is pretty common and that crashes too.
Is never a big impact if it does not affect you. 🤣🤣🤣
That is not the point.
It is a new bug that MS just added in this Build, they need to fix it. 😝😝🤐🤐
If you need to scroll to pick a drive you're most likely clean installing.
I could be wrong but it doesn't affect you either, you didn't need to clean install did you?
I didn't say otherwise.
Maybe when you downloaded again the home edition from uup-dump the code has been changed in the MS servers, who knows they change those files all the time.
Maybe, really no need to speculate any further.
Besides, regular users hardly ever clean install or use Shift + F10 so no big of an impact.
Most users may not do Shift + F10 but scrolling to pick the drive is pretty common and that crashes too.
Is never a big impact if it does not affect you. 🤣🤣🤣
That is not the point.
It is a new bug that MS just added in this Build, they need to fix it. 😝😝🤐🤐
Maybe when you downloaded again the home edition from uup-dump the code has been changed in the MS servers, who knows they change those files all the time.
Maybe, really no need to speculate any further.
Besides, regular users hardly ever clean install or use Shift + F10 so no big of an impact.
That could be the reason why MS did not catch the problem. It seems to require some unusual conditions to hit the bug.
IDK what to tell you, I can't reproduce the error using Home Edition, only with Pro Edition on both the laptop and on a VM, the proof is on the screenshots.
Maybe when you downloaded again the home edition from uup-dump the code has been changed in the MS servers, who knows they change those files all the time.
I'm now using the original MS official ISO and get the exact same failure with either Home or Pro editions.
Also, I found an easier way to get the error by simply trying to scroll on this screen as I mentioned on previous post.
Pretty consistent with either Home or Pro. 🤷♂️
Clearly if you don't have the scroll bar on the right for this screen that does not apply. 🤣🤣🤣
That could be the reason why MS did not catch the problem. It seems to require some unusual conditions to hit the bug.
IDK what to tell you, I can't reproduce the error using Home Edition, only with Pro Edition on both the laptop and on a VM, the proof is on the screenshots.