Solved In-place upgrade: Couldn't update the System reserved partition

sbee · Aug 1, 2024

Was trying to assist someone that experienced responsive issues related to the taskbar, start button and search field. After several tries to uninstall recently installed windows updates without any success i decided to do an in-place upgrade.

This however failed with the following error message:

I've tried the below but the issue persists:
“We couldn’t update system reserved partition” error installing Windows 10 - Microsoft Support

In case it is usefull this is a screenshot of diskmanagement:

NB: Windows 11 Enterprise 23H2 (64 bits) is already installed on the device.

zbook · Aug 1, 2024

1) Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

BSOD - Posting Instructions

2) Run Disk partition information > post a share link

https://www.tenforums.com/attachmen...atch-files-use-bsod-debugging-diskparinfo.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums

antspants · Aug 1, 2024

Welcome to the forum

sbee said:
Windows 11 Enterprise 23H2 (64 bits) is already installed on the device.

Then possibly Enterprise was installed with a bypass added to ignore the restrictions, meaning the PC possibly is not eligible to run Windows 11.

Download the ISO, create an install USB using RUFUS.
Then use option two here. Read the tutorial through first:

Repair Install Windows 11 with an In-place Upgrade Tutorial

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

Rufus - Create bootable USB drives the easy way

Rufus: Create bootable USB drives the easy way

rufus.ie

Change the settings after you have setup the first window in RUFUS and after you press start, to ignore requirements for Windows 11.

sbee · Aug 5, 2024

zbook said:
1) Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

BSOD - Posting Instructions

2) Run Disk partition information > post a share link

https://www.tenforums.com/attachmen...atch-files-use-bsod-debugging-diskparinfo.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums

@zbook Thanks alot for your quick reply! I have run the collector and retrieved the partition info. As for the collector i'm unfortunately quite restricted in what I can share. Is it possible to specify which part of the gathered info you need to this particular issue?

As for 2:

Code:

    Disk 0 : SSD. It has 4 partition(s). Model: NVMe PM9A1 NVMe Samsung 512GB

    The script has found the above 1 storage device(s) in total.
=======================================================================

Microsoft DiskPart-Version 10.0.19041.3636

Copyright (C) Microsoft Corporation.
Auf Computer: **********

  Datentr„ger ###  Status         Gr”áe    Frei     Dyn  GPT
  ---------------  -------------  -------  -------  ---  ---
  Datentr„ger 0    Online          476 GB      0 B        *

  Volume ###  Bst  Bezeichnung  DS     Typ         Gr”áe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    474 GB  Fehlerfre  Startpar
  Volume 1                      FAT32  Partition    100 MB  Fehlerfre  System  
  Volume 2         Windows RE   NTFS   Partition   2662 MB  Fehlerfre  Versteck

Datentr„ger 0 ist jetzt der gew„hlte Datentr„ger.

NVMe PM9A1 NVMe Samsung 512GB
Datentr„ger-ID: "{9FE32DDD-21D9-4349-A1**-7D22****5592}"
Typ   : "RAID"
Status : "Online"
Pfad   : "2"
Ziel : "0"
LUN-ID : "0"
Speicherortpfad : "PCIROOT(0)#PCI(0E00)#RAID(P02T00L00)"
Aktueller schreibgeschtzter Zustand: Nein
Schreibgeschtzt  : Nein
Startdatentr„ger  : Ja
Auslagerungsdatei-Datentr„ger  : Ja
Ruhezustandsdatei-Datentr„ger  : Nein
Absturzabbild-Datentr„ger  : Ja
Clusterdatentr„ger : Nein

  Volume ###  Bst  Bezeichnung  DS     Typ         Gr”áe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
  Volume 0     C                NTFS   Partition    474 GB  Fehlerfre  Startpar
  Volume 1                      FAT32  Partition    100 MB  Fehlerfre  System  
  Volume 2         Windows RE   NTFS   Partition   2662 MB  Fehlerfre  Versteck

  Partition ###  Typ               Gr”áe    Offset
  -------------  ----------------  -------  -------
  Partition 1    System             100 MB  1024 KB
  Partition 2    Reserviert          16 MB   101 MB
  Partition 3    Prim„r             474 GB   117 MB
  Partition 4    Wiederherstellun  2662 MB   474 GB

