MAJOR BUGS in Win10 22H2

12

Hi all

Following the release of Windows 10 22H2, I used the Media Creation Tool to create some ISOs; one of the “x64” version, and one of the “x86”.

As it’s been a while since I’ve used any 32-bit kernel Windows, I thought I’d give it a whirl inside a VM.

And that’s when I’ve found two serious bugs, both of which render your system unbootable.

Issue 1: Don’t assume older updates are no-longer required!

I would have assumed that given Windows 10 22H2 ISOs will be newer, there should be no-need to install some of the older updates, as surely they would now be integrated — wrong!

I elected to install only the following updates:

• KB4052623 – Windows Security engine update (32-bit)

• mpam-fe – Latest definition updates for Windows Security

• KB5017262 – Update for .NET 3.5 and 4.8 for Win10 21H2 (32-bit)

• KB5018410 – Oct 2022 Cumulative Update for Win10 22H2 (32-bit)

Upon rebooting, I was met with a blue-screen with the error “SYSTEM_THREAD_EXCEPTION_NOT_HANDLED”

After one-further reboot and BSOD, it then went to the “Preparing Automatic Repair” screen.

This process announced “We couldn’t complete the updates. Undoing changes”

And after logging back into Windows, it advised “We removed some recently installed updates to recover your device from a start-up failure”

Moral of the story: yes, in Windows 10 22H2 you still need to install the “2021-07 Servicing Stack Update (KB5005260)” and “2022-08 Secure Boot DBX Update (KB5012170)” updates before installing the updates above. Yes, you would think that Microsoft might actually integrate such older updates within a refreshed install media… but apparently not. (Note that if you let Windows Update install the updates, this issue is avoided.)

Bug 2: Don’t remove the “Windows Fax & Scan” feature

This one is more-serious, as unlike the above bug which most users would avoid (as it only applies if you do updates manually, rather than let Windows Update take-care of things), this one can occur by simply using standard, built-in options in Windows 10 itself!

To replicate (warning: make a System Restore point first!)

1 Log into a 32-bit kernel install of Windows 10 as a local-admin

2 Go into the Settings app

3 Click “Apps” then “Optional Features”

4 Click “Windows Fax & Scan”, then “Uninstall”

5 Restart Windows when it says “Reboot required”

6 During the next boot you will see

  “Updating your system 0%”

then soon after, this blue-screen:

  Stop code: KMODE_EXCEPTION_NOT_HANDLED

  What failed: NTFS.SYS

A System Restore point is your only method to get that Windows install working again!

This bug does not affect the 64-bit (AMD64) kernel installs, and I’ve not got any ARM devices to test on (but it could affect a 32-bit ARM install of W10onARM.)

Windows 11 won’t be affected, as there aren’t any 32-bit kernel releases.