Results 1 to 7 of 7
  1. #1
    ROG Enthusiast Array
    Join Date
    Dec 2015
    Reputation
    10
    Posts
    51

    Cant boot from new ssd after having cloned from original ssd and then wiped original

    G752VT UEFI - GPT , SSD disk 950 Pro samsung.

    Can't boot Windows 10 (primary OS ) after it was cloned from original one, and then the original was ssd was wiped / deleted ( using disk part )
    The disk was cloned via EaseUS, and the whole disk was cloned including the Recovery Partition and the OS.
    I get the Win10 blue boot error : "The boot configuration data file is missing some required information ". Screehshot http://oi67.tinypic.com/16ia5js.jpg

    bcdboot C:\Windows
    ================
    This command succeeds ( ran via a secondary working OS that is available on another disk on the same system ) but does not solve the problem. Strangely via this secondary drive I can boot the Primary one but the Primary one cannot boot on its own,

    Further more I cannot a create a Recovery Drive via the equivalent option in windows 10 ... it tells me "required files are missing".

    A bootable USB boots and detects the primary OS but cannot repair it.. it says, " We cant repair it" or similar message. Going into a command prompt after booting the USB, will not see the disk ( because its an SSD , no drivers ) So I cannot try command prompt tools that people are suggesting.

  2. #2
    Banned Array JustinThyme PC Specs
    JustinThyme PC Specs
    Laptop (Model)G752VY-DH72
    MotherboardRampage VI Extreme
    ProcessorI9 9940X
    Memory (part number)64GB DDR4 8x8 Corsair Dominator Platinum 3800 MHz @ C17
    Graphics Card #1ASUS Strix 2080Ti O11G @ 2.1GHz
    Graphics Card #2ASUS Strix 2080Ti O11G @ 2.1Ghz
    Graphics Card #3ROG Nvlink
    Graphics Card #4Have to feed animals
    Sound CardExternal Audioengine D1 24 bit 192kbps DAC
    MonitorASUS PG348Q @ 100Hz
    Storage #1Intel 905P 480GB U2 flavor
    Storage #2Samsung 850 EVO 1TB X2 in RAID 0, 960 PRO 1TB DIMM.2_1
    CPU CoolerHeatKiller IV PRO and VRM blocks ,Dual D5 PWM serial, 2X 480, 1X 360 RADS
    CasePhanteks Enthoo Elite 8X LL120 PWM, 3X LL140 PWM, 12 SP120 PWM 1x AF140 PWM
    Power SupplyCorsair AX 1500i
    Keyboard ASUS Claymore
    Mouse ASUS Spatha, Logitech MX Master
    Headset Sennheiser HD 700
    Mouse Pad ASUS ROG Sheath
    Headset/Speakers Audioengine A5+ with SVS SB-1000 Sub
    OS Win10 Pro 1809
    Network RouterNetGear NightHawk X10
    Accessory #1 NetGear Prosafe 10GBe Switch
    Accessory #2 Qnap TVS-682 NAS modded with I7 CPU

    Join Date
    Nov 2013
    Reputation
    144
    Posts
    3,858

    What BIOS are you running and how do you have it set up?

    Creating recovery media after the fact it a moot point. Im afraid you have bopped the beagle on that one. I've seen this same thing happened repeatedly over the years and this is specifically why I remove the original drive and put it away for safe keeping.

    Im thinking your only chance now is a clean install, follow the UEFI guide in the sticky and whether or not you will need to load drivers is dependent on what BIOS you are running and how its configured.

    You might want to see if this members post applies to your situation.
    https://rog.asus.com/forum/showthrea...l=1#post572265

  3. #3
    ROG Enthusiast Array
    Join Date
    Aug 2015
    Reputation
    10
    Posts
    74

    no need to follow UEFI guide.
    The current build of Windows 10 iso can detect the key automatically based on my experience, quick and simple, just create a bootable window 10 USB from MS site (https://www.microsoft.com/en-us/soft...load/windows10), clean installation of Windows 10, then install the drivers if needed
    Last edited by cdma2k; 02-08-2016 at 01:38 AM.

  4. #4
    ROG Enthusiast Array
    Join Date
    Dec 2015
    Reputation
    10
    Posts
    51

    I managed to solve it.


    Here are my disks.

    Click image for larger version. 

Name:	Image 111.png 
Views:	4 
Size:	56.4 KB 
ID:	55454

    The C: drive wasn't booting on its own even after I tried bcdboot c:\windows

    Instead I had to do bcdboot c:\windows /s m: /f All

    where m drive was assigned to the 260 MB EFI partition.

    In other words the UEFI setup was expecting the boot manager to go to the EFI partition and will not accept it being in C: drive...

    Maybe the EFI standard requires this, in disks where there is a dedicated EFI partition? Possibly,

    Thanks for helping guys, all done now.

  5. #5
    ROG Enthusiast Array
    Join Date
    Aug 2015
    Reputation
    10
    Posts
    74

    good!
    looks like your recovery partition is gone, did you make usb backup with Asus backtracker?

  6. #6
    ROG Guru: Blue Belt Array Gps3dx PC Specs
    Gps3dx PC Specs
    Laptop (Model)Current: G751JT | Retired: G55VW, G51JX
    MotherboardInc M.2 slot
    Storage #1Samsungs EVO 850 128GB
    Storage #21TB HGST Travelstar 7K1000 (HTS721010A9E630)
    CPU CoolerMother Nature & Thermodynamics laws
    Mouse Logitech MX 518
    Headset/Speakers Logitech T6060
    OS Cleaned installed Windows 10 HOME x64
    Accessory #1 Leap Motion

    Join Date
    Feb 2015
    Reputation
    71
    Posts
    770

    Quote Originally Posted by fixxi.net View Post
    In other words the UEFI setup was expecting the boot manager to go to the EFI partition and will not accept it being in C: drive...
    Maybe the EFI standard requires this, in disks where there is a dedicated EFI partition? Possibly
    Hi there...
    for that reason alone I've dedicated almost full-half-day to write the sticky thread "Guide: How to install windows 8/8.1/10 The proper way (UEFI based installation)" - it holds some key ideas about windows based on UEFI machine - that are true also for the latest ROG models.
    P.S - One of the most important laws of "creative thinking" is that "the solution is near you" - I can suggest to embrace it - after all, reading doesn't hurt,it might just help

  7. #7
    Banned Array JustinThyme PC Specs
    JustinThyme PC Specs
    Laptop (Model)G752VY-DH72
    MotherboardRampage VI Extreme
    ProcessorI9 9940X
    Memory (part number)64GB DDR4 8x8 Corsair Dominator Platinum 3800 MHz @ C17
    Graphics Card #1ASUS Strix 2080Ti O11G @ 2.1GHz
    Graphics Card #2ASUS Strix 2080Ti O11G @ 2.1Ghz
    Graphics Card #3ROG Nvlink
    Graphics Card #4Have to feed animals
    Sound CardExternal Audioengine D1 24 bit 192kbps DAC
    MonitorASUS PG348Q @ 100Hz
    Storage #1Intel 905P 480GB U2 flavor
    Storage #2Samsung 850 EVO 1TB X2 in RAID 0, 960 PRO 1TB DIMM.2_1
    CPU CoolerHeatKiller IV PRO and VRM blocks ,Dual D5 PWM serial, 2X 480, 1X 360 RADS
    CasePhanteks Enthoo Elite 8X LL120 PWM, 3X LL140 PWM, 12 SP120 PWM 1x AF140 PWM
    Power SupplyCorsair AX 1500i
    Keyboard ASUS Claymore
    Mouse ASUS Spatha, Logitech MX Master
    Headset Sennheiser HD 700
    Mouse Pad ASUS ROG Sheath
    Headset/Speakers Audioengine A5+ with SVS SB-1000 Sub
    OS Win10 Pro 1809
    Network RouterNetGear NightHawk X10
    Accessory #1 NetGear Prosafe 10GBe Switch
    Accessory #2 Qnap TVS-682 NAS modded with I7 CPU

    Join Date
    Nov 2013
    Reputation
    144
    Posts
    3,858

    I Know this sounds stupid but did you swap the position of the M2 Drives are you finished cloning?

    Quote Originally Posted by cdma2k View Post
    no need to follow UEFI guide.
    The current build of Windows 10 iso can detect the key automatically based on my experience
    There is a lot more to UEFI than the product key. Takes you from 16 bit BIOS to 64bit firmware and the UEFI parition is used to execute the boot sequence by commanding the .efi files in the UEFI partition.

    Gps3dx's guide is pretty comprehensive and thorough once you get past the blinding color coding.
    Last edited by JustinThyme; 02-08-2016 at 05:15 PM.

Posting Permissions

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