New
#470
It's not the same as Bitlocker.
Here's the Microsoft link:
https://docs.microsoft.com/en-us/win...yption-for-oem
My experience with Windows 8.1 (can't remember which W10 versions I tested it on) was that on my cheap tablet with W8.1 Core, switching on Secure Boot and logging in with an (admin-level) MS Account was enough to start it encrypting.With the right hardware configurations, Windows 10 automatically encrypts a device, helping to keep customer data safe.
Interesting.
From DavidY's link...
...and later on:Windows 10 device encryption is enabled only after users sign in with a Microsoft Account or an Azure Active Directory account. Device encryption is not enabled with local accounts.
My system (legacy bios, so it shouldn't) says...Starting with Windows 10, version 1703, use the following steps to determine if the system supports automatic device encryption.
- Click Start, and type System information
- Right-click System Information app and click Open as Administrator. Allow the app to make changes to your device by clicking Yes. Some devices might require elevated permissions to view the encryption settings.
- In System Summary, see Device Encryption Support. The value will state if the device is encrypted, or if not, reasons why it is disabled.
What does yours say?Device Encryption Support
Reasons for failed automatic device encryption: TPM is not usable, PCR7 binding is not supported, Hardware Security Test Interface failed and the device is not InstantGo, Un-allowed DMA-capable bus/device(s) detected, Disabled by policy, TPM is not usable
OK!
Now I see what this encryption fuzz is all about.
Read this: Wikipedia - InstantGo
Based on this information, automatic encryption is only available on devices that meet all the requirements mentioned in the article.
My laptop has all of those requirements, except it also supports booting using legacy boot (BIOS/MBR), so automatic encryption is disabled because of this limitation. Requires a UEFI ONLY capable device.
Here's what my computer outputs:
Device Encryption Support: Reasons for failed automatic device encryption: Hardware Security Test Interface failed and device is not InstantGo, Disabled by policy
Here is more talk about this: TenForums - Reasons for failed automatic device encryption...Post #11
I have Hibernation issues with this build and 17133, like once every 3-4 times it won't shut down the PC.
Running 17134.1 has brought a good issue I have never seen in any Windows. After running diskcleanup to remove the old Windows folder and stuff, I had 82.8GB free. Most I have had free in Windows 10. I thought this is great. Now let's move along to last night, 84.0GB free... wow thats great. I get on the PC this morning and have 84.7 free
I have seen my drive shrink before, but getting more space is a first. I normally had around 77GB free with the FCU.