Windows 10: Small Wrinkle in Anniversary Update....MBR Disk Solved

Page 2 of 2 FirstFirst 12
  1.    03 Aug 2016 #11

    topgundcp said: View Post
    Great to hear. The procedure also automatically converted your MBR disk to GPT disk. For reference please post your new GPT disk layout. Use the traditional Disk management with graphical interface (Control Panel->Disk Management)
    Will do.... just waiting for the Anni. Update to Apply , 35% in so far.
      My ComputerSystem Spec

  2.    03 Aug 2016 #12

    Looks like the Anni. Update repartitioned my SSD .....Strange, looks like it ignored your Recovery Partition

    Now 450mb, 99mb, 231GB ,450mb ? in disk Management

    The 16mb Partition is Seen in MPW 9 though...... after the 99mb



    Click image for larger version. 

Name:	CaptureWin10c.PNG 
Views:	7 
Size:	293.8 KB 
ID:	93997

    Click image for larger version. 

Name:	CaptureWin10d.PNG 
Views:	4 
Size:	512.9 KB 
ID:	94001



    Had to shutdown the Server after the Update too , Windows didn't see it anymore , but found it again after the Restart.
      My ComputerSystem Spec

  3.    03 Aug 2016 #13

    topgundcp said: View Post
    @Kbird
    Actually I did make a video to convert from MBR to GPT disk but only for Option 1 which requires a fresh install then override the C: partition from backup image:
    Somewhere , perhaps on the Kyhi Thread you posted how to make a small 2-3gb Fat32 partition on a Harddrive and copy the Macrium Reflect Rescue Disk to it from the Mounted .iso. I went one step further and did it for the Kyhi .iso too , as there are 4 HDDs in my MediaSonic Probox. I actually also have one for Acronis Rescue (WD) and the TechBench Win10 Installer too now.

    KB
      My ComputerSystem Spec

  4.    03 Aug 2016 #14

    The 450mb at the end of the SSD is the new recovery Partition , I can tell by the Date Stamp , 2hrs ago, the one on the front of the SSD is dated in July 2015 when you made the MR Template is my guess.
      My ComputerSystem Spec


  5. Posts : 2,034
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       03 Aug 2016 #15

    That's normal. When you do an upgrade, Windows will create an extra 450MB to store the new WinRE.wim there. You are OK.
    Somewhere , perhaps on the Kyhi Thread you posted how to make a small 2-3gb Fat32 partition on a Harddrive and copy the Macrium Reflect Rescue Disk to it from the Mounted .iso. I went one step further and did it for the Kyhi .iso too , as there are 4 HDDs in my MediaSonic Probox. I actually also have one for Acronis Rescue (WD) and the TechBench Win10 Installer too now.
    Depend on the UEFI firmware that came with the MB. You could also put them on the same disk without setting the partition "Active" but you have to select UEFI boot mode from the boot menu.
    The screen shot below shows
    1- My Linux Mint OS
    2-My own built Recovery disk similar to KYHI's
    3-Macrium Rescue
    Click image for larger version. 

