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

Anonymous
2020-01-31T22:50:04+00:00

Install attempt fails with error 0x800f0922 whether I run Windows Update  to install this update or run windows10.0-kb4532695-x64_a85fd28af075ebfd8b0753d2c2aca244e926c3ce.msu

Running WIndows 10 Pro Ver. 1909 build 18363.592

I have tried every suggestion by HiltonOishi in https://answers.microsoft.com/en-us/windows/forum/all/failed-install-attempt-error-code-0x800f0922/c5eb31d7-f04f-4ff8-9d6f-f39e4f03944b

After the update installs I restart the computer and when it reboots it gets to 93% in "Working on Updates" then I get "We couldn't complete the updates Undoing changes"

Windows Update says this is an optional update. Should I just ignore the problem till the next update?

Windows for home | Windows 10 | Windows update

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

133 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2021-02-08T06:07:03+00:00

    Thanks PCR -->

    Microsoft Windows [Version 10.0.18363.1316]

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\Windows\system32>BCDEdit /Enum All

    Firmware Boot Manager

    identifier              {fwbootmgr}

    displayorder            {2c06c486-872c-11ea-b70d-806e6f6e6963}

                            {aadb063e-872b-11ea-830f-c4acb7ccc0f1}

                            {bootmgr}

    timeout                 2

    Windows Boot Manager

    identifier              {bootmgr}

    device                  partition=\Device\HarddiskVolume2

    path                    \EFI\Microsoft\Boot\bootmgfw.efi

    description             Windows Boot Manager

    locale                  en-US

    inherit                 {globalsettings}

    default                 {current}

    resumeobject            {aadb0640-872b-11ea-830f-c4acb7ccc0f1}

    displayorder            {current}

    toolsdisplayorder       {memdiag}

    timeout                 30

    Firmware Application (101fffff)

    identifier              {2c06c486-872c-11ea-b70d-806e6f6e6963}

    device                  partition=\Device\HarddiskVolume2

    description             UEFI: ADATA SU800

    Firmware Application (101fffff)

    identifier              {aadb063e-872b-11ea-830f-c4acb7ccc0f1}

    description             UEFI: Network Card

    Windows Boot Loader

    identifier              {current}

    device                  partition=C:

    path                    \Windows\system32\winload.efi

    description             Windows 10

    locale                  en-US

    inherit                 {bootloadersettings}

    recoverysequence        {aadb0642-872b-11ea-830f-c4acb7ccc0f1}

    displaymessageoverride  Recovery

    recoveryenabled         Yes

    isolatedcontext         Yes

    allowedinmemorysettings 0x15000075

    osdevice                partition=C:

    systemroot              \Windows

    resumeobject            {aadb0640-872b-11ea-830f-c4acb7ccc0f1}

    nx                      OptIn

    bootmenupolicy          Standard

    Windows Boot Loader

    identifier              {aadb0642-872b-11ea-830f-c4acb7ccc0f1}

    device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{aadb0643-872b-11ea-830f-c4acb7ccc0f1}

    path                    \windows\system32\winload.efi

    description             Windows Recovery Environment

    locale                  en-us

    inherit                 {bootloadersettings}

    displaymessage          Recovery

    osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{aadb0643-872b-11ea-830f-c4acb7ccc0f1}

    systemroot              \windows

    nx                      OptIn

    bootmenupolicy          Standard

    winpe                   Yes

    Resume from Hibernate

    identifier              {aadb0640-872b-11ea-830f-c4acb7ccc0f1}

    device                  partition=C:

    path                    \Windows\system32\winresume.efi

    description             Windows Resume Application

    locale                  en-US

    inherit                 {resumeloadersettings}

    recoverysequence        {aadb0642-872b-11ea-830f-c4acb7ccc0f1}

    recoveryenabled         Yes

    isolatedcontext         Yes

    allowedinmemorysettings 0x15000075

    filedevice              partition=C:

    filepath                \hiberfil.sys

    bootmenupolicy          Standard

    debugoptionenabled      No

    Windows Memory Tester

    identifier              {memdiag}

    device                  partition=\Device\HarddiskVolume2

    path                    \EFI\Microsoft\Boot\memtest.efi

    description             Windows Memory Diagnostic

    locale                  en-US

    inherit                 {globalsettings}

    badmemoryaccess         Yes

    EMS Settings

    identifier              {emssettings}

    bootems                 No

    Debugger Settings

    identifier              {dbgsettings}

    debugtype               Local

    RAM Defects

    identifier              {badmemory}

    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              {aadb0643-872b-11ea-830f-c4acb7ccc0f1}

    description             Windows Recovery

    ramdisksdidevice        partition=\Device\HarddiskVolume1

    ramdisksdipath          \Recovery\WindowsRE\boot.sdi

    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\partition1\Recovery\WindowsRE

        Boot Configuration Data (BCD) identifier: aadb0642-872b-11ea-830f-c4acb7ccc0f1

        Recovery image location:

        Recovery image index:      0

        Custom image location:

        Custom image index:        0

    REAGENTC.EXE: Operation Successful.

    C:\Windows\system32>Diskpart

    Microsoft DiskPart version 10.0.18362.1171

    Copyright (C) Microsoft Corporation.

    On computer: DESKTOP-VHJK81L

    DISKPART> Select Disk 0

    Disk 0 is now the selected disk.

    DISKPART> Select Part 1

    Partition 1 is now the selected partition.

    DISKPART> Assign Letter=R

    DiskPart successfully assigned the drive letter or mount point.

    DISKPART> Exit

    Leaving DiskPart...

    C:\Windows\system32>Dir R:\ /a

     Volume in drive R is Recovery

     Volume Serial Number is 10DE-A86E

     Directory of R:\

    08/02/2021  07:57 AM    <DIR>          Recovery

    25/04/2020  12:38 PM    <DIR>          System Volume Information

                   0 File(s)              0 bytes

                   2 Dir(s)      98,332,672 bytes free

    C:\Windows\system32>DiskPart

    Microsoft DiskPart version 10.0.18362.1171

    Copyright (C) Microsoft Corporation.

    On computer: DESKTOP-VHJK81L

    DISKPART> Select Disk 0

    Disk 0 is now the selected disk.

    DISKPART> Select Part 1

    Partition 1 is now the selected partition.

    DISKPART> Remove Letter=R

    DiskPart successfully removed the drive letter or mount point.

    DISKPART>

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-02-08T06:12:09+00:00

    PS We live in Australia hence the time delay...

    I really admire your skills, have done a bit of support over the years (now retired) so have got really rusty with this stuff!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-02-08T07:38:20+00:00

    RobynR1,

    (1) That looks good regarding the EFI & Recovery partitions. It says EFI is partition 2 (HardDiskVolume2), &  Recovery is partition 1 (HardDiskVolume1). The folders on Recovery are right, & ReagentC points nicely to it & is enabled. So, go ahead & change its ID as I posted earlier...

    DiskPart                                                                                       <<<Enter DiskPart

    Select  Disk  0                                                                              <<<Select disk 0

    Select  Part  1                                                                               <<<Select the Recovery partition

    Detail  Part                                                                                   <<<Show improper ID

    Set ID=de94bba4-06d1-4d40-a16a-bfd50179d6ac  Override    <<<Give it proper ID

    Detail  Part                                                                                   <<<Show proper ID

    Exit                                                                                               <<<Leave DiskPart

    Reboot to be sure the full system is aware of the change.

    (2) But here is how your BIOS is set at the Boot Order page...

    Firmware Boot Manager

    identifier            {fwbootmgr}

    displayorder       {2c06c486-872c-11ea-b70d-806e6f6e6963}     <<<Direct boot to hard drive

                               {aadb063e-872b-11ea-830f-c4acb7ccc0f1}

                               {bootmgr}                                                          <<<Windows Boot Manager

    timeout              2

    It's booting directly to the HDD instead of to the Windows Boot Manager. But Windows should always boot to the latter. This could well be the reason the computer fails to update. Can you get into BIOS Setup & move {BootMgr} to the top at the Boot Order page? Might be best to do it that way, but I think this does it too, at an Administrator Command Prompt...

    BCDEdit  /Set  {FWBootMgr}  DisplayOrder  {BootMgr}  /AddFirst

    Those are pointed braces which are above square brackets on the keyboard. It will go into effect at your next reboot.

    PS. I'm here in the USA standing on my head from your perspective.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2021-02-08T09:51:25+00:00

    Woohoo!!

    That did the trick - it skipped the 1090 Update and;

    Feature update to Windows 10, version 20H2

    Successfully installed on ‎8/‎02/‎2021

    Your last command was not quite syntactically correct, but this worked;

    C:\Windows\system32>BCDEdit  /Set  {fwbootmgr}  DisplayOrder  {bootmgr}  /AddFirst

    The operation completed successfully.

    C:\Windows\system32>

    "Your blood should be bottled" as we say downunder!! ie You are worth more money...

    In fact you could send me a BSV public key and I could give you some BSV if that's allowed on this forum (BSV is all I use online :-). Or connect with me on powping.com @jasmr and I can tip you.

    I installed an SSD in this when I did the upgrade on a really old Toshiba and it now boots blindingly fast - must be cutting into new computer sales?

    Regards

    JamesR

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2021-02-08T11:42:53+00:00

    I am overjoyed to hear it. You are welcome.

    No money of any kind is desired. Thanks for the generous comments of praise. Good that you spotted & were able to correct the syntax. I've fixed it in the post & actually just logged on to fix it having realized it myself. My printout of the help screens have faded, & the forward slashes are barely readable. I'm considering getting an SSD myself. Thanks for the report on that.

    Good luck, & keep us informed.

    Was this answer helpful?

    0 comments