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

Anonymous
2022-10-14T22:36:07+00:00

My computer is a DELL Optiplex 3020. Both recent cumulative updates (KB5018410 and KB5016616) have failed on installation. The code is 0x800f0845. I have tried all the suggested things to try to get the update to go through up to an in-place update. All other updates go through with no problem. Just the cumulative updates. I have version 21H2 build 19044.1826.

Windows for home | Windows 10 | Install and upgrade

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

47 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-10-28T01:08:28+00:00

    I have the same problem, can you solve it?

    Was this answer helpful?

    0 comments
  2. Anonymous
    2022-10-27T21:10:58+00:00

    Thanks for the findings, but swapping stornvme.sys didn't work for me, sorry. I did put the machine to a VM for testing, too (Win10pro_21H2_64bit). I did backup stornvme.sys in system32\drivers. Then run kb5018410 and after 30% of the update the machine did the problematic reboot. This time I did boot to WinRE and I saw the new stornvme.sys. I removed the new one and replaced it with the backed up on. After that I tried the restart in good faith, but no luck. Startup process did stuck at the black screen with the spinner short after the win logo is gone, as always. Too bad .... . Or did I understand it wrong? When I swap other drivers e.g. storahci.sys I get a BSOD.

    Btw adding my findings and data:

    No hidden restore partitions on the drive. Machine was upgraded from Win7pro_64Bit. OS was already on many machines: Lenovo Thinkpad T400 -> Dell -> Lenovo T560 -> now in a VM. Never used secure boot. If MBR/BIOS or GPT/UEFI doesnt matter, tried the update with both configurations. If virtualisation put on or off in Bios/UEFI doesnt matter, tried the update with both configurations. Inplace-Upgrade with 22H2 leads to error code 0xC1900101 - 0x30017 and works only when I choose "keep nothing". Indeed selecting "Keep only own files" leads to the same error, so really a driver problem? I tried to uninstall all third party drivers and software, still no luck. A clean install 22H2 works with all machines. My guess is there's something wrong in the registry left during the lots of upgrades, updates and hardware changes the OS has undergone, but where to look?

    Was this answer helpful?

    0 comments
  3. Anonymous
    2022-10-27T16:28:21+00:00

    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.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2022-10-27T01:21:25+00:00

    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

    Was this answer helpful?

    0 comments
  5. Anonymous
    2022-10-26T23:00:28+00:00

    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.

    Was this answer helpful?

    0 comments