PDA

View Full Version : Help to recreate Recovery partition working with F9



hexaae
05-24-2016, 12:36 PM
Hello,
as many did, a long time ago I switched from Windows 8 to Windows 10, but this deleted old Recovery partition working with F9 on reboot...
Now, pressing F9 breaks the BCD startup (easy to fix with Macrium Reflect boot disk "Fix Startup Problem" or other solutions (http://answers.microsoft.com/en-us/windows/forum/windows_8-update/i-get-your-pc-needs-to-be-repaired-and-error-code/e17ece75-0c69-4551-a3a1-a4e2ae2e8234?auth=1)...):

https://wpcf.neosmart.net/sites/5/2015/01/winload-efi-0xc0000225-windows-8.jpg

Your PC needs to be repaired
A required device isn't connected or can't be accessed.
Error code: 0xc0000225
[ A text saying I should use recovery tools on my installation media to fix the issue. ]
Press Enter to try again
Press F8 for Start-up Settings
Press Esc for UEFI Firmware Settings

...so, my goal is to recreate a custom Recovery partition with std Windows 10 clean install files when pressing F9.

To do this I need some infos from users with the original function still working on their G751JY:
- run Minitool Partition Wizard (free) and attach here a pic of your HD partitions structure
- run 2 commands from ADMIN prompt:
MountVol /info
REAgentC /info
and paste here your output

Thanks...

I suppose F9 expects to find a 5th partition on the boot drive named "Restore" and without a drive letter assigned (= hidden to Windows explorer) with the original \Recovery\install.wim file to boot from.

P.S.
I reapeat: I don't need to fix my PC to be able to boot again (I know how to do that, it's simple), I'm investigating a way to recreate a custom Recovery partition working with ASUS F9 feature.

JustinThyme
05-24-2016, 01:32 PM
Good luck! Wish I cold help you out but my recovery partition left long ago with windows 8.. I just created a recovery USB and have an image on my NAS as well.

cdma2k
05-24-2016, 02:21 PM
the question does not make sense.
for win 8, one can easily do it with asus backtracker
for win 10, it has the built-in "reset" or one can make a recovery usb as suggested by Justin

hexaae
05-24-2016, 09:57 PM
the question does not make sense.
for win 8, one can easily do it with asus backtracker
for win 10, it has the built-in "reset" or one can make a recovery usb as suggested by Justin
The point is that when you hit F9 on an ASUS with a removed factory Recovery partition you'll have a BSOD and a destroyed BCD every time (you have to repair boot process every time, easy to do anyway...).
My goal was to find a way to customize the "new" Recovery partition, making use of original ASUS F9 built-in feature. I think a tutorial on this topic could be useful.

cdma2k
05-25-2016, 01:35 AM
1. there is no window 10 version of backtracker
2. For window 7, I have created a partition with factory.wim, then "ReAgentc.exe /enable" to enable custom recovery environment, then F9 will bring up the page you mentioned; not sure if it will work for window 10

edit: looks like you might be able to do it in win 10, https://msdn.microsoft.com/windows/hardware/commercialize/manufacture/desktop/reagentc-command-line-options

hexaae
05-25-2016, 08:25 AM
Yes thank you for your help.
Learning how to use REAgentC, Diskpart, DISM etc. to recreate the so called "F9 partition" is exactly what I'm investigating these days...

REAgentC /ENABLE (from an admin cmd prompt), will automatically locate and re-enable your Recovery partition only (?), granted you still have it (everybody should).
Will do this looking for a marked recovery partition on your HD (they have a special GUID ID: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC) and select it for Recovery, e.g.:

C:\Users\Luca\Desktop>reagentc /info
Informazioni di configurazione per Ambiente ripristino Windows
e la reimpostazione del sistema:


Stato Ambiente ripristino Windows: Enabled
Percorso Ambiente ripristino Windows: \\?\GLOBALROOT\device\harddisk0\partition4\Recover y\WindowsRE
Identificatore dati di configurazione di avvio (BCD): fc0612d5-20ce-11e6-8adf-9bc77791b978
Percorso immagine di ripristino:
Indice immagine di ripristino: 0
Percorso immagine personalizzata:
Indice immagine personalizzata: 0


REAGENTC.EXE: operazione riuscita.
Legenda (example of pic in English (https://msdnshared.blob.core.windows.net/media/TNBlogsFS/prod.evol.blogs.technet.com/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/94/09/metablogapi/6661.image_174D7433.png) where a Recovery image was also set, the red square)

In my example above I used /info just to show my current state, but /ENABLE will set it automatically for you if you don't have one assigned anymore, this command is smart enough.
Notice Windows 10 upgrade creates a new 450MB partition for this (that's exactly the partition used when you do a SHIFT+REBOOT or troubleshooting reboot to repair PC) and probably wiped out the previously found one on the HD (usually it should simply add a new one at every major OS upgrade).

As you can see above from REAgentC output I don't have a RE image already set, and that's probably the problem when pressing F9...

I've just learned how to convert the "<mounted Windows 10 iso>:\sources\install.esd" available from Windows 10 ISO (downloaded with official MediaCreationTool (https://www.microsoft.com/en-US/software-download/windows10)) with DISM command, to create a generic W10 "install.wim":
dism /Export-Image /SourceImageFile:"YOUR_ESD_FILE" /SourceIndex:1 /DestinationImageFile:install.wim /compress:recovery /CheckIntegrity
This should work as boot recovery image since I don't have ASUS recovery.wim anymore...

Now... I'm not sure if it's sufficient to create another recovery partition (with correct GUID set) on my HD containing install.wim, and point REAgentC to it, to make F9 work again...


AUTO LEARNING FROM THE NET:

In the meanwhile I've found others discussed how to recreate a custom boot image (that we can use for F9) and recovery partition:
http://www.eightforums.com/installation-setup/39197-unable-use-built-asus-recovery-partition.html


Notice this is a known issue MS doesn't care to fix. It happened for Win 8 -> 8.1 before and again with Win 10 upgrade:
http://www.technologytell.com/gadgets/133905/windows-8-1-update-leaves-oem-owners-with-broken-restore-function/
Probably that's because MS official position is: just boot first time and always make a Recovery disk (http://windows.microsoft.com/en-US/windows-10/create-a-recovery-drive) to solve any future problem and/or restore/refresh your PC to current defaults. No need of manufacturer custom recovery partitions from MS point of view. The only problem is that this will f**** up ASUS F9 feature.

hexaae
05-25-2016, 02:22 PM
From what I can see here http://hothardware.com/reviews/asus-rog-g751jy-laptop-g-sync-gaming-on-the-go?page=3

http://hothardware.com/ContentImages/Article/2354/content/small_G751JY_partitions.jpg

I've found also this other pic from the net: http://i.imgur.com/YlqIBS3.jpg

Original G751JY (with ASUS F9 still working, the recovery partition is positioned as the 4th partition, 15GB).
Someone can confirm and paste its output from the command (from Admin prompt):
reagentc /info
please?

hexaae
05-25-2016, 07:02 PM
2. For window 7, I have created a partition with factory.wim, then "ReAgentc.exe /enable" to enable custom recovery environment, then F9 will bring up the page you mentioned; not sure if it will work for window 10
Please can you elaborate on this? What's your partitions structure? Where exactly did you put the "factory.wim" file (is this the exact name?)... And F9 does still work for you?
I miss exactly these kind of infos to recreate a new F9 recovery partition...

nice.lw
06-09-2016, 03:56 PM
https://drive.google.com/open?id=0B_DQ7egHfbtNRmE0dlhKcUxqWU0

nice.lw
06-09-2016, 03:57 PM
This is a recovery my G751JY ... :)