Error 0x800f0922 for 2020-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4532695)

Okay. Thank you so much for trying to help me. I'm assuming that the only simple solution is a system reinstall. I really appreciate that you helped me and I've learnt a lot.

Best regards

OK, I see the Kingston SSD is only 500 GB. Well, I see nothing wrong with your disks & partitions. There is only one EFI anywhere, & it is where it belongs. It has the right Type code. Your problem with doing an update must lie elsewhere.

I have seen threads in which it is sometimes difficult to boot to an SSD. But I really don't know what to suggest. Can you easily switch them in their slots & make the SSD to be Disk 0? And maybe leave the other two unplugged until Windows on the SSD is updated? But that really isn't my forte (as if anything really is). I'm unsure whether doing such opens up a whole new can of worms.

Here are the other two disks and their parts. Disk 2 is an nmve m.2 ssd and disk 3 is as you said, a barracuda one, and disk 0 is some i found in an old laptop.

DISKPART> list disk

Disk ### Status Size Free Dyn Gpt

---

Disk 0 Online 465 GB 1024 KB

Disk 2 Online 465 GB 1024 KB *

Disk 3 Online 1853 GB 0 B *

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset

---

Partition 1 Primary 465 GB 31 KB

DISKPART> select disk 3

Disk 3 is now the selected disk.

DISKPART> list part

Partition ### Type Size Offset

---

Partition 1 Reserved 128 MB 1024 KB

Partition 2 Primary 1853 GB 129 MB

And here is my disk management. Its in Swedish but I hope that wont be an issue.

(1) I still want to see a DiskPart/List Disk of disks 0 & 3 to see whether there is an EFI on one. And where are those asterisks? Also, let's see a picture of "right-click START, Disk Management". Use the divider lines in the Header to make the columns readable.

(2) The Firmware Boot Manager (fwbootmgr) is a window to the BIOS boot screen...

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {bootmgr} ....................................................<<<Windows Boot Manager

{5b8bc523-5fee-11eb-bd3e-e0a6f380f4ef} .............<<<ST9500325AS (500 GB Seagate Momentus)

{5b8bc524-5fee-11eb-bd3e-e0a6f380f4ef} .............<<<ST2000DM006-2DM164 (2TB Barracuda)

{5b8bc526-5fee-11eb-bd3e-e0a6f380f4ef} .............<<<KINGSTON SA2000M8500G (1TB Nvme SSD)

timeout 1

Yours is showing a Windows Boot Manager (bootmgr) on top of the boot order which is what a UEFI install likes. It is followed by two HDD & an SSD, When plugged in, those show up as boot items (whether or not they hold an OS) in the BCD. When the BIOS Boot Menu F-key is pressed during boot, they will show up as a onetime boot option. That much looks good to me.

But your earlier List Disk is showing two disks of 500 GB & one of 2 TB...

Disk ### Status Size Free Dyn Gpt

---

Disk 0 Online 465 GB 1024 KB ,,,,,,,,,,,,,,,,,,,,,,,,,,,Momentus HDD

Disk 2 Online 465 GB 1024 KB * ........................Another Momentus HDD? Kingston SSD

Disk 3 Online 1853 GB 0 B * ................................Barracuda HDD

I think I am seeing two Momentus instead of just one plus an SSD. Where is the SSD of 1TB?

Edit: OK, now I see the Kingston SSD is just 500 GB, & it is Disk 2.

Hmm, I dont belive I have two windows installs but better safe than sorry right?

Here is my BCDEdit /Enum All

C:\Windows\system32>BCDEdit /enum all

Firmware Boot Manager

---

identifier {fwbootmgr}

displayorder {bootmgr}

                    {5b8bc523-5fee-11eb-bd3e-e0a6f380f4ef} 

                    {5b8bc524-5fee-11eb-bd3e-e0a6f380f4ef} 

                    {5b8bc526-5fee-11eb-bd3e-e0a6f380f4ef} 

timeout 1

Windows Boot Manager

---

identifier {bootmgr}

device partition=\Device\HarddiskVolume1

path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description Windows Boot Manager

locale sv-SE

inherit {globalsettings}

default {current}

resumeobject {5b8bc528-5fee-11eb-bd3e-e0a6f380f4ef}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Firmware Application (101fffff)

---

identifier {5b8bc523-5fee-11eb-bd3e-e0a6f380f4ef}

description ST9500325AS

Firmware Application (101fffff)

---

identifier {5b8bc524-5fee-11eb-bd3e-e0a6f380f4ef}

description ST2000DM006-2DM164

Firmware Application (101fffff)

---

identifier {5b8bc526-5fee-11eb-bd3e-e0a6f380f4ef}

description KINGSTON SA2000M8500G

Windows Boot Loader

---

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

description Windows 10

locale sv-SE

inherit {bootloadersettings}

recoverysequence {5b8bc52a-5fee-11eb-bd3e-e0a6f380f4ef}

displaymessageoverride Recovery

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {5b8bc528-5fee-11eb-bd3e-e0a6f380f4ef}

nx OptIn

bootmenupolicy Standard

Windows Boot Loader

---

identifier {5b8bc52a-5fee-11eb-bd3e-e0a6f380f4ef}

device ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{5b8bc52b-5fee-11eb-bd3e-e0a6f380f4ef}

path \windows\system32\winload.efi

description Windows Recovery Environment

locale sv-se

inherit {bootloadersettings}

displaymessage Recovery

osdevice ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{5b8bc52b-5fee-11eb-bd3e-e0a6f380f4ef}

systemroot \windows

nx OptIn

bootmenupolicy Standard

winpe Yes

Resume from Hibernate

---

identifier {5b8bc528-5fee-11eb-bd3e-e0a6f380f4ef}

device partition=C:

path \Windows\system32\winresume.efi

description Windows Resume Application

locale sv-SE

inherit {resumeloadersettings}

recoverysequence {5b8bc52a-5fee-11eb-bd3e-e0a6f380f4ef}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

filedevice partition=C:

filepath \hiberfil.sys

bootmenupolicy Standard

debugoptionenabled No

Windows Memory Tester

---

identifier {memdiag}

device partition=\Device\HarddiskVolume1

path \EFI\Microsoft\Boot\memtest.efi

description Windows Minnesdiagnostik

locale sv-SE

inherit {globalsettings}

badmemoryaccess Yes

EMS Settings

---

identifier {emssettings}

bootems No

Debugger Settings

---

identifier {dbgsettings}

debugtype Local

RAM Defects

---

identifier {badmemory}

badmemorylist 0x34c9e6

Global Settings

---

identifier {globalsettings}

inherit {dbgsettings}

                    {emssettings} 

                    {badmemory} 

Boot Loader Settings

---

identifier {bootloadersettings}

inherit {globalsettings}

                    {hypervisorsettings} 

Hypervisor Settings

---

identifier {hypervisorsettings}

hypervisordebugtype Serial

hypervisordebugport 1

hypervisorbaudrate 115200

Resume Loader Settings

---

identifier {resumeloadersettings}

inherit {globalsettings}

Device options

---

identifier {5b8bc52b-5fee-11eb-bd3e-e0a6f380f4ef}

description Windows Recovery

ramdisksdidevice partition=\Device\HarddiskVolume4

ramdisksdipath \Recovery\WindowsRE\boot.sdi