Replies

There is an update now KB5050411 that replaces KB5048239. Problem looks solved now. KB 5050411 is part of the regular monthly Windows update cycle, rolled out today.
<h1 id=”page-header” class=””></h1>

3 users thanked author for this post.

Rob Kay, Chris B, castiel

Thanks for the link. I’ll read through, but give-up with the current hardware.
I remember to have seen a VM solution from Oracle and a free ‘for test only’ early Windows11 virtual machine. Maybe that one will update to the current version 22H2? I can run the VM on my more capable laptop. We’ll see…

I have tried to install Windows 11 on a desktop PC with Windows 10 Home 22H2 64-bit following the procedure in the link to scottiestech.info without success.
Some keypoints worth mentioning IMHO:
– the system BIOS has to support UEFI / Secure Boot. This because Windows 11 requires UEFI / Secure Boot
– the Windows 10 disk must be a GPT disk, not MBR. A GPT disk needs UEFI to be able to boot from.
– the Windows 10 disk must have a system reserved partition of 450 – 500 MB. Win11 will install nearly completely, but in the end will fail with a ox8007000x … error if this partition has a smaller size.
– the default setting for the boot type in Rufus which is used to prepare the tweaked Win11 install medium is UEFI. The pitfall here is that the USB stick you have prepared with Rufus will only boot on a UEFI system. No problem however, you can mount the USB stick and run setup.exe from there for an upgrade install to Win11 with option to keep personal files and apps or not. If you want a clean install you need a bootable USB stick. OK, you can tell Rufus to use the ‘old’ BIOS boot mode while preparing the tweaked Win11 install medium – it will boot on a BIOS-only (non UEFI capable) system, it will install Win11, but Windows 11 will not start because no UEFI / Secure Boot.

My Win10 system has no UEFI / Secure Boot option in the BIOS settings and the Win10 system disk I tried to upgrade to Win11 using the scottiestech procedure is MBR and not GPT. Converting MBR to GPT without data loss is an exercise on itself, but is of no use here because GPT requires UEFI to be able to boot from.
Guess the result after several retries… Still on Windows 10 – no problem, I wanted some kind of a Win11 test system. Learned a lot. Will have to look around for compatible hardware.

My apologies for maybe being a littlebit off-topic here. I had to reinstall my Windows 7 64-bit SP1 and used the non-destructive (update) install with great success. Data, all my programs and settind kept alive. My question is about IE. The reinstall put back version 9 and my question to Susan is if it is without issues now to install version 10, or even version 11. Both are offered by Windows update. And if I go to version 11, is it advisable to first install version 10, install all security patches for it and then version 11, etc.?
I appreciate your colums about (security) updates very much and I thank you for them.
Pim (Netherlands)

MS13-076 (patch 2876315 – Kernel-mode Driver) issues.
Against Susan’s advice I installed patch 2876315 on one of my Windows 7 Ultimate 64 bit SP1 (US) systems. After the required restart the PC suffered from two Services not being started automatically and instability resulting in the infamous BSOD. The first was the ‘Workstation Service’. When this service is not started the system needs a very long time before the user-login icons appear on the screen and it is not possible to login restricted user accounts. If you login with administrator privileges it succeeds and a popup window from the right side of the taskbar shows a report telling that the Workstation Service was not started & please contact your administrator. In this situation you can start the Workstation Service manually and set it to start automatically. After that you can login restricted users and the system operates as normal.
The next time I cold started the system and logged in with admin privileges another report came up telling that the ‘System Event Notification’ Service was not started. Again the system was slow. Funny enough the ‘System Event Notification’ Service appeared to be started already and set to start automatically. Using the system in this state it behaved instable with random BSOD’s.
All issues described above disappeared after uninstalling patch 2876315. In my opinion Microsoft has to do some extra work on this…