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

(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!

VBabooshka, yours is a UEFI install, I say, because it has that 128 MB System Reserved partition. To be certain, try "BCDEdit" at an Administrator Command Prompt. In the Windows Boot Manager, it must mention EFI twice in the Path. As your EFI partition is partition 2, I expect your Device will say "HardDiskVolume2"...

C:\WINDOWS\system32>bcdedit

Windows Boot Manager

---

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume1         <<<I expect yours to say ...2

path                    \EFI\Microsoft\Boot\bootmgfw.efi        <<<This is a UEFI installation

description         Windows Boot Manager

locale                  en-US

inherit                 {globalsettings}

default                 {current}

resumeobject      {f8d976f9-df94-11ea-b1d0-74e6e2074932}

displayorder        {current}

toolsdisplayorder   {memdiag}

timeout               30

helzayat's discovery was about his EFI System partition. Your EFI is partition 2, so...

(1) Type "CMD" into the Search bar, & click "Run as Administrator".

(2) Enterthe following commands...

DiskPart

Select  Disk  0

List  Part

Select  Part  2 <<< Your EFI is partition 2, VBabooshka

Detail  Part

Exit

Use Ctrl-A & Ctrl-C to copy, then post it to us, The main thing is for it to have the proper type ID of:  c12a7328-f81f-11d2-ba4b-00a0c93ec93b

If it does not have it, then this will fix it...

DiskPart                                                                                       <<<Start DiskPart

Select  Disk  0                                                                              <<<Select drive 0

Select  Part  2                                                                              <<<Select the EFI partition

Detail  Part                                                                                  <<<Show improper ID

Set ID=c12a7328-f81f-11d2-ba4b-00a0c93ec93b  Override     <<<Give it proper ID

Detail  Part                                                                                  <<<Show proper ID

Exit                                                                                               <<<Leave DiskPart

Best reboot afterward to be sure it registers.

That should do it. If it solves the problem, both helzayat & crackshot91 also deserve credit.

Good afternoon, 

I am beyond frustrated trying to fix this issue and I'm not a computer person.  this is the information that comes up when I run the above suggested diagnostic.  Any sight on how to fix this, I would greatly appreciate.

Microsoft Windows [Version 10.0.19041.685]

(c) 2020 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>DiskPart

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.

On computer: NEWHP

DISKPART> Sele

Microsoft DiskPart version 10.0.19041.610

DISK        - Shift the focus to a disk. For example, SELECT DISK.

PARTITION   - Shift the focus to a partition. For example, SELECT PARTITION.

VOLUME      - Shift the focus to a volume. For example, SELECT VOLUME.

VDISK       - Shift the focus to a virtual disk. For example, SELECT VDISK.

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>DiskPart

Microsoft DiskPart version 10.0.19041.610

Copyright (C) Microsoft Corporation.

On computer: NEWHP

DISKPART> Select Disk 0

Disk 0 is now the selected disk.

DISKPART> List Part

  Partition ###  Type              Size     Offset

  -------------  ----------------  -------  -------

  Partition 1    Recovery           400 MB  1024 KB

  Partition 2    System             260 MB   401 MB

  Partition 3    Reserved           128 MB   661 MB

  Partition 4    Primary            677 GB   789 MB

  Partition 5    Recovery           974 MB   678 GB

  Partition 6    Primary             19 GB   679 GB

DISKPART> Select Part 1

Partition 1 is now the selected partition.

DISKPART> Detail Part

Partition 1

Type    : de94bba4-06d1-4d40-a16a-bfd50179d6ac

Hidden  : Yes

Required: Yes

Attrib  : 0X8000000000000001

Offset in Bytes: 1048576

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info

  ----------  ---  -----------  -----  ----------  -------  ---------  --------

* Volume 3         WINRE        NTFS   Partition    400 MB  Healthy    Hidden

DISKPART>

Kindest regards

BecauseDanielWasTaken,

That is great news that you solved it on your own. Good going. That's right, (I almost forgot) sometimes a feature update (new version) installs better when done with the Media Creation Tool, either directly or after making an ISO or a Win 10 Installation USB drive. I had to do it once myself. I like the USB drive because it comes with a recovery environment & of course can also be used for a clean install. Thanks for the reminder.

Your partitions look good, Probably you've got a 5th now. It will be 20H2's Recovery partition carved off the end of the Windows partition (partition 4). Partition 1 is wasted space now (but it isn't much), & it probably is empty. A "ReagentC  /Info" will name the RE location to be partition 5.

That looks like a UEFI install on Disk 1 because of the presence of what looks like an MSR (Microsoft Reserved) 16 MB partition. A Legacy install wouldn't have one. So, partition 2 is an EFI system partition. EFI never needs to be larger than 100 MB. A System Reserved partition (of a Legacy install) can double as the Recovery partition (meaning it will hold WinRE.wim) & also can be used by 3rd-party software; so, that might need more space sometimes. Glad you don't have one & didn't have to do it.

Good going. Good luck, & keep us informed.