Bitlocker was developed entirely inside MSFT. Upon further review, there is a chance that this is all somewhat normal behaviour. Part of MSFT safeOS to make it convenient to recover bitlocker access, and update windows.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
replies: