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

I suspect yours is a Legacy install. Let us see...

(1) Right-click START, & select "Disk Management". Use the divider lines in the header row to make it readable. Widen it with the right border line. Crunch it with the divider line between the panes. Then show us a picture....

(a) Shift+Winkey+S invokes Snip & Sketch.

(b) Draw an outline to make the snip. A notification appears in Action Center.

(c) Click the notification to reopen the snip into Snip & Sketch.

(d) You may draw on it, if desired. Then click the Save icon (disk) at top right.

(e) Click the "Insert Image" icon above your post (2nd from right) to insert it.

     It was saved to the Pictures folder, & Insert Image opens that same folder.

(2)  At an Administrator Command Prompt, let's see...

DiskPart                  <<<Enter DiskPart

List  Vol                   <<<List the volumes & letters

List  Disk                 <<<List the disks

=== For each disk that had a System Reserved or an EFI partition in Disk Management, ===

=== select its disk number & let's see the details of each partition.                                   ===

Select  Disk  X         <<<Focus on disk X (use an actual number)

List  Part                  <<<List its partitions

=== Let's say it has 3 partitions. then show the details of each one.                                   ===

Select  Part  1          <<<Focus on partition 1

Detail  Part              <<<List its details such as Type & Attributes

Select  Part  2          <<<Focus on partition 2

Detail  Part

Select  Part  3          <<<Focus on partition 3

Detail  Part

Exit                          <<<Leave DiskPart

ReagentC  /Info                                  <<<Show Recovery partition location

