On the 20 GB par is running Linux. This ist par 5. could that be the answer to (1) (a)?
Error 0x800f0922 for 2020-01 Cumulative Update for Windows 10 Version 1909 for x64-based Systems (KB4532695)
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.
133 answers
Sort by: Oldest
-
Anonymous
2021-01-21T07:57:38+00:00 -
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.)
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)...
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
-
Anonymous
2021-01-22T08:51:20+00:00 Here is Disk Manager:
DISKPART> List Vol
Volume ### Bst Bezeichnung DS Typ Größe Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
Volume 0 C NTFS Partition 203 GB Fehlerfrei Startpar
Volume 1 NTFS Partition 521 MB Fehlerfrei
Volume 2 FAT32 Partition 100 MB Fehlerfre System
Volume 3 D Volume NTFS Partition 931 GB Fehlerfrei
Volume 4 E Volume NTFS Partition 447 GB Fehlerfrei
DISKPART>
DISKPART> List Disk
Datenträger ### Status Größe Frei Dyn GPT
--------------- ------------- ------- ------- --- ---
Datenträger 0 Online 223 GB 1024 KB *
Datenträger 1 Online 931 GB 1024 KB *
Datenträger 2 Online 447 GB 1024 KB *
DISKPART>
DISKPART> Select Disk 0
Datenträger 0 ist jetzt der gewählte Datenträger.
DISKPART>
DISKPART> List Part
Partition ### Typ Größe Offset
------------- ---------------- ------- -------
Partition 1 System 100 MB 1024 KB
Partition 2 Reserviert 16 MB 101 MB
Partition 3 Primär 203 GB 117 MB
Partition 5 Unbekannt 19 GB 203 GB
Partition 4 Wiederherstellun 521 MB 223 GB
DISKPART>
DISKPART> Select Disk 1
Datenträger 1 ist jetzt der gewählte Datenträger.
DISKPART>
DISKPART> List Part
Partition ### Typ Größe Offset
------------- ---------------- ------- -------
Partition 1 Reserviert 15 MB 17 KB
Partition 2 Primär 931 GB 16 MB
DISKPART>
DISKPART> Select Disk 2
Datenträger 2 ist jetzt der gewählte Datenträger.
DISKPART>
DISKPART> List Part
Partition ### Typ Größe Offset
------------- ---------------- ------- -------
Partition 1 Reserviert 15 MB 17 KB
Partition 2 Primär 447 GB 16 MB
DISKPART>
DISKPART> Exit
And BCD:
C:\WINDOWS\system32>BCDEdit /Enum All
Start-Manager für Firmware
Bezeichner {fwbootmgr}
displayorder {bootmgr}
{bc3fa510-fe92-11ea-b227-806e6f6e6963}
{bc3fa50f-fe92-11ea-b227-806e6f6e6963}
{7c737fc1-dbb4-11ea-8708-836fcd478fb1}
timeout 1
Windows-Start-Manager
Bezeichner {bootmgr}
device partition=\Device\HarddiskVolume1
path \EFI\MICROSOFT\BOOT\BOOTMGFW.EFI
description Windows Boot Manager
locale de-DE
inherit {globalsettings}
default {current}
resumeobject {80bb344c-fc52-11ea-b786-dae81f622fe9}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Firmwareanwendung (101fffff)
Bezeichner {7c737fc1-dbb4-11ea-8708-836fcd478fb1}
description Hard Drive
Firmwareanwendung (101fffff)
Bezeichner {bc3fa50f-fe92-11ea-b227-806e6f6e6963}
device partition=\Device\HarddiskVolume1
path \EFI\UBUNTU\SHIMX64.EFI
description ubuntu
Firmwareanwendung (101fffff)
Bezeichner {bc3fa510-fe92-11ea-b227-806e6f6e6963}
device partition=\Device\HarddiskVolume1
path \EFI\UBUNTU\GRUBX64.EFI
description ubuntu
Windows-Startladeprogramm
Bezeichner {current}
device partition=C:
path \WINDOWS\system32\winload.efi
description Windows 10
locale de-DE
inherit {bootloadersettings}
recoverysequence {ae3879e3-fb7f-11ea-bd25-7085c25d426a}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \WINDOWS
resumeobject {80bb344c-fc52-11ea-b786-dae81f622fe9}
nx OptIn
bootmenupolicy Standard
Windows-Startladeprogramm
Bezeichner {ae3879e3-fb7f-11ea-bd25-7085c25d426a}
device ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{ae3879e4-fb7f-11ea-bd25-7085c25d426a}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale de-DE
inherit {bootloadersettings}
displaymessage Recovery
displaymessageoverride PushButtonReset
osdevice ramdisk=[\Device\HarddiskVolume5]\Recovery\WindowsRE\Winre.wim,{ae3879e4-fb7f-11ea-bd25-7085c25d426a}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes
Wiederaufnahme aus dem Ruhezustand
Bezeichner {80bb344c-fc52-11ea-b786-dae81f622fe9}
device partition=C:
path \WINDOWS\system32\winresume.efi
description Windows Resume Application
locale de-DE
inherit {resumeloadersettings}
recoverysequence {ae3879e3-fb7f-11ea-bd25-7085c25d426a}
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filedevice partition=C:
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Windows-Speichertestprogramm
Bezeichner {memdiag}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\memtest.efi
description Windows-Speicherdiagnose
locale de-DE
inherit {globalsettings}
badmemoryaccess Yes
EMS-Einstellungen
Bezeichner {emssettings}
bootems No
Debuggereinstellungen
Bezeichner {dbgsettings}
debugtype Local
RAM-Defekte
Bezeichner {badmemory}
Globale Einstellungen
Bezeichner {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Startladeprogramm-Einstellungen
Bezeichner {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisoreinstellungen
Bezeichner {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Einstellungen zur Ladeprogrammfortsetzung
Bezeichner {resumeloadersettings}
inherit {globalsettings}
Geräteoptionen
Bezeichner {ae3879e4-fb7f-11ea-bd25-7085c25d426a}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume5
ramdisksdipath \Recovery\WindowsRE\boot.sdi
Thanks for your help
-
Anonymous
2021-01-22T22:59:53+00:00 (1) So now DiskPart does agree that your Windows partitions & Ubuntu are on Disk 0. That's great. Sadly, the positions of partitions 4 & 5 are still switched on the disk. That doesn't seem natural to me. And within the BCD it is saying the Recovery partition (Shift+Restart goes there) is on Partition 5...
Geräteoptionen
Bezeichner {ae3879e4-fb7f-11ea-bd25-7085c25d426a}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume5 <<<Partition 5
ramdisksdipath \Recovery\WindowsRE\boot.sdi
That's its correct position on Disk 0, but it everywhere else is known as ...4. Even ReagentC calls it 4.
(2) I like seeing {bootmgr} on top here...
Start-Manager für Firmware
Bezeichner {fwbootmgr}
displayorder {bootmgr} <<<Windows Boot Manager
{bc3fa510-fe92-11ea-b227-806e6f6e6963} <<<Direct to Ubuntu
{bc3fa50f-fe92-11ea-b227-806e6f6e6963} <<<Direct to Ubuntu (same one I guess)
{7c737fc1-dbb4-11ea-8708-836fcd478fb1} <<<Direct to "Hard Drive"
timeout 1
I think Windows likes that when it needs to do a reboot. It wants {Bootmgr} to determine which OS to boot. Unfortunately, there is no boot loader entry for Ubuntu; so, that never will be a choice. You can only direct-boot to Ubuntu. I don't know why you've got two entries for Ubuntu when I see only one partition -- weird partition 5.
(3) What happens when you boot to Ubuntu? Is there an uninstall procedure for it? Looks like it's put a folder into EFI...
Firmwareanwendung (101fffff)
Bezeichner {bc3fa50f-fe92-11ea-b227-806e6f6e6963}
device partition=\Device\HarddiskVolume1
path \EFI\UBUNTU\SHIMX64.EFI <<<Ubuntu boot loader on EFI
description ubuntu
I think I would uninstall it, delete partition 5, then reinstall it if still wanted.