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-01-21T21:18:40+00:00

    Your Disk Management (DM) matches DiskPart in what it says is the nutty order of those partitions, (keeping in mind that DM never shows the MSR). So your Linux partition is partition 5 but it precedes partition 4 on the disk. That's scary enough. But, on top of that, DM says it is Disk 0 that holds those partitions where DiskPart says it is Disk 1. (You've got a Disk 1, but it doesn't have those partitions.)

    Image

    Image

    DISKPART> sel disk 1                                                  <<<Disk 1 was selected

    Datenträger 1 ist jetzt der gewählte Datenträger.

    DISKPART> list par                                                        <<<And here are the wacky partitions

      Partition ###  Typ               Größe    Offset

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

      Partition 1    System             100 MB  1024 KB             <<<EFI

      Partition 2    Reserviert          16 MB   101 MB              <<<MSR

      Partition 3    Primär             203 GB   117 MB               <<<Windows

      Partition 5    Unbekannt           19 GB   203 GB             <<<Not a known partition type - Linux

    * Partition 4    Wiederherstellun   521 MB   223 GB        <<<Recovery

    Your BCDEdit & ReagentC look OK to me. The latter agrees with DM that the partitions are on Disk 0.

    Did you say you tried to delete that Linux partition. Are you still willing to do so? It's in a nice enough spot that you will be able to extend C:partition into the 19 GB of freed space. DM can do that, after you delete the partition in DiskPart. Let's see this...

    DiskPart

    List  Vol

    List  Disk

    Select  Disk  0

    List  Part

    Select  Disk  1

    List  Part

    Select  Disk  2

    List  Part

    Exit

    It's worth one more look before we do the delete.

    BIOS probably would continue to work as is, but I'd want to remove the Linux entries. Also, I must admit, I can't quite tell whether it is booting to the Windows Boot Manager or directly to the disk (whatever that is)...

    Image

    I don't think mine names the disk, but just says "Windows Boot Manager". If you can get it like that, it would be best. Yours looks like a list of disks, but really they are all the same disk which likely is Disk 0. I suppose the bottom 2 go to the same Linux partition 5. The top one goes to EFI partition 1, I guess.

    Let's see the whole BCD:     BCDEdit  /Enum  All

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-01-21T08:10:16+00:00

    (3) So its Disk 1 which is selected. 

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-01-21T07:57:38+00:00

    On the 20 GB par is running Linux. This ist par 5. could that be the answer to (1) (a)?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-01-21T07:54:23+00:00

    (1)

    (a) Yes i was once dooing partiton work. I dont exactly know what is was, but i had an error, where i was not able to boot so i did some partition work. I only know there was some kind of missing data in the EFI partition.

    (b) It was a long time ago but it could be, that ive deletet this partiton.

    (3) I will try with the next boot, to look from which disk it is booting.

    (4)

    Hope you can read it

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-01-21T00:39:57+00:00

    (1) You selected Disk 1 then listed its partitions...

    DISKPART> list par

      Partition ###  Typ               Größe    Offset

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

      Partition 1    System             100 MB  1024 KB             <<<EFI

      Partition 2    Reserviert          16 MB   101 MB              <<<MSR

      Partition 3    Primär             203 GB   117 MB               <<<Windows

      Partition 5    Unbekannt           19 GB   203 GB             <<<Not a known partition type

    * Partition 4    Wiederherstellun   521 MB   223 GB        <<<Recovery

    (a) How does partition 4 come after 5? Were you doing partition work of some kind? You should do a reboot as soon as possible after partition work so that the full system knows of the changes. After a reboot, I'm hopeful 4 & 5 will be listed in the right order.

    (b) Unbekannt means "unknown". Normally I'd want to say it was a factory reinstall partition. But those usually have the same partition type of a Recovery partition, i.e., Wiederherstellun. Have you altered its partition type?

    (2) Your ReagentC shows...

    WinRE-Status:      Enabled

    WinRE-Ort:          \?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE

    Partition 4 is good, but it says "harddisk0". That's Disk 0. So I suspect you've got two complete installations of Windows plugged in at once, which is no good. Especially, you don't want two EFI partitions. Windows can be confused when it does a reboot as to which should be used.

    (3) Your BCDEdit says EFI is on "HarddiskVolume1"...

    Windows-Start-Manager


    Bezeichner           {bootmgr}

    device                  partition=\Device\HarddiskVolume1             <<<Partition 1

    path                    \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI

    HarddiskVolume1 means Partition 1, but which Disk is it referring to? I used to say it would be Disk 0, because it counts partitions starting from Disk 0. But now I think, if you booted directly from BIOS to Disk 1, it might start counting from there. Then, it's saying the EFI on Disk 1 was used to achieve the boot. Do you know if BIOS is set to boot directly to Disk 1?

    (4) Show us a "right-click START, Disk Management". Use the separator lines in the header to make the columns readable. Use the separator line between the panes to scrunch it smaller, but show all the Disks.

    Was this answer helpful?

    0 comments No comments