Solved Is it possible to create system reserved partition manually ?

Always Why · Jan 13, 2022

William654 said:
I:\
How I remove all the other orphans enteries please ?

Start over. It's easier and far less frustrating. I agree it's tedious reinstalling your programs/apps but you'll have a pristine system. Also, unplug any external drives or internal backup drives so the new installation sees your Primary Drive, which it will name C by default. You'll have about 3 or 4 other partitions once it's installed as GPT volumes which Windows 10 and 11 do automatically.

Note: This will happen on computers built or purchased in the last seven years which had state-of-the-art tech/hardware and BIOS in them at the time. Speaking of BIOS. Check your motherboard on the mfg's site and download the latest BIOS too.

Is it possible to create system reserved partition manually ?

Here is how the successful commands looked on my computer: Microsoft Windows [Version 10.0.22000.434] (c) Microsoft Corporation. All rights reserved. C:\windows\system32>diskpart Microsoft DiskPart version 10.0.22000.1 Copyright (C) Microsoft Corporation. On computer: RAIDER DISKPART>...

www.elevenforum.com

zbook · Jan 13, 2022

When there is failure to upgrade Windows creates log files.

The challenge is sifting through these logs to identify the problem(s).
The next challenge is creating various trial and error steps.

Alternatively you can perform general troubleshooting steps.

Often substantial time can be spent troubleshooting.
That needs to be compared to the time spent backing up files, clean install, reinstalling drivers and applications.

SIW2 · Jan 13, 2022

NavyLCDR said:
Some UEFI computers can boot from NTFS and on those computers it is entirely 100% possible to boot from the C: drive Windows partition from a GPT disk.

Correct or even from a separate disk that has the the efi boot files.

You could look in registry for firmware boot device

HKLM\SYSTEM\CurrentControlSet\Control\FirmwareBootDevice

or I have a little script that does it, but it would need compiling for anyone else to use it

William654 · Jan 13, 2022

Here is the last update: I removed extra enteries using Visual BCD then I tried to update and this time ...viola it is updated :)

I am on OS build 22000.434
Experience Windows Feature Experience Pack 1000.22000.434.0

EFI partition was the problem

NavyLCDR · Jan 13, 2022

@William654,

If you want to proceed with the process of getting your computer to boot from a separate EFI system partition, the next step would be to ensure that you have proper boot files established on the EFI System Partition that you created. You gave it drive letter I:. Assuming that it still has drive letter I:, the command would be:

Code:

bcdedit /store I:\EFI\Microsoft\boot\BCD

The result should look like:

Code:

C:\Windows\System32>bcdedit /store I:\EFI\Microsoft\boot\BCD

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=I:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {d876edba-749f-11ec-980a-2c8db1e3769f}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {d876edba-749f-11ec-980a-2c8db1e3769f}
nx                      OptIn
bootmenupolicy          Standard

C:\Windows\System32>

NavyLCDR · Jan 13, 2022

William654 said:
Here is the last update: I removed extra enteries using Visual BCD then I tried to update and this time ...viola it is updated :)

I am on OS build 22000.434
Experience Windows Feature Experience Pack 1000.22000.434.0

EFI partition was the problem

That is great news! Good to hear that creating a real EFI System Partition and getting your computer to boot from it solved your problem!

William654 · Jan 13, 2022

NavyLCDR said:

@William654,

If you want to proceed with the process of getting your computer to boot from a separate EFI system partition, the next step would be to ensure that you have proper boot files established on the EFI System Partition that you created. You gave it drive letter I:. Assuming that it still has drive letter I:, the command would be:

Code:

bcdedit /store I:\EFI\Microsoft\boot\BCD

The result should look like:

Code:

C:\Windows\System32>bcdedit /store I:\EFI\Microsoft\boot\BCD

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=I:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {d876edba-749f-11ec-980a-2c8db1e3769f}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.efi
description             Windows 11
locale                  en-us
inherit                 {bootloadersettings}
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \Windows
resumeobject            {d876edba-749f-11ec-980a-2c8db1e3769f}
nx                      OptIn
bootmenupolicy          Standard

C:\Windows\System32>

It has not drive letter now and I can not assign any from disk management

William654 · Jan 13, 2022

I am not sure I am booting from EFI partition how I know ?

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 {default}
resumeobject {cf64f082-74a4-11ec-b5cc-087190bfe608}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.efi
description Windows 11
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \Windows
resumeobject {cf64f082-74a4-11ec-b5cc-087190bfe608}
nx OptIn
bootmenupolicy Standard

NavyLCDR · Jan 13, 2022

William654 said:
I am not sure I am booting from EFI partition how I know ?

diskpart
list vol

Your bcdedit shows that you are booting from Volume 2, Also, see @SIW2 excellent post #42. You were originally getting a bcdedit error that the BCD store could not be opened. Whatever happened to fix that problem is what fixed your update problem.

zbook · Jan 13, 2022

Which link had given you information about the upgrade failure code being caused by the reserved partition?

In post #4 you had reported:
0x800f0922

Setupdiag reported:
0x800704C7 - 0x40004

William654 · Jan 13, 2022

zbook said:
Which link had given you information about the upgrade failure code being caused by the reserved partition?

It was from google but also one from Microsoft support suggest the same.

William654 · Jan 13, 2022

zbook said:
Which link had given you information about the upgrade failure code being caused by the reserved partition?

In post #4 you had reported:
0x800f0922

Setupdiag reported:
0x800704C7 - 0x40004

found the first number in the software distribution folder, there is a log there

zbook · Jan 13, 2022

If available please post the link(s).

Where was the first error code seen?
Windows updates?

What was the name of the log file?

William654 · Jan 13, 2022

zbook said:
If available please post the link(s).

Where was the first error code seen?
Windows updates?

here is one

Windows Update Error 0x800f0922

Hi, while most recent (14/02/18) auto updates were installing they failed and windows removed failed files. Problem error code 0x800f0992 appeared, not sure what to do as website does not explain how

answers.microsoft.com