You might still be in a panic, but you’re more likely to actually remember how to get to that recovery key. It’s much better (and safer) to either store your Bitlocker recovery key in Azure AD (for enterprises) or in a Microsoft account (for home computers). I also guarantee that you’ll likely forget the super-secret place you stuck the printed-out recovery key or the USB flash drive where it’s stored, and you’ll have to totally rebuild that computer. I guarantee you at some point you will have either a patching issue that triggers a Bitlocker recovery key event, or a hardware issue that requires the recovery key. I strongly recommend that anyone using Bitlocker encryption on their hard drive reconsider using only a Local account instead of a Microsoft account. (Once again, the key to avoiding this speed bump is to keep the PC off the internet while setting it up so you can work around the Microsoft account mandate.)
One of the concerns that’s come up as 22H2 gets closer is the requirement for a Microsoft account during setup. So, if you have any office - or home - NAS devices that can’t support SMBv2 or v3, it’s time to decide: do you want better network security or do you prefer to just post a sticky note on your computer urging attackers to “hack me.” Microsoft is again pushing to get rid of Server Message Block (SMB) version 1 (SMBv1). (It will also warn you if you’ve entered your Microsoft account passwords on phishing sites.)
For example, Microsoft Defender SmartScreen will alert users when they store passwords insecurely, such as typing them in plain texts using Notepad. In terms of Windows 11 22H2 itself, what am I looking forward to? Lots of little enhancements involving security.
0 kommentar(er)