Partition 1 ist jetzt die gew„hlte Partition.

Partition 1
Typ         : c12a7328-f81f-11d2-ba4b-00a0c93ec93b
Versteckt   : Ja
Erforderlich: Nein
Attribut    : 0X8000000000000000
Offset in Byte: 1048576

  Volume ###  Bst  Bezeichnung  DS     Typ         Gr”áe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 1                      FAT32  Partition    100 MB  Fehlerfre  System  

Partition 2 ist jetzt die gew„hlte Partition.

Partition 2
Typ         : e3c9e316-0b5c-4db8-817d-f92df00215ae
Versteckt   : Ja
Erforderlich: Nein
Attribut    : 0X8000000000000000
Offset in Byte: 105906176

Dieser Partition ist kein Volume zugewiesen.

Partition 3 ist jetzt die gew„hlte Partition.

Partition 3
Typ         : ebd0a0a2-b9e5-4433-87c0-68b6b72699c7
Versteckt   : Nein
Erforderlich: Nein
Attribut    : 0000000000000000
Offset in Byte: 122683392

  Volume ###  Bst  Bezeichnung  DS     Typ         Gr”áe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 0     C                NTFS   Partition    474 GB  Fehlerfre  Startpar

Partition 4 ist jetzt die gew„hlte Partition.

Partition 4
Typ         : de94bba4-06d1-4d40-a16a-bfd50179d6ac
Versteckt   : Ja
Erforderlich: Ja
Attribut    : 0X8000000000000001
Offset in Byte: 509318529024

  Volume ###  Bst  Bezeichnung  DS     Typ         Gr”áe    Status     Info
  ----------  ---  -----------  -----  ----------  -------  ---------  --------
* Volume 2         Windows RE   NTFS   Partition   2662 MB  Fehlerfre  Versteck

===============================================================================

Konfigurationsinformationen zur Windows-Wiederherstellungsumgebung (WinRE) und
zur Systemwiederherstellung:

    WinRE-Status:                          Enabled
    WinRE-Ort:                             \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE
    Startkonfigurationsdaten-ID:           7943d2e8-d712-11ee-a6f8-ac74b1762649
    Ort des Wiederherstellungsimages:      
    Index des Wiederherstellungsimages:    0
    Ort des benutzerdefinierten Images:    
    Index des benutzerdefinierten Images:  0

REAGENTC.EXE: Vorgang erfolgreich.
    
===============================================================================

Start-Manager fr Firmware
--------------------------
Bezeichner              {fwbootmgr}
displayorder            {bootmgr}
                        {623a6870-8ec7-11ec-9c01-fb66b1f4ff8f}
                        {623a686e-8ec7-11ec-9c01-fb66b1f4ff8f}
                        {623a686f-8ec7-11ec-9c01-fb66b1f4ff8f}
                        {623a6871-8ec7-11ec-9c01-fb66b1f4ff8f}
                        {9ccca31a-5095-11ef-a7a9-806e6f6e6963}
                        {9ccca31b-5095-11ef-a7a9-806e6f6e6963}
                        {9ccca31c-5095-11ef-a7a9-806e6f6e6963}
timeout                 2

