nice, would be curious on a separate thread how you do it as always used those tools but would prefer the power to do it myself without, even if more laborious as at least you can make it your own then
Yes confirmed by real world test, you DON'T need a recovery partition. Just deleted one on a computer here with bitlocker enabled (with preboot authentication) and it works fine, could even press escape at pre-boot PIN prompt and enter bitlocker recovery key and it booted fineThis implies that a separate recov partition isn't needed:
BitLocker overview - Windows Security
Learn about BitLocker practical applications and requirements.learn.microsoft.com
. At least we both confirmed it
Was definitely worth testing just to prove the point, as you say it gives us options now. And like you I would always boot from a UFD to solve problems anyway so never need the RE anyway.Sorry, I responded before I saw your post
Good question! sadly I don't have an answer
Man, you ain't kidding. But there's also a heck of a lot of satisfaction when you resolve a complex riddle.
It means there won't be autofailover in case of problems with startup etc.
if we have issues where a computer won't even boot then we boot from a UFD with various tools on to fix any basic issues or if terminal to recover any data (although technically they shouldn't be saving data locally!), but usually we just reapply our custom image again as usually it is just quicker to do this than it is to spend time fixing problems if files etc corrupt
Nor do I, and I never will, but I still want to understand it and I do not. I had read the gobbly-gook MS instructions in the release notes on the cumulative before this thread was even opened and this thread has provoked even more confusion for me.
1 - You are dead on correct. No need for any of this if you are not using BitLocker. The whole issue is that the Recovery Environment can be exploited so that someone with physical access to the machine could potentially gain access to the BitLocker encrypted data.
I think that is spot on - it is simply that Microsoft don't always update WinRE everytime they release a new build / ISO of Windows
gist.github.com
gist.github.com
2004 and all versions up to 22H2 share a common set of system files. From 2004 up to 22H2 all new features have been delivered in the cumulative updates, but in a dormant state. Each Feature Update was done by means of installing an Enablement Package that turned on the new features and bumps up the major build number by 1, the 22H2 update taking it to 19045.