BCDEdit                                              <<<Show BCD (but I'm unsure this applies to Legacy installations)

Hi there,

Im facing an issue to install the 2020-12 Cumulative Update for Windws 10 Version 1909 for x64-based Systems (KB4592449) 

My current OS Build is 18363.1171 

So my partition situation with drives is below:

As we can see my SDD drive is prior for running & boot windows. Disk & partition breakdown information below. 

Microsoft Windows [Version 10.0.18363.1171]

(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>disk part

'disk' is not recognized as an internal or external command,

operable program or batch file.

C:\WINDOWS\system32>disc part

'disc' is not recognized as an internal or external command,

operable program or batch file.

C:\WINDOWS\system32>diskpart

Microsoft DiskPart version 10.0.18362.1171

Copyright (C) Microsoft Corporation.

On computer: MSI

DISKPART> select disk 0

Disk 0 is now the selected disk.

DISKPART> list part

  Partition ###  Type              Size     Offset

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

  Partition 1    System             300 MB  1024 KB

  Partition 2    Reserved           128 MB   301 MB

  Partition 3    Primary            129 GB   429 MB

  Partition 4    Primary            329 GB   129 GB

  Partition 5    Recovery           900 MB   459 GB

  Partition 6    Recovery            16 GB   460 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         SYSTEM       FAT32  Partition    300 MB  Healthy    System  <-- Under Label, should it be stated as "EFI" instead of "System"?

DISKPART> exit

Leaving DiskPart...

C:\WINDOWS\system32>BCDEdit

Windows Boot Manager

---

identifier              {bootmgr}

device                  partition=\Device\HarddiskVolume4                     <-- Should it be replaced with EFI allocated disk Volume1? 

path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

description             Windows Boot Manager

locale                  zh-CN

inherit                 {globalsettings}

default                 {current}

resumeobject            {04a32fd6-7c9c-11ea-a7bf-00d861e498a8}

displayorder            {current}

toolsdisplayorder       {memdiag}

timeout                 30

Windows Boot Loader

---

identifier              {current}

device                  partition=C:

path                    \WINDOWS\system32\winload.efi

description             Windows 10

locale                  zh-CN

inherit                 {bootloadersettings}

recoverysequence        {5a3eabbd-1345-11eb-a7bf-9bd3608c2917}

displaymessageoverride  Recovery

recoveryenabled         Yes

isolatedcontext         Yes

allowedinmemorysettings 0x15000075

osdevice                partition=C:

systemroot              \WINDOWS

resumeobject            {04a32fd6-7c9c-11ea-a7bf-00d861e498a8}

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\harddisk0\partition6\Recovery\WindowsRE

    Boot Configuration Data (BCD) identifier: 5a3eabbd-1345-11eb-a7bf-9bd3608c2917

    Recovery image location:

    Recovery image index:      0

    Custom image location:

    Custom image index:        0

REAGENTC.EXE: Operation Successful.

A did also tried to use use Windows update troubleshooter, report provide below issues.

IsPostback_RC_PendingUpdates 

IsPostback: False 

InformationalWaaSMedicService 

Issue found by :EnableUUPScanPlugin 

InformationalIsPostback_RC_PendingUpdates 

IsPostback: True 

InformationalService Status 

Problem with BITS service : The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException  

InformationalService Status 

Problem with BITS service : The requested service has already been started. System.Management.Automation.RemoteException More help is available by typing NET HELPMSG 2182. System.Management.Automation.RemoteException  

Collection information 

Computer Name:  MSI 

Windows Version: 10.0 

Architecture: x64 

Time: Monday, January 11, 2021 5:22:41 PM 

Hope for your help, please kindly let me know if i need to provide extra information? Will do my best!

(1) "

Disk 0 is now the selected disk.

DISKPART> list part

  Partition ###  Type              Size     Offset

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

  Partition 1    System             300 MB  1024 KB            <<<EFI

  Partition 2    Reserved           128 MB   301 MB

  Partition 3    Primary            129 GB   429 MB

  Partition 4    Primary            329 GB   129 GB              <<<Your D: drive

  Partition 5    Recovery           900 MB   459 GB

  Partition 6    Recovery            16 GB   460 GB

Windows Boot Manager

---

identifier      {bootmgr}

device          partition=\Device\HarddiskVolume4         <-- Should it be replaced with EFI

                                                                                              allocated disk Volume1?

"

I would expect it should say HarddiskVolume1 just as you suspect. That is your EFI partition going by its type in the Detail Disk you showed...

Partition 1

Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b          <<<That's correct for EFI

Let's see a Detail Part on partition 4 (which is your D:drive)...

DiskPart

Select  Disk  0

Select  Part  4

Detail  Part

Exit

DIR   D:\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI  /a        <<<And is the file there?

(a) It should normally be a basic data partition:  ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

(b) And normally that folder & file shouldn't be on it. It should be on EFI.

(c) Are you booting to the Windows Boot Manager in BIOS Setup?

It does look suspicious to me. I've seen a case where booting directly to a drive caused the HarddiskVolume number to be different from my expectation. But even if your BIOS does boot directly to disk 0, I'd still expect to see HarddiskVolume1. So, I'm really confused to see ...4.

(2) "

  Volume ###  Ltr  Label        Fs     Type        Size     Status     Info

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

* Volume 2         SYSTEM       FAT32  Partition    300 MB  Healthy    System  <-- Under Label, should it be

                                                                                                             stated as "EFI" instead of "System"?

"

No, the Label can be anything. It needs to say "System" under "Info" just as it does. And it should be FAT32 just as it is. Usually it is 100 MB, but your 300 is OK. I believe some types of drives may even require the larger size.

(3) Your ReagentC /Info indicates partition 6 is the Recovery partition...

    Windows RE location:       \?\GLOBALROOT\device\harddisk0\partition6\Recovery\WindowsRE

Judging from its size of 16 GB, it is a factory reset partition. So, a Reset would return the computer to its factory condition whatever that OS may be. If the computer came with Win 8.1, for instance, you'll end up back there. That could get messed up by doing an upgrade.

Have you upgraded the OS since purchase of the computer? Or did it come with 1909?

Hi,

Kind thanks for your help. Below is my comments as required.

Windows Boot Manager

---

identifier      {bootmgr}

device          partition=\Device\HarddiskVolume4         <-- Should it be replaced with EFI

                                                                                              allocated disk Volume1?

"

I would expect it should say HarddiskVolume1 just as you suspect. That is your EFI partition going by its type in the Detail Disk you showed...

• So should I change it to Volume1? Is there any risk or this is an easy to proceed thingy? I honestly dont know how its allocated Volume4, since i didnt change nothing once received my laptop (only once i did a factory reset).

Let's see a Detail Part on partition 4 (which is your D:drive)...

DiskPart

Select  Disk  0

Select  Part  4

Detail  Part

Exit

DIR   D:\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI  /a        <<<And is the file there?

(a) It should normally be a basic data partition:  ebd0a0a2-b9e5-4433-87c0-68b6b72699c7

(b) And normally that folder & file shouldn't be on it. It should be on EFI.

(c) Are you booting to the Windows Boot Manager in BIOS Setup?

• Im not able to view EFI folder, im not sure even if its existing, is it hidden or something ? Any steps to check this ?

(3) Your ReagentC /Info indicates partition 6 is the Recovery partition...

    Windows RE location:       \?\GLOBALROOT\device\harddisk0\partition6\Recovery\WindowsRE

Judging from its size of 16 GB, it is a factory reset partition. So, a Reset would return the computer to its factory condition whatever that OS may be. If the computer came with Win 8.1, for instance, you'll end up back there. That could get messed up by doing an upgrade.

Have you upgraded the OS since purchase of the computer? Or did it come with 1909?

• Yes, this is my factory reset partition. Windows come along with 1903 version. But in Oct 2020 i did a factory reset and my windows updated up to 1909 version. Below is history per updates.

"- So should I change it to Volume1? Is there any risk or this is an easy to proceed thingy? I honestly dont know how its allocated Volume4, since i didnt change nothing once received my laptop (only once i did a factory reset)."

I just don't know what's up with that. Looking at your Disk Management,..

I'd expect HarddiskVolume1 would already be there in the BCD. That is because I think it counts the partitions beginning with those on Disk 0 & progressing to the others. I can't think of how it could be saying ...4. Even if BIOS were set to boot directly to Disk 0 (instead of to the Windows boot manager), I'd still expect it be ...1.

The only exception I think I know is, if there were an OS on Disk 1 & BIOS were set to boot directly to it. then maybe it would start counting with the partitions on Disk 1. But still I can't see how that would come up with a ...4 looking at the partitions you've got, Big puzzle to me how you're getting a ...4.

Another thing is, I think that value (HarddiskVolume) might be set by Windows during/after the boot. IOW, it may not matter what is in there to begin the boot. It is set afterward to say which system partition was used to accomplish the boot. But really there should be only one system partition, which normally is EFI. If this is true, changing it yourself has no real effect anyway, It may act as just a suggestion to tell Windows where to start looking, I don't really know.

Maybe, then, your BCD isn't being used at all & it just remains a ...4 from its last use (when presumably there actually was an EFI where it says). But how are you booting now then? Big puzzle. Did you look in BIOS Setup to see what's going on at the Boot page...?...

https://www.sysnative.com/forums/threads/get-access-to-bios-settings-boot-menu-f-keys-hotkeys-by-system-manufacturer-oem.23010/

Get access to BIOS settings & Boot Menu: F-keys/Hotkeys by System Manufacturer (OEM)

Note: That should say what PF key gets to your BIOS Setup, but I know nothing (bad or good) of any links or downloads that are there (or anywhere else).

(2) "- Im not able to view EFI folder, im not sure even if its existing, is it hidden or something ? Any steps to check this ?"

Let's see all of this at an Administrator Command Prompt...

DiskPart                    <<<Enter DiskPart

Select  Disk  1           <<<Focus on Disk 1

List  Part                    <<<Maybe there's a hidden partition on it (like MSR is hidden)

Select  Disk  0           <<<Focus on Disk 0

Select  Part  4            <<<Focus on partition 4

Detail  Part               <<<I think we won't see EFI's type because Disk Management doesn't say EFI for it

Select  Part  1           <<<Focus on partition 1 (EFI)

Assign  Letter=S       <<<Give EFI the letter S

Exit                            <<<Exit DiskPart

DIR   D:\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI  /a       <<<I think the file won't be there

DIR   S:\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI  /a       <<<I think it will be here

DIR   C:\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI  /a       <<<Check C:\ too

DiskPart                         <<<Enter DiskPart

Select  Vol=S                 <<<Select the EFI partition by its letter

Remove  Letter=S         <<<Remove the letter

Exit                                <<<Exit DiskPart

Use Ctrl-A & Ctrl-C to copy, then show us. With "/a", the Command Prompt can see what File Explorer may not see. If it says there is no BOOTMGFW.EFI there, then Windows can't possibly be booting from D: partition.

(3) "- Yes, this is my factory reset partition. Windows come along with 1903 version. But in Oct 2020 i did a factory reset and my windows updated up to 1909 version. Below is history per updates."

The upgrade to 1909 messed up the ability to do another factory reset. That partition is being used now to hold Windows' recovery environment which really only needs the 900 MB of partition 5. We should switch to partition 5 for that. Then repurpose partition 6 to be a data partition or give its 16 GB to C: partition. After that, make your own system image(s) of 1909 onto external media.