Windows-Start-Manager
---------------------
Bezeichner              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  ****
inherit                 {globalsettings}
isolatedcontext         Yes
fverecoverymessage      ****
default                 {current}
resumeobject            {5bd84be0-9770-11ed-a260-c692d9e82c26}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {623a686e-8ec7-11ec-9c01-fb66b1f4ff8f}
description             ONBOARD NIC (IPV4)
isolatedcontext         Yes

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {623a686f-8ec7-11ec-9c01-fb66b1f4ff8f}
description             ONBOARD NIC (IPV6)
isolatedcontext         Yes

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {623a6870-8ec7-11ec-9c01-fb66b1f4ff8f}
description             UEFI HTTPs Boot
isolatedcontext         Yes

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {623a6871-8ec7-11ec-9c01-fb66b1f4ff8f}
device                  partition=\Device\HarddiskVolume1
path                    \EFI\Boot\BootX64.efi
description             UEFI RST PM9A1 NVMe Samsung 512GB S65RNF1R842840 
isolatedcontext         Yes

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {9ccca31a-5095-11ef-a7a9-806e6f6e6963}
description             USB NIC (IPV4)
isolatedcontext         Yes

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {9ccca31b-5095-11ef-a7a9-806e6f6e6963}
description             USB NIC (IPV6)
isolatedcontext         Yes

Firmwareanwendung (101fffff)
----------------------------
Bezeichner              {9ccca31c-5095-11ef-a7a9-806e6f6e6963}
description             UEFI HTTPs Boot (MAC:A02919A8C597)
isolatedcontext         Yes

Windows-Startladeprogramm
-------------------------
Bezeichner              {current}
device                  partition=C:
path                    \WINDOWS\system32\winload.efi
description             Windows 10
locale                  ****
inherit                 {bootloadersettings}
recoverysequence        {7943d2e8-d712-11ee-a6f8-ac74b1762649}
displaymessageoverride  Recovery
recoveryenabled         Yes
isolatedcontext         Yes
allowedinmemorysettings 0x15000075
osdevice                partition=C:
systemroot              \WINDOWS
resumeobject            {5bd84be0-9770-11ed-a260-c692d9e82c26}
nx                      OptIn
bootmenupolicy          Standard

Windows-Startladeprogramm
-------------------------
Bezeichner              {7943d2e8-d712-11ee-a6f8-ac74b1762649}
device                  ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{7943d2e9-d712-11ee-a6f8-ac74b1762649}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment
locale                  ****
inherit                 {bootloadersettings}
displaymessage          Recovery
isolatedcontext         Yes
osdevice                ramdisk=[\Device\HarddiskVolume4]\Recovery\WindowsRE\Winre.wim,{7943d2e9-d712-11ee-a6f8-ac74b1762649}
systemroot              \windows
nx                      OptIn
bootmenupolicy          Standard
winpe                   Yes

Wiederaufnahme aus dem Ruhezustand
----------------------------------
Bezeichner              {5bd84be0-9770-11ed-a260-c692d9e82c26}
device                  partition=C:
path                    \WINDOWS\system32\winresume.efi
description             Windows Resume Application
locale                  ****
inherit                 {resumeloadersettings}
recoverysequence        {7943d2e8-d712-11ee-a6f8-ac74b1762649}
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 Memory Diagnostic
locale                  ****
inherit                 {globalsettings}
badmemoryaccess         Yes
isolatedcontext         Yes

EMS-Einstellungen
-----------------
Bezeichner              {emssettings}
bootems                 No
isolatedcontext         Yes

Debuggereinstellungen
---------------------
Bezeichner              {dbgsettings}
debugtype               Local
isolatedcontext         Yes

RAM-Defekte
-----------
Bezeichner              {badmemory}
isolatedcontext         Yes

Globale Einstellungen
---------------------
Bezeichner              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}
isolatedcontext         Yes

Startladeprogramm-Einstellungen
-------------------------------
Bezeichner              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}
isolatedcontext         Yes

Hypervisoreinstellungen
-----------------------
Bezeichner              {hypervisorsettings}
isolatedcontext         Yes
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Einstellungen zur Ladeprogrammfortsetzung
-----------------------------------------
Bezeichner              {resumeloadersettings}
inherit                 {globalsettings}
isolatedcontext         Yes

Ger„teoptionen
--------------
Bezeichner              {7943d2e9-d712-11ee-a6f8-ac74b1762649}
description             Windows Recovery
isolatedcontext         Yes
ramdisksdidevice        partition=\Device\HarddiskVolume4
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

