New
#11
Thanks you. Looks the same other than a different drive.
What reagentc does when it is disabled - it moves WinRE.wim back into the windows\system32\recovery folder
What reagentc does when it is enabled - it moves WinRE.wim out of the Windows Directory - thus the OS can be Refreshed/Restored without effecting WinRE....
If you have a designated Recovery Partition (Partition 4) - WinRE is moved there
If you do not have designated Recovery Partition - WinRE is moved to the Root of the drive ( C:\Recovery) thus either location is outside the OS directory.....
My claim to fame in all this - is that for the last 5 Years - all I do on a daily bases is develop, troubleshoot and integrate WinRE for use as Rescue Media on a Host OS... Which gives me a lot more insight into the Apps, processes, failures and error messages regarding that integration... With that said - Your other thread could of been solved a lot faster, with a lot this aggravation...
As I was the only one that stated the failure with using the Bootice method and the reason for the winload.efi error message... Which all comes down to Experience...
I didn't know that, thanks for that gem. I just checked and Winre.wim was in C:\Windows\System32 when reagentc was disabled (see post #3). Once I got it straightened out and enabled, it is no longer there, exactly as you said. I do have a Recovery partition, partition 1. Gave it a letter to look at it and removed the Hide protected OS files checkmark so I could see the Recovery partition had a Recovery folder but I couldn't access it.
Anyway, thanks again for the info.
I was under the impression you where looking for the Windows Recovery ( WinRE.wim ) not the macrium Recovery