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
    2020-02-13T04:24:50+00:00

    I don't know that it would be a cure, but you may as well check whether your EFI partition has the right ID GUID...

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

    (2) Enter the following commands...

    DiskPart

    Select  Disk  0

    List  Part

    Select  Part  1 <<< If your System (EFI) partition is partition 1

    Detail  Part

    Exit

    Microsoft Windows [Version 10.0.18363.657]

    (c) 2019 Microsoft Corporation. All rights reserved.

    C:\WINDOWS\system32>DiskPart

    Microsoft DiskPart version 10.0.18362.1

    Copyright (C) Microsoft Corporation.

    On computer: PCRSCOMPUTER

    DISKPART> Select Disk 0

    Disk 0 is now the selected disk.

    DISKPART> List Part

      Partition ###  Type              Size     Offset

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

      Partition 1    System          99 MB    32 KB        <<< EFI is the System partition

      Partition 2    Reserved       16 MB   100 MB              

      Partition 3    Primary        930 GB   116 MB

      Partition 4    Recovery      790 MB   930 GB

    DISKPART> Select Part 1                                    <<< Select the System (EFI) partition

                                                                                         (Your number may be different from mine)

    Partition 1 is now the selected partition.

    DISKPART> Detail Part

    Partition 1

    Type    : c12a7328-f81f-11d2-ba4b-00a0c93ec93b      <<< That should be its ID

    Hidden  : Yes

    Required: No

    Attrib  : 0X8000000000000000

    Offset in Bytes: 32768

      Volume ###  Ltr  Label         Fs          Type      Size     Status        Info

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

    * Volume 3               ESP   FAT32    Partition  99 MB   Healthy  System

    DISKPART> Exit

    Leaving DiskPart...

    C:\WINDOWS\system32>

    If yours is different from that, I'll tell you how to set it right. But use CTRL-A & CTRL-C to copy your result & post it to us first so that we may inspect it.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  2. Anonymous
    2020-02-13T10:18:44+00:00

    PCR wrote "I don't know that it would be a cure, but you may as well check whether your EFI partition has the right ID GUID..."

    As you saw in my post on February 2, that was indeed the solution.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2020-02-13T21:33:31+00:00

    I still wonder whether the case is the same for CuongPN.

    BTW, I once messed with my EFI & had to restore its proper ID GUID afterward (& its attributes too, IIRC). But in the meantime an update never tried to enter (or so I don't recall), so I can't personally vouch it fixes  that. Also, I want to say it's never been necessary for me to increase EFI's size. In fact it used to be 100 MB but got down to 99 by messing with it. Still no update problem.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2020-03-15T08:04:31+00:00

    Exactly the same problem on same version. Stops at 94%

    My Windows 10 is a recent download performed with the help of MS second level support on 20/02/20 when the previous Cumulative Update failed. 

    Will contact them again next week

    Was this answer helpful?

    0 comments
  5. Anonymous
    2020-03-17T15:16:36+00:00

    Hi,

    Having experienced exactly the same issue described in these posts and with a recently reset windows 10 installation. I was following the above and I have participation 2 set with the correct guid, is it possible the system partition is not sufficiently large? 

    DISKPART> select disk 2

    Disk 2 is now the selected disk.

    DISKPART> detail part

    There is no partition selected.

    Please select a partition and try again.

    DISKPART> list part

      Partition ###  Type              Size     Offset

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

      Partition 1    Recovery           529 MB  1024 KB

      Partition 2    System             100 MB   530 MB

      Partition 3    Reserved            16 MB   630 MB

      Partition 4    Primary            465 GB   646 MB

    DISKPART> select part 2

    Partition 2 is now the selected partition.

    DISKPART> detail part 2

    The arguments specified for this command are not valid.

    For more information on the command type: HELP DETAIL PARTITION

    DISKPART> detail part

    Partition 2

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

    Hidden  : Yes

    Required: No

    Attrib  : 0X8000000000000000

    Offset in Bytes: 555745280

      Volume ###  Ltr  Label        Fs     Type        Size     Status     Info

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

    * Volume 5                      FAT32  Partition    100 MB  Healthy    System

    Was this answer helpful?

    0 comments