sbee · Aug 5, 2024

antspants said:
Welcome to the forum

Then possibly Enterprise was installed with a bypass added to ignore the restrictions, meaning the PC possibly is not eligible to run Windows 11.

Download the ISO, create an install USB using RUFUS.
Then use option two here. Read the tutorial through first:

Repair Install Windows 11 with an In-place Upgrade Tutorial

This tutorial will show you how to do a repair install of Windows 11 by performing an in-place upgrade without losing anything. If you need to repair or create a new recovery partition or having problems with the Windows 11 operating system on your PC, and the usual solutions will not fix it...

www.elevenforum.com

Rufus - Create bootable USB drives the easy way

Rufus: Create bootable USB drives the easy way

rufus.ie

Change the settings after you have setup the first window in RUFUS and after you press start, to ignore requirements for Windows 11.

@antspants, Thank you for the welcoming message and quick response. First time posting here but have been a long time in the shadows following your great tutorials and support to the community.

Thank you for the suggestion, but I prefer to find the cause of the issue as it is showing up more often lately and applying your suggestion isn't always possible due to practical reasons.

antspants · Aug 5, 2024

sbee said:
@antspants, Thank you for the welcoming message and quick response. First time posting here but have been a long time in the shadows following your great tutorials and support to the community.

Thank you for the suggestion, but I prefer to find the cause of the issue as it is showing up more often lately and applying your suggestion isn't always possible due to practical reasons.

sbee said:
i decided to do an in-place upgrade.

What I posted was the correct way to perform an in-place upgrade, which you said you tried, hence the error message.

Using RUFUS to create the install media (if not an alternative round about way) is used for nothing more than tricking Windows into believing the PC is supported for Windows 11. Just because it is currently running Enterprise, could simply mean that a work around was used to install it.
What are the exact PC specs?

The Media is created using RUFUS with the Windows ISO, then the Media is used to perform the In-Place upgrade.
If the PC you're working on is "unsupported" then it's exactly (in my opinion) why you're having problems.

Being informed that "This PC doesn't meet currently meet..." (screenshot) and the partition, aren't related as far as I know.

antspants · Aug 5, 2024

zbook said:
1) Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

BSOD - Posting Instructions

2) Run Disk partition information > post a share link

https://www.tenforums.com/attachmen...atch-files-use-bsod-debugging-diskparinfo.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Batch files for use in BSOD debugging - Windows 10 Help Forums

I'm curious as to what the taskbar, start button, search field and a PC being unsupported to run Windows 11 have to do with a partition?
Interested only because I've never heard of it.

sbee · Aug 5, 2024

antspants said:
What I posted was the correct way to perform an in-place upgrade, which you said you tried, hence the error message.

Using RUFUS to create the install media (if not an alternative round about way) is used for nothing more than tricking Windows into believing the PC is supported for Windows 11. Just because it is currently running Enterprise, could simply mean that a work around was used to install it.
What are the exact PC specs?

The Media is created using RUFUS with the Windows ISO, then the Media is used to perform the In-Place upgrade.
If the PC you're working on is "unsupported" then it's exactly (in my opinion) why you're having problems.

Being informed that "This PC doesn't meet currently meet..." (screenshot) and the partition, aren't related as far as I know.

@antspants The method that i've used was the " 4 To Repair Install Windows 11 with an ISO file" without using a usb device. As i'm assisting remotely this is the most practical way to do the in-place upgrade.

What are the exact PC specs?

DELL Latitude 5420
16GB
Intel i5 1145G7
512GB SSD
Intel Iris Xe Graphics

If the PC you're working on is "unsupported" then it's exactly (in my opinion) why you're having problems.

It probably could be, but the strange thing is when running the PC Health Check app to confirm the device meets the minimum system requirements, the results show it does meet the reqs.
By the way there is another Windows 10 Device that I tried to upgrate to windows 11 using the W11 installation Assistant and the exact same error occurred there and also this device got through the pc health check.

