The MSR (Microsoft Reserved) partition is hidden, so you won't see it on the GUI. But it will show up in DISKPART (command line tool from CMD or PowerShell). However, I seriously doubt that's your problem. I had MSR (the default 16M sized one from the original auto-partitioning of the clean drive during the first install of Win10) on all machines, yet my laptop has been showing all kinds of issues with this build (while the desktop machine does not). And I decided to remove MSR completely along with the redundant Recovery partition. (The laptop initially had a small Recovery in the begging and a new bigger one at the end of the disk, so I got rid of the older small one. The desktop had a bigger first partition for Recovery, so there was no additional last partition created during the upgrades.) And guess what, just as one would expect, an EFI system can boot just fine without that stupid MSR partition even when the entire C: drive is encrypted with BitLocker (no wonder, since the decryption key is stored in the TPM hardware and the boot manager is on the EFI System [Boot] partition [not on C: and definitely not on MSR which doesn't even have a recognizable file system]). I wonder if the next upgrade will try to re-create MSR (by shrinking the main C: system partition) but I didn't mind since that Windows install seems to be hopelessly broken anyways (even before I messed with the partitions, user logons always fail after any CU installs, it's stuck on .1). Edit.: I rearranged the partition layout on the desktop PC as well. This time I removed Recovery and MSR, moved EFI and System to the beginning of the space, created a blank Recovery at the end, expanded System to fill the remaining free space in the middle and then ran an in-place upgrade which did not re-create the missing MSR but populated the empty Recovery with the proper contents. Now the layout is almost as it's ought to be (EFI,MSR,System,Recovery) except with the omission of the useless MSR. (I didn't care to backup and restore the contents of Recovery because I was curious if the installer recreates the missing MSR or not. Nice to see it didn't.)
The 16MB MSR is rumored to be useless, but since there's no official documentation to prove it I leave MSR alone on all my deployments.
@petok, this is the thread about reserved storage: https://forums.mydigitallife.net/threads/reserved-storage-in-windows-10.79347/ These new 19041 online dism options aren't published before, afaik, maybe put it in there too?
edited - so far so good with 19041.x I haven't updated to build 19041.113 so I'll wait for the next CU coming next Tue. 3/10
Just File - Open powershell where your mounted ISO is and enter: ./setup /ResizeRecoveryPartition disable This will usually force setup to place the WinRE.wim in C:\Recovery\ if the existing partition is too small. I've seen PCs with 5 "recovery partitions" all over the drive with random size - it's ridiculous. Setup got better in all areas except this. I have no idea what Microsoft are smoking - how can they program it to fail instead of falling back automatically to the obvious solution? Other useful launch options for upgrades: /MigrateDrivers all /ShowOOBE none Will force setup to keep more drivers and hopefully prevent no input/network/display drivers or barking protected software (lame accounting stuff) or av's - leading to boot failures, respectively help prevent infamous black screen at login and/or wrong account (nt authority\system) leading to unresponsive ui and missing icons (ofc since it's not your user.. still not fixed from 1803 - probably because most people have actually no idea and just file moronic reports, and those actually documenting it don't get any traction and get buried. I'm also willing to bet the recent re-occurrence of file deletions have this same root cause since the system profile normally resides in system32, and on the very next boot it's gonna move / discard files). These 3 launch options seem to alleviate most of the grievance with upgrades, for years. My mediacreationtool.bat has them on for this reason. It has cut my support requests in more than half. Those that fail MCT setup I know for certain that have been "tweaked" and require manual intervention to keep the software zoo intact for the user.
Just did the update via WSUS on an old HP EliteBook 8470p with a fingerprint reader that I had previously configured.. I had to delete the fingerprints and set it up again, before it would let me use it to log on. On the Surface Pro (2018) I did last weekend, it did NOT forget my facial recognition.
Yup, I have resorted to all sorts of hacks found in google to restore my recovery. Windows randomly decides that recovery path has changes and refuses to boot into recovery. BTW even recovery partition is not needed. I just have 2 partitions on my hard drive. EFI Installation In this scenario, windows boots from winre.wim when you select recovery option. I manually create 200 MB EFI or system partition and Installation. This way, Windows has no option but to install itself in installation partition. So far it has worked flawlessly for me.
for some reason automatic maintenance is running everyday....... so it keeps defragging the drive everyday.. good thing its a mechanical drive. although gonna have to disable automatic defrag because that just nuts I analysed the disk with auslogic disk defrag yesterday and day before and today and it showed difference each of the days............ but at lest everything is loading fast but also it defrag keeps trying to do retrim on drives that dont support trim error in event viewer The storage optimizer couldn't complete retrim on (C because: The operation requested is not supported by the hardware backing the volume. (0x8900002A)