"We couldn't update the system reserved partition" failure build 1903

Hello,

I have been plagued by the impossibility of updating build 1809 to 1903 in any way whatsoever. I have tried the long route via Windows Update, but also from an ISO file, with a clean boot, uncoupling of peripherals, stopping my virus scanner and all kinds of other precautions.

If I am to believe the several articles on Internet, mine is an ubiquitous problem. Indeed, after a certain amount of time the update is aborted with the message: "We couldn't update the system reserved partition". No further explanation, not even an error number (which usually is of little or no help anyway).

Now, after reading several articles on the Internet, it appears that this concerns - so much is obvious - a particular partition on the hard drive now called "0" by Windows, which also contains the Operating System on partition C:.

But which of the four partitions on that drive is it? And what should be done to allow Windows to "update the system reserved partition". Even more interestingly for future use, what prevents Windows to "update the system reserved partition"?

However, it appears that said "system reserved partition" has often changed names in the course of the years (apparently after each update). So it is impossible for me to know which is the right one on my system. To all intents, I am attaching a screenshot of Windows Write Management, to allow whoever answers this thread to indicate which of the partitions is the "reserved" one.

Second, what should I do to overcome the apparent impossibility to "update the system reserved partition"?

Disk Management doesn't say it, but Minitool Partition Wizard indicates that said "0" HD is of the MBR type. Please also know that the 4 partitions of said HD cannot be resized, even though the drive seems to be perfectly in order (sectors have been examined, chkdsk has been done on all partitions, as well as all possible other checks). However, several articles on Internet mention that since build 1803 Microsoft would have rendered that kind of access on said drive almost impossible. I seem to have heard that the MBR format prevents manipulation - but am not sure.

Be all that as it may, it remains a galling situation. All the more since Microsoft support, in a most arrogant and sloppy manner, can only suggest a complete clean Windows reinstall to solve the matter. Given the large amount of users confronted with the same problem (tot judge by the Internet), I cannot begin to imagine that all victims of the "We couldn't update the system reserved partition" situation have been obliged to submit to such a drastic measure.

Thanks for your help.

haku

Disk 0 Partition 1 is too small. It needs to be increased to 150MB. You can use MiniTool position Wizard Free to do it.

Hi,
Thanks. I have screenshots of all partitions drive "0" and it appears that Partition 1 is indeed the system reserved one. After reading the first article you mentioned [What is the System Reserved or EFI Partition in Windows?], I checked the contents of that partition 1 and it corresponds with the contents described in that article.
[Aside: Microsoft support, which is manned by people who don't know chalk from cheese, suggested I should delete said partition!!! The gentleman on the other side of the line said literally he didn't know what the 100 MB partition was for. Can you imagine? Fortunately I knew better...]
Now the screenshots of Write Management with the respective properties of each disk will show you the amount of used and unused space.
You ask for a screenshot of MiniTool. There we get into even more weird terrain. Whereas Windows Write Management shows that the partitions are NFTS, MiniTool shows neither used/unused parts, and says "Other" about the format. MiniTool Support said: "Windows Disk Management can detect the drive correctly because it uses the backup DBR, while MiniTool Partition Wizard doesn't use it." At first they thought there was something wrong with the sectors of C: But after close check with Winhex, all partitions, including C, are healthy (as said chkdsk /f was done on all accessible partitions).
Aside from that MiniTool problem, what is, I repeat, the solution. If you need more information than the now attached screenshots, please let me now. But I just can't begin to imagine I have to do a clean reinstall all over again. The last one (because Windows couldn't update from 1709 to 1803/9 dates from 15 May this year! Surely you don't mean to say that every major Windows update will require the same all over again.
And the "solution" offered by Repair Windows Boot Partition | Includes files and partitioning" is as radical...
And that while all checks indicate that my computer is in perfect working order...
PS - If you have a problem with some Dutch terminology, please signal me. For good measure I am adding an initial Windows popup, prior to the installation of 1903, which says quite ironically: "Congratulations, this PC is compatible! Downloading Windows 10 begins immediately... Processor: OK / Memory: OK / Available disk space: OK. Microsoft will never cease to amaze me... And every day I regret not having started my computer "career" - starting in 1979 - with Macintosh / Apple as soon as it was available... They have other drawbacks there, not mentioning the cost, but at least they don't make spaghetti software, which needs to be patched up as they go along...
Best
haku

You could delete the system reserved partition and recreate it. You have to boot into a recovery command line to do it, such as booting from a Windows 10 USB flash drive.

Thanks Navy LCDR!

Partition 1 is indeed an EFI active partition, and the partition to which the error message of the failed 1903 alludes That much is clear. And despite the properties saying it is full, it does contain the files enumerated in the article What is the System Reserved or EFI Partition in Windows and is not full at all. I checked this by temporarily giving that partition a letter, which allowed me to look into it.

