cumulative updates fail to install. Both KB5018410 and KB5016616 failed on installation.

THX to all. Despite everything, I presume 2022-10 for 21H2 and 22H2 will be not possible to install. Unless Microsift creates a specifix fix for it. What I doubt.. Thanks anyway for all your comments.

John,

Is that driver left over from a native device using Disk2Vhd, or did you install windows from scratch as a VM?

I thought HyperV normally had is own Disk drivers... is this driver used for anything?

If Not, I would snapshot the VM and remove the driver and see if she still boots and more importantly updates, you can always Apply and rollback the VM if it crashes.

Also - What Error does the Samsung Drivers give you?

HTH,

Mike

I also have the same problem. The Windows 10 64-bit system is using the Samsung NVMe Controller, but I run a Windows 10 32-bit VM. The VM has the Standard NVM Express Controller, so it failed on KB5018410 and also on 22H2. I can't install the Samsung drivers on the VM, so these updates won't install.

So I started off today with a new USB and MS Media Creation tool creating a 32\64 install thumb of 22H2

I put two failing Gigabyte H110N machines on the bench, used DISKPART and wiped both.

Starting with the Machine A, I loaded a 64 bit version and after booting took the 2022-10 and it booted perfectly

I then tool Machine A wiped it again and reloaded a 64 bit version as EFI and after booting took the 2022-10 and it still booted perfectly

Starting with the Machine B, I loaded a 32 bit version and after booting took the 2022-10 and it failed as expected.

I Tried downloading the 2022-10 as a .MUI and it Failed

I disabled everything I could in the BIOS and it Failed

I wiped Machine B, and Added a SATA 860 Pro SSD and loaded 32 bit and took 2022-10 and it Worked!

I know from the past Using the Samsung NVMe driver will make the systems work, so I decided to a like test hacking.

I reloaded the M.2 again with 22H2 x32 and Prior to the update I took a copy of original Microsoft's stornvme.sys, I then took the 2022-10 update and during the reboot I pulled the drive stuck it in Machine A and took ownership and swapped out the newer version for the original.

After putting the drive back in Machine B and it booted, and finished the upgrade :)

I Now have a perfectly working 22H2 box with 2022-10 running the original 22H2 stornvme.sys.... Of coarse I would never put this into production as it will probably die again with the next cumulative, but it proved that MS broke their NVMe driver which is exactly what I first diagnosed.

So.. no matter what I did it I couldn't break 64bit and 32bit I can't fix without switching 150 machines NVMe Driver to Samsung.

I presume all our issues are bugs related to the changes for Secure Boot, just sad that the engineers at Microsoft really don't know what their doing and are completely hidden from the world and the chaos they cause.

This is so frustrating!

Regards,

Mike Pisano

Multiple stock Intel NUCs (NUC7i3BNB) are crashing after installing KB5018545 on Windows 10 21H2 (and also same after upgrading to 22H2).

Black screen after first reboot. Error 0x800f0845 after rollback.

Does anyone actually test these updates at all? This is ridiculous.