Timeline for How to move the recovery partition on Windows 10?
Current License: CC BY-SA 4.0
35 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15 at 0:18 | comment | added | GuyPaddock | What's the best way to allocate the new recovery drive at the end of the disk? I guess I could just create a new dummy partition that takes up the slack, create the new recovery partition, and then delete the dummy partition. | |
| Aug 11, 2023 at 9:28 | comment | added | Teng-pao Yu | As there is only one single partition on my device, I actually did the following instead: Step 1~2 unchanged 3. Disable recovery ``` reagentc /disable reagentc /setreimage /path N:\Recovery\WindowsRE ``` 4. Delete the original recovery (and optionally extned the original C:) 5. Create a new parition for recovery 6. Apply the recovery ``` Dism /Apply-Image /ImageFile:C:\recovery-partition.wim /Index:1 /ApplyDir:N:\ ``` 7. Reenable the recovery ``` reagentc /enable ``` 8~11 Follow the original 5~8 | |
| Jul 21, 2023 at 22:39 | comment | added | Tony Salls | Also, I too noticed the N: drive in file explorer - you need to remove the drive letter from the partition as well as the volume. in diskpart: Select volume N /n Remove -> that should remove it from file explorer. | |
| Jul 21, 2023 at 22:33 | comment | added | Tony Salls | For whatever reason I couldn't disable bitlocker on the new recovery partition in the gui. This is how you can do that from the command line: manage-bde -off N: | |
| Jun 16, 2023 at 19:03 | comment | added | Gili | I just discovered that if one adds or removes a physical drive from the computer in a way that causes the boot disk number to change, then the system will crash loading the boot loader (error 0xc00000f). Running step 5 ("hide the recovery partition") fixes this problem, every time. You just need to boot off an installation media (e.g. USB), drop to the command line, run step 5 and when you reboot the system works again. Thank you a million! You saved my day. | |
| Mar 9, 2023 at 2:04 | comment | added | sinback | Followup to my guidance for people trying to expand storage in MBR situations. answers.microsoft.com/en-us/windows/forum/all/… also helped me understand the goal - but I didn't use any third-party tools like Greg Carmack suggested in the answer for that post, I just used diskpart and friends. | |
| Mar 9, 2023 at 2:00 | comment | added | sinback | Great answer! I used it to resize a disk image for a VM while keeping the recovery partition at the end. I'll call the old recovery partition O and new one N still. I use an MBR, not UEFI, setup, which it turns out imposes limitations on the number of Primary partitions which can be created by default. Since C is Primary, it's best if N is NOT a part of a Logical partition when you do this, which may involve disconnecting external storage disks(/images for VMs) if you have 4 Primary partitions across all disks. See superuser.com/q/856945/1255891 | |
| Nov 12, 2022 at 12:10 | comment | added | Julian | @user2297550 If you get that message just turn off bitlocker on the "new recovery partition" | |
| Oct 17, 2022 at 16:31 | comment | added | VainMan | @GeertSmelt Sorry for late reply. You forgot to reboot(step #6) after removing the volume letter. That would keep it enabled. | |
| Sep 19, 2022 at 14:39 | comment | added | Geert Smelt | If you remove the assigned drive letter (N: in the above example) after you're done (e.g. because the partition didn't have one prior to the move) then it will show up as disabled when you check the status. Re-adding the drive letter solves that issue. | |
| Apr 15, 2022 at 12:25 | comment | added | JW0914 |
@JakeF It's not a "gotcha", it's simply the incorrect sequence of commands was executed, as in order for WinRE's path to be changed, it must be disabled (it's analogous to trying to capture a WIM of C: while booted to Windows)
|
|
| Apr 15, 2022 at 12:20 | comment | added | JW0914 | @VainMan Please don't add disclaimers, as they're not needed and only serve to generate anxiety in inexperienced users - instead, please ensure the answer's directions/steps are correct and link to Microsoft Docs man pages as needed. | |
| Jan 15, 2022 at 10:33 | comment | added | croraf | Not working. Before step 3 I created a simple NTFS partition with 1.5GB with label "N". I then did step 3 which reports success (but I see no change in partition "N"). Then "reagentc /setreimage /path N:\Recovery\WindowsRE" fails with "REAGENTC.EXE: The specified path was not found." | |
| Jan 3, 2022 at 3:44 | comment | added | Clay Lenhart | Thanks so much! For me running 'reagentc /info' at the end showed my recovery partition disabled. When I rebooted, it was enabled. | |
| Dec 21, 2021 at 9:57 | comment | added | jef | BTW you can also use cygwin's dd to copy and restore the rescue partition once it moved. | |
| Nov 7, 2021 at 14:48 | comment | added | user2297550 | It doesn't seem to work. I get the error: "Windows RE cannot be enabled on a volume with BitLocker Drive Encryption enabled." | |
| Jul 25, 2021 at 21:12 | comment | added | SSilk |
Great instructions! One comment: after following the above instructions, my new recovery partition kept reappearing in Windows Explorer/ This PC as drive 'N' despite the diskpart > remove step. I discovered there was a registry key \DosDevices\N: under Computer\HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices that was making this come back. Deleting that key fixed this issue. YMMV; registry editing precautions apply. This is detailed here: answers.microsoft.com/en-us/windows/forum/all/…
|
|
| Feb 16, 2021 at 3:47 | comment | added | VainMan | @Steve When I did this using empty name was OK. Edited it to use non-empty name, MS has no document about this yet though. | |
| Feb 16, 2021 at 3:38 | history | edited | VainMan | CC BY-SA 4.0 |
use non-empty name for captured image
|
| Feb 14, 2021 at 0:16 | comment | added | Steve | I wanted to say great comment, people generally don't care about following through like this, and it bugs me But +1 and thanks are discouraged lol So I thought I might add a suggestion In step 2 there is no name for the image, Windows 10 1904 will complain if there is no name Just great to see thoughtful people putting the effort in, document the world! | |
| Jan 16, 2021 at 17:57 | comment | added | VainMan | @JakeF Thanks for nice finding this. Added a disable-step before step 4. | |
| Jan 16, 2021 at 17:55 | history | edited | VainMan | CC BY-SA 4.0 |
disable re before change image location
|
| Jan 16, 2021 at 15:01 | comment | added | Jake F |
There is a subtle gotcha, at least in Windows 10 2004, which is the one I just did this on: When reagentc /setreimage /path N:\Recovery\WindowsRE is executed, it actually doesn't change the Windows RE location. Once the original partition (O:) is deleted, reagentc reports Disabled. The workaround is to run reagentc /disable before step 4, or to do step 7 before step 4.
|
|
| Jan 12, 2021 at 17:50 | comment | added | haridsv | I think I tried that and it gave an error, but I can't recollect it now. I will try again and get back to you with the correct message. | |
| Jan 12, 2021 at 17:40 | comment | added | VainMan |
@haridsv Sorry to see now. You can run reagentc /enable to enable it again.
|
|
| Dec 31, 2020 at 11:38 | comment | added | haridsv |
While creating the image, dism forced me to give a name with /name option, but other than that I was able to get through step 4. I confirmed that reagentc /info showed the status as Enabled, but once I changed the id to 27, status became Disabled and reagentc /boottore complained about the same. What could I be doing wrong?
|
|
| Nov 24, 2020 at 20:18 | history | edited | VainMan | CC BY-SA 4.0 |
fix tiny gramma mistake
|
| S Nov 24, 2020 at 20:15 | history | suggested | CommunityBot | CC BY-SA 4.0 |
The command to enable RE is missing
|
| Nov 23, 2020 at 19:39 | review | Suggested edits | |||
| S Nov 24, 2020 at 20:15 | |||||
| Oct 22, 2020 at 2:02 | history | edited | VainMan | CC BY-SA 4.0 |
added 39 characters in body
|
| Oct 21, 2020 at 19:25 | review | Late answers | |||
| Oct 21, 2020 at 20:53 | |||||
| Oct 21, 2020 at 19:21 | history | edited | VainMan | CC BY-SA 4.0 |
added 83 characters in body
|
| Oct 21, 2020 at 19:10 | history | edited | VainMan | CC BY-SA 4.0 |
added 154 characters in body
|
| Oct 21, 2020 at 19:06 | review | First posts | |||
| Nov 4, 2020 at 19:06 | |||||
| Oct 21, 2020 at 19:04 | history | answered | VainMan | CC BY-SA 4.0 |