No a few questions, ome of which may seem silly to you.

1. How do I make a USB flash drive? Where do I download its elements? Or will it suffice to copy over the files now contained in partition 1 if drive "0"?
2. How do I delete Partition 1? It seems to me that it is heavily protected. Don't forget that the whole drive is rather inapproachable, certainly where the manipulation of partitions is concerned.
3. By "recovery command", do you mean using the DISKPART DOS command? Where can I find simple instructions for doing that?
4. In which case, how big should the new partition be? Will 100 MB still suffice?

I have a feeling that your suggestion points to the right direction. But I need some handholding here coz this is quite an undertaking... Not so much technically, but for the risks involved.

Thanks anyway for following this.

haku

I'm afraid I'm not going to be able to post a good example of how to do it until Monday. Family visiting tonight and leaving for camping tomorrow without the computer. Here's how to make the USB flash drive, though. I prefer option 1 or 4:

Create Bootable USB Flash Drive to Install Windows 10

Thanks!
And very wise to go camping without the diabolical machine!
Best. Until Monday...
haku

If the computer does not have the single language please change the default language to English and post images in English:


https://www.tenforums.com/tutorials/...dows-10-a.html


Open disk management > by default some columns are compressed > widen each Status and Volume > make sure the contents within the parenthesis are in full view and that none of the characters are cutoff > view disk 0 > widen this row as needed so that all of the characters are in full view > post an image into the thread
Disk Management - How to Post a Screenshot of


Run setupdiag > post a share link into the thread using one drive, drop box, or google drive:
https://docs.microsoft.com/en-us/win...rade/setupdiag


If the only upgrade problem is failure to upgrade the system reserved partition, this may be able to be fixed by temporarily removing unneeded files that are consuming the needed space. Windows will automatically reinstall the files after a successful upgrade. Alternatively the partition may be able to be enlarged to fix the deficit.

The typical deficit is < 15 MB.
The deficit can be seen by viewing the Panther logs.

Post the most recent setuperr and setupact Panther logs using share links (one drive, drop box, or google drive,

Open administrative command prompt and copy and paste:

Code:

bcdedit /enum all
reagentc /info
diskpart
lis dis
lis vol
sel dis 0
det dis
lis par
sel par 1
det par
sel par 2
det par
sel par 3
det par
sel par 4
det par
sel par 5
det par
sel dis 1
det dis
lis par
sel par 1
det par
sel par 2

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread


Open administrative command prompt and type or copy and paste:
sfc /scannow
dism /online /cleanup-image /restorehealth
chkdsk /scan
wmic recoveros set autoreboot = false

When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

Hi Zbook,

This begins to look like a solution for a problem that has been pursuing me since more than a month. Microsoft - or its so-called support team - has given up, resorting to their ubiquitous "remedy": do a clean reinstall.
But your message contains a few mysteries for me. And answer to a galling annoyance that has bothered me for a long time: the display language problem.
Thank you so much for pointing this out to me. I will now be able to post threads with attachments in English - at least I hope so, because with Windows some hiccup often lurks around the corner.
As for expanding Disk Management, no problem: will do. But even by enlarging to a maximum a few things still remain hidden. However, everything is clear.
I'll run setupdiag as soon as possible. However, please explain to me how I can post this via Google drive. Must I share the file. If yes, to whom? I am not familiar with the procedure.
It seems indeed that the only problem is failure to upgrade the system reserved partition - at least up to the point where the update aborts of course en gives that error message. What is extremely frustrating is that the update starts with a popup message saying that my computer is absolutely compatible with the update.
If the problem can indeed be resolved so easily as you indicate, they will have another thing coming at Microsoft for sending me up the garden path for so long and with so little competence (including a suggestion to get rid of partition 1 completely, because they didn't know what it was for).
I can, as said before, make the contents of Partition 1 visible by giving it a letter. However, will that enable me to delete the files it contains. Indeed, I have encountered quite some obstacles when trying to manipulate that Drive "0", including the impossibility to resize the partitions (some articles I read say the MBR format renders such resizing impossible). So, until a solution is found for that problem, your other suggestion, to enlarge the partition can not be done.
What are Panther logs, and where can I find them? I didn't see them in Computer Management, so they must be somewhere else. Same goes for setuperr and setupact. What are these? Where are they to be found?
I understand you final suggestion (Open administrative command prompt and copy and paste), but don't know what it is for; nor do I understand what the "code" is meant to result in. I am a bit wary of running commands I don't know the meaning of, or not aware of what they will do.
Please enlighten me.

Thanks,

haku