Romkslrqusz

@[email protected]

This profile is from a federated server and may be incomplete. View on remote instance

Romkslrqusz ,

USB can actually be ideal in some data recovery scenarios. HDDSuperClone / OpenSuperClone support a relay mode that turns a disk off and back on to regain access after they drop out, and that is reliant on a USB connection.

Romkslrqusz ,

I own a repair shop and use USB to SATA adapters all the time. Sector scans, imaging/cloning, and booting live environments.

It has less to do with the medium and more to do with the quality of your chosen adapter.

I have one of the adapter you pictured, ordered it to test it out because it was comparatively low cost. Did not order more.

I have about a dozen of the Sabrent adapters and they see daily use.

Romkslrqusz ,

You should, it’s quite powerful and can work in tandem with both DMDE and UFS Explorer!

Power cycling the drive reboots and reinitializes it. I’ve mostly seen it with SSDs - you get a few dozen MB worth of reads before it drops out, unplugging and reconnecting a SATA power connector that many times would be real tedious so you automate it with a relay.

Romkslrqusz ,

The automatic encryption and subsequent backup both took place because you were using a Microsoft Account

Romkslrqusz ,

Hi, repair shop owner here.

Automatic Bitlocker encryption has been a thing since TPM 2.0 devices hit the market in 2018.

If a device is UEFI, Secure Boot is enabled, TPM 2.0 is present, and the user signs in with a Microsoft Account , then the disk is encrypted and the recovery key is saved to that Microsoft Account.

If those conditions aren’t met, automatic encryption doesn’t happen.

As long as they know their Microsoft Account Identifier, users can easily get to that key through the first search engine result for “bitlocker recovery key”: https://support.microsoft.com/en-us/windows/finding-your-bitlocker-recovery-key-in-windows-6b71ad27-0b89-ea08-f143-056f5ab347d6

We don’t really have a hard time with it - if a user provides their login PIN, a short terminal command will let us grab a copy of their key before BIOS updates or battery disconnects.

I have had very few cases where folks suffered data loss because of Bitlocker.
Most of them were HP Laptops that used Intel Optane accelerated SSDs - encrypting what is effectively a software RAID0 is a recipe for disaster.

The other few had an unhealthy paranoia where they were reluctant to share anything about themselves with Microsoft, yet still decided to use a Microsoft operating system. While setting up the computer, they created a new Outlook.com email (instead of using their primary email), made up a random birthday, and did not fill in any recovery options like a phone number or secondary email. With the password (and sometimes even email) forgotten, they created a situation where they could not prove the online account was theirs and therefore could not get to the recovery key that had been backed up.

I do think that Microsoft should have this as an opt-in feature during the out of box experience, which is how Apple has it set up for Filevault and how most Linux distributions are set up. Ultimately, most users will still mash “next’ through the process and later blame the computer.

I have had quite a few clients have their laptops stolen after car breakins. Their biggest stressor was the possibility of thieves having access to the data on those machines, and the fact that we knew their systems were encrypted with Bitlocker brought them a lot of relief.

Romkslrqusz ,

There are dozens of more probable scenarios that could have the same outcome. Mitigation is as simple as keeping at least one backup, a recommendation as old as home computing.

Ironically, the problem you describe most commonly applies to systems with Intel Optane storage technology, so it’s hardly even a Microsoft Issue.

Romkslrqusz ,

Then don’t?

If you still want to use Windows and use their encryption solution, manually enable Bitlocker and store the recovery key yourself.

There are also third party encryption options.

Romkslrqusz ,

If you’re at that point of not trusting a company, the best practice would be to avoid using their devices or connecting them to your network.

There are plenty of other ways to track and identify users, a company could conceivably bake whatever the hell they want into the operating system and doesn’t need to rely on you creating an account with them to achieve that objective.

I used the term “unhealthy paranoia” due to the logical fallacy that is at play.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • kbinchat
  • All magazines