Results 1 to 5 of 5

Thread: 'Howto' Recover a bootable device that is MBR when you are now UEFI: MBR>GPT Win 10

  1. #1
    don't stock motherhoods
    Join Date
    Jun 2005
    Posts
    1,209
    Thanks
    749
    Thanked
    109 times in 94 posts
    • Millennium's system
      • Motherboard:
      • Asus Z170 Pro Gamer ATX
      • CPU:
      • Intel i5 6600K @ 4.5GHz 4 core
      • Memory:
      • Corsair VPX 3000 DDR4 (16, 4*4)
      • Storage:
      • 500gb 850 Evo sata3 SSD, 2*2TB Green 5900 Raid 0
      • Graphics card(s):
      • MSI 390 8gb
      • PSU:
      • toughpower 1kw
      • Case:
      • Zalman Z3 Plus
      • Operating System:
      • Windows 10 64bit
      • Monitor(s):
      • VIEWSONIC VG2401MH 144hz (Solid)
      • Internet:
      • Origin ADSL Broadband, not really recommended.

    Exclamation 'Howto' Recover a bootable device that is MBR when you are now UEFI: MBR>GPT Win 10

    My computer has been a little unstable recently (looks like the GPU will need an RMA) and this afternoon I turned on the monitor to a lovely blue screen stating that the BCD entries were corrupt and I should try Win10 installation media. Crikey!

    Didn't really expect it as only had one unexpected restart before, but hey ho, off I went in search of a blank USB key. This proved fruitless as although I bought 2 32GB sticks in December, they've both gone walkies. Long story short, I did find another 32GB Stick, and cleared it with my laptop and used the Windows 10 Installation Media creator (I believe I googled ISO tool) to eventually create windows installation media of it.

    So did the repair work? Well no. Startup repair failed consistently from the official installation media and I couldn't even re-install windows as you can't upgrade from outside the booted OS you want to upgrade, and I couldn't install alongside my current install on my SSD as apparently I was using EFI boot mode (news to me) and my Win10 SSD install was an MBR disk. *sigh*

    Now it appears the reason for this is my recently-updated Ryzen BIOS only supports 2 boot "modes" now: UEFI and UEFI+Legacy. I believe when I originally installed Win10 on this PC I used Legacy and to be honest it may even have been a previous motherboard. It looked like I was not going to be able to set the BIOS now to Legacy to try and boot or install to the MBR device.

    Resigned that all easy options were closed to me (and with a 2 day old backup) I went to repartition and reformat a 2TB Sata HDD I had recently made available, and install Win10 on that. This took quite a long time, it was stuck at preparing files at around 80% for ages, something I don't remember from previous windows installs.

    Eventually I was back in a bootable, if slow, windows 10 environment and considered my options. Recover from 2 day old backup: valid, but not going away any time soon so on the backburner. Try and recover the bootable bit of the SSD: tricky but the best option I could see.

    I thought I would have a go at converting the SSD to GPT and then re-installing the BCD and maybe the bootloader. I used the open source gptgen.exe (v1.1) to convert the drive, and used EasyBCD (which wasn't very happy with either my installations or GPT) to recover the bootloader and BCD info to the SSD. Then I tried to boot from it.

    Some progress - not an immediate blue screen but one slightly later on in the boot process which suggested my storage drivers were not ACPI compliant (they are!) and suggested a reinstall. Err - no thanks.

    My options here as I saw it were to install windows alongside the windows install on my SSD and then reinstall all my programs, or use the backup. I didn't like either of these, and I had some time to kill and didn't want to rush, so I looked online to see if I had done the boot from GPT thing properly. A lucky link to a forum thread about 3 pages into my google results led me to this fantastic article:

    Microsoft TECHNET Converting Windows BIOS installation to UEFI https://social.technet.microsoft.com/wiki/contents/articles/14286.converting-windows-bios-installation-to-uefi.aspx

    I am honestly so happy that someone at MS went into the level of detail they did here, even recommending and suggesting the use of gptgen and other 3rd party software. The solution had worked for at least 2 people so I figured why not give it a shot?

    Some slightly hair raising command prompt from rescue disk commands later my original Win10 was booting again! Hooray! I've had no other problems but I am still slightly unstable so will have to look into that RMA I guess.

    So if you want to convert from MBR to GPT my suggestion is : don't do it just for boot times, don't do it unless you have no choice, which may come with future OSes. If you need to do it, print out the link above or read it on another device and follow the instructions carefully and fully. You should be ok then.

    Thanks for reading Hexus.
    Last edited by Millennium; 20-02-2018 at 08:21 AM.
    hexus trust : n(baby):n(lover):n(sky)|>P(Name)>>nopes

    how do you spend your time online? (Hexus link)

  2. Received thanks from:

    Biscuit (22-02-2018),peterb (20-02-2018)

  3. #2
    The late but legendary peterb - Onward and Upward peterb's Avatar
    Join Date
    Aug 2005
    Location
    Looking down & checking on swearing
    Posts
    19,380
    Thanks
    2,892
    Thanked
    3,403 times in 2,693 posts

    Re: Howto (?) Recover a bootable device that is MBR when you are now UEFI: MBR>GPT Wi

    ‘Stickied’ for future reference.
    (\__/)
    (='.'=)
    (")_(")

    Been helped or just 'Like' a post? Use the Thanks button!
    My broadband speed - 750 Meganibbles/minute

  4. Received thanks from:

    Millennium (20-02-2018)

  5. #3
    Senior Member AGTDenton's Avatar
    Join Date
    Jun 2009
    Location
    Bracknell
    Posts
    1,711
    Thanks
    412
    Thanked
    282 times in 212 posts
    • AGTDenton's system
      • Motherboard:
      • ASUS P6T7 WS Supercomputer
      • CPU:
      • Intel Core i7 980
      • Memory:
      • 24GB Corsair Dominator GT
      • Storage:
      • Samsung 860 Pro + HDDs
      • Graphics card(s):
      • Asus 1030
      • PSU:
      • Seasonic X-850W
      • Case:
      • Fractal Design R3
      • Operating System:
      • 10 Pro x64
      • Internet:
      • 70MB using BT line

    Re: 'Howto' Recover a bootable device that is MBR when you are now UEFI: MBR>GPT Win

    Very useful, sadly not as simple as changing from IDE/AHCI/RAID which I've done a lot of recently.
    I will hang on to this as will no doubt come across this problem at some stage. I personally would just take the hit of only doing it when I do a re-install.


    Rigs:
    Main: ASUS P6T7 WS Supercomputer, i7 980, 24GB Corsair Dominator GT, Samsung 860 Pro + HDDs, Asus 1030, Seasonic X-850W, Fractal Design Define R3, 10 x64 Pro, Noctua DH14 + Noctua chassis fans

  6. #4
    Anthropomorphic Personification shaithis's Avatar
    Join Date
    Apr 2004
    Location
    The Last Aerie
    Posts
    10,857
    Thanks
    645
    Thanked
    872 times in 736 posts
    • shaithis's system
      • Motherboard:
      • Asus P8Z77 WS
      • CPU:
      • i7 3770k @ 4.5GHz
      • Memory:
      • 32GB HyperX 1866
      • Storage:
      • Lots!
      • Graphics card(s):
      • Sapphire Fury X
      • PSU:
      • Corsair HX850
      • Case:
      • Corsair 600T (White)
      • Operating System:
      • Windows 10 x64
      • Monitor(s):
      • 2 x Dell 3007
      • Internet:
      • Zen 80Mb Fibre

    Re: 'Howto' Recover a bootable device that is MBR when you are now UEFI: MBR>GPT Win

    It's a bit scary when it BSODs, especially as you have passed the point of no return (bar a full restore) at that point. Although after doing this on numerous machines (both physical and virtual) I have yet to have the procedure go wrong or lose data.

    While the recovery partition does not work, I did find that after deleting it and making a bit of extra space, once a new Windows 10 build is installed/upgraded the recovery partition can get recreated by the upgrade.
    Main PC: Asus Rampage IV Extreme / 3960X@4.5GHz / Antec H1200 Pro / 32GB DDR3-1866 Quad Channel / Sapphire Fury X / Areca 1680 / 850W EVGA SuperNOVA Gold 2 / Corsair 600T / 2x Dell 3007 / 4 x 250GB SSD + 2 x 80GB SSD / 4 x 1TB HDD (RAID 10) / Windows 10 Pro, Yosemite & Ubuntu
    HTPC: AsRock Z77 Pro 4 / 3770K@4.2GHz / 24GB / GTX 1080 / SST-LC20 / Antec TP-550 / Hisense 65k5510 4K TV / HTC Vive / 2 x 240GB SSD + 12TB HDD Space / Race Seat / Logitech G29 / Win 10 Pro
    HTPC2: Asus AM1I-A / 5150 / 4GB / Corsair Force 3 240GB / Silverstone SST-ML05B + ST30SF / Samsung UE60H6200 TV / Windows 10 Pro
    Spare/Loaner: Gigabyte EX58-UD5 / i950 / 12GB / HD7870 / Corsair 300R / Silverpower 700W modular
    NAS 1: HP N40L / 12GB ECC RAM / 2 x 3TB Arrays || NAS 2: Dell PowerEdge T110 II / 24GB ECC RAM / 2 x 3TB Hybrid arrays || Network:Buffalo WZR-1166DHP w/DD-WRT + HP ProCurve 1800-24G
    Laptop: Dell Precision 5510 Printer: HP CP1515n || Phone: Huawei P30 || Other: Samsung Galaxy Tab 4 Pro 10.1 CM14 / Playstation 4 + G29 + 2TB Hybrid drive

  7. #5
    Senior Member Ciber's Avatar
    Join Date
    Feb 2007
    Location
    Southampton
    Posts
    1,602
    Thanks
    167
    Thanked
    77 times in 61 posts
    • Ciber's system
      • Motherboard:
      • Asus Prime X470 Pro
      • CPU:
      • Ryzen 5 3600
      • Memory:
      • 16GB Ballistix
      • Storage:
      • ADATA XPG SX8200 Pro 512GB + 1TB
      • Graphics card(s):
      • GTX960
      • PSU:
      • Seasonic Prime Ultra Snow Silent 650W
      • Case:
      • Phanteks Enthoo Pro
      • Operating System:
      • W10 64
      • Monitor(s):
      • Samsung 275T 27" LCD
      • Internet:
      • Virgin Fibre

    Re: 'Howto' Recover a bootable device that is MBR when you are now UEFI: MBR>GPT Win

    There is a Microsoft tool to do the MBR to GPT conversion. Has anyone used it? https://docs.microsoft.com/en-us/win...ent/mbr-to-gpt

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •