Hi @JL Arranz
-- I'm confused --- and maybe it's a translation problem when you translated the titles to English as you said above
I just did the same list of applied updates on my Windows 10 system Windows Update History, as you did and here is how it listed the update:
The word Preview
is definitely present in the update title, and if you Google search for "KB5032278", every hit that comes back for that search has the word Preview in the title. When the same fix(es) are released to the entire user community, it will be assigned a different KB number. That will happen after the next Patch Tuesday Dec 12. So I think you installed the KB5032278 Preview
version , but as I posted this latest Preview did not damage the Recovery code, and Rescue Media built with WinRE is not damaged. If you continue to get the BSOD with ntoskernel.exe missing when you boot rescue media, then you probably were infected iby installing one of the earlier bad Preview updates. (You should look as far back as July 2023 in the update history -- the bad updates are KB503300 and KB5029331).
Earlier, when this topic was first opened, two monthly PREVIEW updates damaged the ability to use Win RE when building Rescue Media. The damaging change that was present in the first Preview KB5029331 did not get carried forward in the next NON-PREVIEW (Patch Tuesday) updates, and instead reappeared in the next months PREVIEW KB503300, and again did not get carried into the next NON-PREVIEW version. However, once anybody installed one or both of the PREVIEW versions, it had to be uninstalled (or the system restored from backup) to undo the damage to WinRE
. Any Rescue Media built based on WinRE with the bad Recovery partition will fail to boot. It has to be rebuilt after any of the bad updates have been removed.
Edited to correct this statement: Later Preview versions of updates (after KB503300) don't
INTRODUCE the problem.
Non-preview Cumulative updates AFTER 2023-09
appear to fix the problem with the recovery partition, and damaged RM built on WinRE 10 can be fixed by a Forced Rebuild after the Windows Update has been applied.
L.W. (Dan) Danz, Overland Park KS
Reflect v8.1.7847+ on Windows 11 Home 23H2 22631.3085+ | Reflect v8.1.7853+ on Windows 10 Pro 22H2 19045.3996+
Reflect v8.1.7784+ on 2 systems Windows 10 Home 22H2 19045.3803+