Being informed that "This PC doesn't meet currently meet..." (screenshot) and the partition, aren't related as far as I know.

It is not the first time that an error message puts us on the wrong track. But the error clearly refers to the system reserved partition. I therefore read this thread with alot of interest but couldn't figure out where the culprit is.

IanMosley · Aug 5, 2024

sbee said:
Thank you for the suggestion, but I prefer to find the cause of the issue as it is showing up more often lately and applying your suggestion isn't always possible due to practical reasons.

Download and run WhyNotWin11

sbee · Aug 5, 2024

IanMosley said:
Download and run WhyNotWin11

@IanMosley Thank you for the suggestion! However everything is showing green

was hoping for some red though.

antspants · Aug 5, 2024

sbee said:
But the error clearly refers to the system reserved partition.

Now that I put my glasses on, I see that

antspants · Aug 5, 2024

Was there a 4th partition, a 2nd recovery partition (which is often the case as I have read in here) and the owner removed it removing the wrong one?

sbee · Aug 5, 2024

antspants said:
Was there a 4th partition, a 2nd recovery partition (which is often the case as I have read in here) and the owner removed it removing the wrong one?

This indeed could be the case here if I remember well. KB5034441 didn't want to install so one of the 2 recovery partitions was initially removed but probably later on both were removed and these instructions were followed. If this is the cause what should be done to resolve it?

antspants · Aug 5, 2024

Firstly, I shouldn't try helping when I am tired, confusing the SRP and the recovery partition.

Here are some suggestions on replacing/repairing.

System Reserved Partition Deleted? 4 Ways to Recover It Here

Windows partitions can be easily deleted by mistake in people's daily life, including the System Reserved Partition. Follow to learn how to restore the deleted System Reserved Partition when the Windows system can or cannot boot normally with four methods. EaseUS Partition Master will make the...

www.easeus.com

Megahertz · Aug 5, 2024

Windows Disk manager is very basic and it doesn't show the MSR partition and gives wrong information of the EFI and Recovery partition. A good Disk manager is Minitoll partition
You can use diskpart to see all the partitions:
Open a CMD window as administrator and type:

diskpart
select disk 0
list part
exit (to exit diskpart)

zbook · Aug 5, 2024

Please use English as the default language during the troubleshooting so that log files can be scanned and read.

Add, Remove, and Change Display Language in Windows 10

How to Add or Remove Language Packs and Change Display Language in Windows 10

www.tenforums.com

Change Display Language in Windows 10

How to Change Display Language in Windows 10

www.tenforums.com

The V2 log collector does not collect personal files.

It can be deleted after it is downloaded or at the completion of troubleshooting.

BSOD - Posting Instructions

BSOD - Posting Instructions This will show you how to help provide needed information about your system and dump files. It will not contain any personal or sensitive information about you or your data. To get better help with your Windows BSOD issue, please read these instructions and follow...

www.elevenforum.com

sbee · Aug 26, 2024

antspants said:
Firstly, I shouldn't try helping when I am tired, confusing the SRP and the recovery partition.

Here are some suggestions on replacing/repairing.

System Reserved Partition Deleted? 4 Ways to Recover It Here

Windows partitions can be easily deleted by mistake in people's daily life, including the System Reserved Partition. Follow to learn how to restore the deleted System Reserved Partition when the Windows system can or cannot boot normally with four methods. EaseUS Partition Master will make the...

www.easeus.com

I've tested the suggested solution on a virtual machine and it got broken and the operating system couldn't start up anymore. So I haven't tried this on the impacted device.

What I did instead on the device was the following:

I Formatted the system reserved partition and then rebuild it. (there are different ways to do it, one of them is shown here How to create system reserved partition manually? - Windows 10 Help Forums )

This resolved the issue and windows 11 could be (in-place) upgraded successfully. Hope this will help out someone else. Thanks everyone for your input.