Name:	a.jpg 
Views:	2 
Size:	340.8 KB 
ID:	94008
      My ComputerSystem Spec

  6.    03 Aug 2016 #16

    Yep not sure why it doesn't overwrite the old one but I guess it want's it in case the Update goes sideways and it needs to recover to a pre-update state

    I'll most likely move it with reagentc later, once I know all is well and get my 450mb back.

    I didn't realise W10 Disk Management can't even see the 16mb partition , I guess they really don't want you in there

    I see it in Minitool Partition Wizard though.

    Thanks again.
    Last edited by Kbird; 05 Aug 2016 at 13:05.
      My ComputerSystem Spec

  7.    03 Aug 2016 #17

    GPT boot and UEFI etc is all new to me with this New Build , the MB is fully UEFI capable unlike my old Computer, so I was not even aware of the MSR Partition ......

    looks like the Update has overwritten Brink's .reg files I use too.... eg Numlock at Boot On.
      My ComputerSystem Spec

  8.    05 Aug 2016 #18

    Kbird said: View Post
    Yep not sure why it doesn't overwrite the old one but I guess it want's it in case the Update goes sideways and it needs to recover to a pre-update state

    I'll most likely move it with reagentc later, once I know all is well and get my 450mb back.

    I didn't realise W10 Disk Management can't even see the 16mb partition , I guess they really don't want you in there

    I see it in Minitool Partition Wizard though.

    Thanks again.

    As I mentioned above , I have moved the WinRE Environment Back to the Front of my SSD into the 450 mb partition that was already there before the Win10-1607 Update. this Is how I did it incase someone else needs to do it too.


    Moving WinRE to The New Separate Partition


    1.) Give the Recovery Partition a Drive Letter in Disk Management ...

    I use B: (A: & B: were once reserved for Floppy Drives)

    if you don't use B:\ you will need to change the following comamnds to YOUR choice of Drive Letter

    ***Update...this may not be possible in Disk Management if the Partition is already seen as a True Recovery Partition ie Type 0x27 on MBR disks.

    2.) Copy the Recovery folder from whever Windows installed it to B:\ Drive (assuming B: was used in No#1)

    DO NOT disable WinRE 1st ( see no#4) or you will have nothing to copy !


    3.) Open a Command Prompt with Admin Rights ( RC the Start Button>Command Prompt (Admin) )


    4.) Disable Win RE if active with the command reagentc /disable ( Completed sucessfully should be the answer)


    5.) Inform Win10 where the new Recovery Partition you copied to B:\ is with this command :


    reagentc /setreimage /path B:\Recovery\WindowsRE ( Completed sucessfully should be the answer)


    6.) now re-enable the Recovery Drive with this command:

    reagentc /enable ( Completed sucessfully should be the answer)


    7.) Check Recovery Environment is ok with this command


    reagentc /info


    and you should see something similar too below in response:


    Windows RE status: Enabled
    Windows RE location: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
    Boot Configuration Data (BCD) identifier: efd8c481-36c0-11e6-962e-1c6f6537fa59
    Recovery image location:
    Recovery image index: 0
    Custom image location:
    Custom image index: 0
    REAGENTC.EXE: Operation Successful.



    8.) Remove the drive letter B: in Disk Management again ( if desired )


    9.) Remove the old Win RE Folder from whereever windows installed it ie C:\Recovery or C:\Windows\System32\Recovery ?


    10.) Or as in my Case, it was in the 450 mb new partition Win10 created at the end of the Disk 0 (my SSD) , (even though there was one already at the front of the Disk) so I just used Minitool Partition Wizard to delete the whole New Partition instead and then resized C:\ Drive back to maximum size into the unallocated space.


    Additional Info:
    The recovery partition is a hidden partition of 450MB.
    ( turn on show hidden files and system files in File Explorer>Options )

    On BIOS systems with an MBR formatted drive, the recovery partition has the type 0x27.

    On UEFI systems with an GPT formatted drive the recovery partition has the
    GUID {DE94BBA4-06D1-4D40-A16A-BFD50179D6AC}.

    Good Luck ,

    KB.
    Last edited by Kbird; 23 Aug 2016 at 15:51.
      My ComputerSystem Spec


  9. Posts : 2,034
    Ubuntu14.04x64 MintMate17x64 Win10Prox64
       05 Aug 2016 #19

    Very good @Kbird. However, you could have done it with ease using Macrium while Windows is running.

    1. From Restore tab. Select your Backup image as Source, select your current C drive as Destination (should already be selected).
    2. On Destination, click on the first Recovery Partition (Partition 1) then click delete existing partition, do the same for last Recovery partition. Drag the last partition (New Recovery) from Source and drop onto the first empty space of Destination, click Next->Finish
    3. Extend C. Use ReAgentc to point to the first partition.
      Note: No need to assign any letter. Use:
      reagentc /setreimage /path \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\WindowsRE
      instead of
      reagentc /setreimage /path B:\Recovery\WindowsRE
    Last edited by topgundcp; 05 Aug 2016 at 19:11.
      My ComputerSystem Spec

  10.    05 Aug 2016 #20

    Sweet ! Thanks I will add that trick to my notes for next time
      My ComputerSystem Spec


 
Page 2 of 2 FirstFirst 12

Related Threads
I have a Lenovo Stick 300 (Intel Compute stick clone) and I formatted the drive. I made a recovery USB and when I boot it and try to install, it says something like "drive too small." It has a 32/28GB SSD and I could install Windows x86 on it. I...
Solved Disk too small? in Installation and Upgrade
So I have a Sony VAIO laptop. It came with Windows 7 and I was able to successfully upgrade to Windows 10. I wanted to then upgrade the HD from a 5400 drive to an SSD. Old one was 580 or so GB, new one is 480 GB. First step I tried was to clone...
So after the big update, I have a few questions. 1. Some of my tiles in the start menu have changed colour from blue to black don't look right next to the blue tiles. How do I change it back to what it was before? 2. Safe to remove both...
Since I received the latest update over last weekend, a new small (un-named) partition has appeared at the end of my 'C' Drive - see attached screenshot. Previously there was only a single partition containing all files. Can anyone explain what...
:really:Hey Guys, SOrry that i had seen these post before too on this forum several times,But please kindly have a look to My Snapshot. I realize this Issue when i was in windows 8.1 Enterprise so after that after a while i installed win10 . ...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 01:54.
Find Us