Recent content by Comport Colin

Ok, for the case that someone uses multiple bootable disks, that will be the necessary, correct. I wíll change that today, thanks for pointing out.

It's encrypted but with an empty key which would get exchanged for a real one as soon as you log on with a Microsoft account. If you don't want to use a Microsoft account AND you're on Windows Home Edition, there's a workaround for you which I describe here: How to use Bitlocker on Windows 10...

It is encrypted but no protectors are active, so it's "not armed" and thus, anyone can access it at any time. There is no recovery password to retrieve as there's none set. If I am not mistaken, manage-bde -off c: should work on an elevated command prompt in order to turn it off completely.

I wonder why you care about your mouse and not your keyboard. Mouse movement, unless perfectly relatable to GUI buttons that do something secret like an onscreen keyboard for PIN entry could, is usually not seen as critical. often, companies disallow non-corded keyboards while they impose no...

No, this behavior is still the same as of w11 24H2. But anyhow, you know the solution.

I am sure that the truth is: the account that you create when setting up the PC (during OOBE) will have the flag "password never expires", while any new local account you create afterwards won't but instead obeys the default machine account pw policy which is documented to be the default...

On the Win11 home OS edition (your specs say that you use pro - is that the same machine?), you would not even have a GUI to set a password to "never expire" and by default, it expires after 6 weeks. That's my experience for years, if Brink says, "by default it is set to 'never expire'" I would...

Device Encryption and Bitlocker are technically identical. DevEnc is a limited version of Bitlocker, it has less config options but more requirements (since Microsoft wants you to give something for the benefit of DevEnc, they let you use it only with a Microsoft account). So what you replied to me is...

I wrote How to use Bitlocker on Windows 10 Home | Experts Exchange in order to show a way how to encrypt your drive even when device encryption requirements are not met. Use it if you understand what it's about.

The real question in my opinion is: why would keepass xc even ask for this PIN? Did you configure XC to use windows hello in addition to the password (is that even configurable)? If it is, the PIN entry should be mandatory. About the question as gathered from the title of this thread: a PIN is a...

As said, for compatibility, you should use the compatible mode, as depicted. Since you want it to work on older OS', you have no choice.

Exactly, sorry for the confusion. Windows2Go is no longer supported and thus, bitlocking Windows2Go as well, while Bitlocker2Go remains supported. Of course, Windows2Go still works, even with newer windows versions there are ways to set it up and I still use it myself.

Nothing could go wrong with any of the encr. algorithms. As for "the fastest" - do your own benchmarks. I guess nobody will ever have cared since BL2Go is a niche product and no longer supported. I don't think switching from (default) "XTS_AES128" to "aes128" will make a difference.

As you status query shows, c: is not even encrypted, so the OS and its programs cannot be affected.

Dave, any feedback?