Jump to content











Photo
- - - - -

REagentC.exe and GUIDs


  • Please log in to reply
1 reply to this topic

#1 spleenharvester

spleenharvester

    Member

  • Members
  • 91 posts
  •  
    United Kingdom

Posted 06 May 2016 - 04:25 PM

Really odd problem here.

 

Basically, I'm working on a BCD repair script that is run from a WinPE-based image. If I forcibly invalidate and rebuild the BCD, I get an entry with guid XYZ in bcdedit. If I then attempt "reagentc /enable /osguid XYZ" after setting the image, I get an error that the BCD has not yet been configured, and to run bcdboot (which is odd, since I just did that).

 

However, if I then run bcdedit.exe /enum /v again, the OS identifier's GUID has completely changed, to guid ABC. If I then use this new GUID in "reagentc /enable /osguid ABC", it then enables WinRE without a problem.

 

I haven't had a chance to figure out if the GUID is changing in the BCD itself or if it's an odd issue getting bcdedit.exe to refresh, but does anyone happen to know what might be causing this?



#2 spleenharvester

spleenharvester

    Member

  • Members
  • 91 posts
  •  
    United Kingdom

Posted 06 May 2016 - 05:54 PM

Hah nevermind, it was a bug in the script. I had the paths to the legacy and EFI BCDs swapped around and the OS had a different GUID in each, hence the conflicting result.






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users