BSOD. Stop code SYSTEM SERVICE EXCEPTION. What failed win32kfull.sys. Build 25227.1000 OOBE clean install from USB media.

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.

Hi Sibro,

I just tried with the Home edition only, extracted from the original MS multi-edition ISO.

Used a fully compliant Desktop DELL XPS 8940, booted from the USB and did the same sequence that I tried before, it crashed with the BSOD exactly the same way as the Pro edition. As I try to select a key in the registry it just crashes with the same BSOD as reported earlier.

I also saw a different case getting the same BSOD every time just trying to scroll on the selection for the drive where to install windows.

Note that in my case I can always reproduce the BSOD if I attempt to modify the registry after Shift + F10 and "regedit".

If I just follow the normal install procedure it proceeds normally to completion with either Home or Pro and no errors at all.

That could be the reason why MS did not catch the problem. It seems to require some unusual conditions to hit the bug.

For Johnny and yourself, VM seems to be the variable, in my case it is just the editing of the registry or scrolling on the selection for the drive, but the end result is the same BSOD. 😝🤷‍♂️

I was not expecting a different result with Home versus Pro at this stage, given that is not even installed yet.

The screwup must be in the common setup regardless of which edition I try to install. 😎

Here is the other case, I mentioned above, I get the BSOD reproduced consistently just trying to scroll to select the drive partition where to install.

Note that if I select the drive partition directly without scrolling, the bug does not happen, and I can go on formatting and installing. 🤣

You may not even have the scroll bar in your system if you don't have many disks with multiple partitions. 🤷‍♂️

On the laptop screen that you showed earlier type regedit in the command prompt, then try opening a key.

Looking more and more like a Pro version only bug

This on a VM using UUPdump ISO Home version only, no error.

Hi Sibro,

It is easy for me to try Home Edition only on the same fully compliant machine that is failing with Pro and see if it makes any difference.

I'll extract the Home edition only from the MS ISO and then try again.

I'll let you know when I'm done with the test. 😎