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 No comments

133 answers

Sort by: Newest
  1. Anonymous
    2021-05-15T09:24:37+00:00

    Dear Microsoft,

    Curses.

    With kind regards, Mr this is really frustrating thanks for taking another hour of my life. It would have been more, but I've grown smart enough to give up on these broken updates.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-04-12T02:17:12+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-04-11T15:24:01+00:00

    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

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-02-11T20:24:50+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-02-11T19:30:18+00:00

    JohnTimmermans1,

    (1) First, let's see whether you've got a System partition (EFI or System Reserved) on the other disks. Show a "right-click START, Disk Management". Use the divider lines in the Header to make each column fully readable. Show all the disks, but scrunch it smaller using the divider line between the panes.

    (2) If there is an extra System partition on one, we'd have to research...

    (a) Would disabling the disk(s) in Device Manager do it?

    (b) If an EFI, how about just changing its ID to something else?

    (c) If a System Reserved, would removing its Active attribute be enough?

    I don't know, it would take research or trial & error to know. Unplugging it probably is best.

    Was this answer helpful?

    0 comments No comments