reagentc command - output not what I was expecting

Page 2 of 3 FirstFirst 123 LastLast
  1. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
    Thread Starter
       #11

    Thanks you. Looks the same other than a different drive.
      My Computers

  2. Kyhi's Avatar
    Posts : 3,552
    Windows 3.1 to Windows 10
       #12

    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...
      My Computer

  3. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
    Thread Starter
       #13

    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.
      My Computers

  4. Kyhi's Avatar
    Posts : 3,552
    Windows 3.1 to Windows 10
       #14

    you would have to reset the folder attribute to see contents..
      My Computer

  5. SoFine409's Avatar
    Posts : 1,287
    Win10 Pro
       #15

    Kyhi said:
    you would have to reset the folder attribute to see contents..
    I think you can use MiniTool to “Explore” any partition regardless of wether or not it has a drive letter.
      My Computers

  6. jumanji's Avatar
    Posts : 5,618
    Windows 10 Home 64bit Version 20H2
       #16

    Yes @Ztruker

    As
    SoFine409 said in the previous post you can explore the partition containing winre.wim with MiniTool Partition Wizard whether or not that partition has a drive letter.

    reagentc command - output not what I was expecting-17-02-2020-22-09-53.jpg

    Learnt the trick from dalchina .
      My Computer

  7. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
    Thread Starter
       #17

    Thanks @SoFine409 and @jumanji. Works a treat. Lot more stuff there than I realized:

    reagentc command - output not what I was expecting-image.png
      My Computers

  8. Kyhi's Avatar
    Posts : 3,552
    Windows 3.1 to Windows 10
       #18

    That Pic is the Macruim Recovery Partition -
      My Computer

  9. Ztruker's Avatar
    Posts : 13,512
    Windows 10 Pro X64 20H4 19042.746
    Thread Starter
       #19

    Just redid it. Removed boot entry, formatted partition, copied Macrium Reflect Premium v7.2.4732 ISO to the partitioopn then ran the batch file to gen the boot entry. Looks the same as before. Booted it and it works fine, as it did before.

    reagentc command - output not what I was expecting-image.png
      My Computers

  10. Kyhi's Avatar
    Posts : 3,552
    Windows 3.1 to Windows 10
       #20

    I was under the impression you where looking for the Windows Recovery ( WinRE.wim ) not the macrium Recovery
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
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 11:52.
Find Us




Windows 10 Forums