bookie32 Posted June 25, 2018 Author Share Posted June 25, 2018 Thanks Tripredacus! I gave it the attribute 0x8000000000000000 and then removed the letter assigned via diskpart and it wasn't there after reboot...nice fix... bookie32 Link to comment Share on other sites More sharing options...
jaclaz Posted June 25, 2018 Share Posted June 25, 2018 38 minutes ago, bookie32 said: Thanks Tripredacus! I gave it the attribute 0x8000000000000000 and then removed the letter assigned via diskpart and it wasn't there after reboot...nice fix... bookie32 Should be 0x8000000000000001, not 0x8000000000000000. https://superuser.com/questions/1108243/setting-winre-windows-recovery-environment-flag-on-partitions jaclaz Link to comment Share on other sites More sharing options...
bookie32 Posted June 25, 2018 Author Share Posted June 25, 2018 Yes I agree but with that attribute I couldn't remove the assigned letter.... I tried that attribute and then removed the assigned letter but after reboot it was back... So, I don't know why it worked the way I did it... I will try again to make sure.... Thanks for your reply! bookie32 Link to comment Share on other sites More sharing options...
jaclaz Posted June 25, 2018 Share Posted June 25, 2018 22 minutes ago, bookie32 said: Yes I agree but with that attribute I couldn't remove the assigned letter.... I tried that attribute and then removed the assigned letter but after reboot it was back... So, I don't know why it worked the way I did it... I will try again to make sure.... Thanks for your reply! bookie32 In case you can try the other way round, i.e. first remove the drive letter with mountvol (this, unless the flag already starts with 0x80... will be only temporary until next reboot), then change the attribute flag with diskpart. jaclaz Link to comment Share on other sites More sharing options...
bookie32 Posted June 26, 2018 Author Share Posted June 26, 2018 Thanks jaclaz! That worked.....;) bookie32 Link to comment Share on other sites More sharing options...
jaclaz Posted June 26, 2018 Share Posted June 26, 2018 2 hours ago, bookie32 said: Thanks jaclaz! That worked.....;) bookie32 Good. Now that the issue is solved, we can comment wondering what (the heck) the good MS guys "touched" related to GPT partitioning and/or Disk Manager and/or Mount Manager (or Explorer) "touched" to create the issue (which seemingly is not an isolated case, but happened to lots of people). That partitioning scheme wth the "recovery" partition is AFAICR the same - suggested by MS themselves in official documentation - since Windows 8 (i,e- circa 2012) and in themselves the behaviours of the involved subsystems is the same since the dawn of time on NT systems. Thet "invented" the 27 and then the DE94BBA4-06D1-4D40-A16A-BFD50179D6AC (and conversely the 0x8000000000000001) and now they don't even respect it? jaclaz Link to comment Share on other sites More sharing options...
bookie32 Posted June 26, 2018 Author Share Posted June 26, 2018 I don't really spend time "wondering" about anything Microsoft does these days....it is just one continuous nightmare.... 1 minute ago, jaclaz said: Good. Now that the issue is solved, we can comment wondering what (the heck) the good MS guys "touched" related to GPT partitioning and/or Disk Manager and/or Mount Manager (or Explorer) "touched" to create the issue (which seemingly is not an isolated case, but happened to lots of people). That partitioning scheme wth the "recovery" partition is AFAICR the same - suggested by MS themselves in official documentation - since Windows 8 (i,e- circa 2012) and in themselves the behaviours of the involved subsystems is the same since the dawn of time on NT systems. Thet "invented" the 27 and then the DE94BBA4-06D1-4D40-A16A-BFD50179D6AC (and conversely the 0x8000000000000001) and now they don't even respect it? jaclaz bookie32 1 Link to comment Share on other sites More sharing options...
Tripredacus Posted June 26, 2018 Share Posted June 26, 2018 6 hours ago, jaclaz said: Now that the issue is solved, we can comment wondering what (the heck) the good MS guys "touched" related to GPT partitioning and/or Disk Manager and/or Mount Manager (or Explorer) "touched" to create the issue (which seemingly is not an isolated case, but happened to lots of people). Similar to this issue I replicated with the Windows 8.1 update on GPT disks, where the original recovery partition had attributes of 0x8000000000000001, then after the update, Windows changed those attributes to 0x8000000000000000, and then created an additional recovery partition with 0x8000000000000001. https://msfn.org/board/topic/169284-windows-81-creates-2nd-recovery-partition/ Link to comment Share on other sites More sharing options...
mikedigitize Posted July 17, 2018 Share Posted July 17, 2018 On 6/25/2018 at 1:28 PM, bookie32 said: we keep on track with this thread I will send you a link when more pics are on onedrive Any progress? Link to comment Share on other sites More sharing options...
bookie32 Posted July 17, 2018 Author Share Posted July 17, 2018 Do you mean with the cottage? Haven't had time to put up any new pics... Link to comment Share on other sites More sharing options...
mikedigitize Posted July 18, 2018 Share Posted July 18, 2018 no panic... Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now