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

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

(1) Well, your EFI on Disk 2 has the right Type code. And even its Attribute looks fine. All 4 partitions look good in type, size & order. And your ReagentC names the right disk & partition to hold the RE (Recovery Environment)...

Windows RE location: \?\GLOBALROOT\device*harddisk2\partition4*\Recovery\WindowsRE

(2) But is there another EFI on Disk 0 or Disk 3? That too could be problematic when doing an update. Let's See...

DiskPart ..................<<<Enter DiskPart

List Disk ......................<<<List the disks

Select Disk 0 ............<<<Focus on Disk 0

List Part ......................<<<List the partitions of Disk 0

Select Disk 3 ...........<<<Focus on Disk 3

List Part ......................<<<List the partitions of Disk 3

Exit .................................<<<Leave DiskPart

(3) Your List Disk looked like this...

Disk ### Status Size Free Dyn Gpt

---

Disk 0 Online 465 GB 1024 KB

Disk 2 Online 465 GB 1024 KB * .............<<<Where is that asterisk - under Dyn or Gpt?

Disk 3 Online 1853 GB 0 B *

(a) Copy/paste does an injustice to it. Can you say whether those asterisks are under DYN or GPT? Yours is a UEFI install, so Disk 2 should be GPT (GUID Partition Table). It would be strange otherwise.

(b) And another thing: Where is Disk 1? (But I guess that likely is OK.)

(4) Your BCDEdit is showing...

Windows Boot Manager

---

identifier {bootmgr}

device partition=\Device**HarddiskVolume1 ..........**<<<Location of Boot Manager & EFI

path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

HardDiskVolume1, I used to say, was the first partition of Disk 0 (or whatever the first disk is). But now I think it is the first partition of the disk that is booted. That would mean you are booting directly to Disk 2 from BIOS (unless there is also an EFI on Disk 0). That is a problematic way to boot Windows. It leads me to suspect you have two complete installations of Windows plugged in at once. That is bad when there is a reboot (to complete an install) during an update. If you want to dual-boot Windows, there is another way to do it. Plugging in two complete installations is wrong. I believe. Let's see a full BCDEdit...

BCDEdit /Enum All

Hey!

It saddends me to have to, as many others have, ask for help. I have used all of the possible solutions without success. Here are my logs for diskpart and bcdedit etc.

First of all, DiskPart:

Microsoft Windows [Version 10.0.19042.746]

(c) 2020 Microsoft Corporation. Med ensamrätt.

C:\Windows\system32>DiskPart

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.

On computer: ...

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 2

Disk 2 is now the selected disk.

DISKPART> List part

Partition ### Type Size Offset

---

Partition 1 System 100 MB 1024 KB

Partition 2 Reserved 16 MB 101 MB

Partition 3 Primary 465 GB 117 MB

Partition 4 Recovery 500 MB 465 GB

DISKPART> select part 1

Partition 1 is now the selected partition.

DISKPART> detail part

Partition 1

Type : c12a7328-f81f-11d2-ba4b-00a0c93ec93b

Hidden : Yes

Required: No

Attrib : 0X8000000000000000

Offset in Bytes: 1048576

Volume ### Ltr Label Fs Type Size Status Info

---

* Volume 2 FAT32 Partition 100 MB Healthy System

DISKPART>

In my eyes nothing seems to be wrong here right?

Here is my BCDEdit and ReagentC /info

C:\Windows\system32>BCDEdit

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

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

C:\Windows\system32>ReagentC /info

Windows Recovery Environment (Windows RE) and system reset configuration

Information:

Windows RE status:         Enabled 

Windows RE location:       \\?\GLOBALROOT\device\harddisk2\partition4\Recovery\WindowsRE 

Boot Configuration Data (BCD) identifier: 5b8bc52a-5fee-11eb-bd3e-e0a6f380f4ef 

Recovery image location: 

Recovery image index:      0 

Custom image location: 

Custom image index:        0 

REAGENTC.EXE: Operation Successful.

I will be forever grateful for any response!