Does FileVault encrypt the disk instantly?
I have recently found that FileVault is disabled on my machine. Although I remember that I set "encrypt" option when I was setting the machine up.
I opened System Preferences and enabled FileVault. To my surprise it didn't take any time. I didn't have to wait while the data is encrypted. It just got instantly enabled.
How does it possible that turning on FileVault doesn't take any time?
macos encryption filevault
add a comment |
I have recently found that FileVault is disabled on my machine. Although I remember that I set "encrypt" option when I was setting the machine up.
I opened System Preferences and enabled FileVault. To my surprise it didn't take any time. I didn't have to wait while the data is encrypted. It just got instantly enabled.
How does it possible that turning on FileVault doesn't take any time?
macos encryption filevault
1
There are 3 main implementations of FV. Can you specify what machine you have (model year ideally) and what version of macOS? We'll need to know if you have an SSD or HDD. We might even need to know if you havediskutil cs listordiskutil apfs listto know if the conversion is still happening in the background.
– bmike♦
3 hours ago
add a comment |
I have recently found that FileVault is disabled on my machine. Although I remember that I set "encrypt" option when I was setting the machine up.
I opened System Preferences and enabled FileVault. To my surprise it didn't take any time. I didn't have to wait while the data is encrypted. It just got instantly enabled.
How does it possible that turning on FileVault doesn't take any time?
macos encryption filevault
I have recently found that FileVault is disabled on my machine. Although I remember that I set "encrypt" option when I was setting the machine up.
I opened System Preferences and enabled FileVault. To my surprise it didn't take any time. I didn't have to wait while the data is encrypted. It just got instantly enabled.
How does it possible that turning on FileVault doesn't take any time?
macos encryption filevault
macos encryption filevault
edited 3 hours ago
bmike♦
157k46284612
157k46284612
asked 4 hours ago
Oleksandr ShpotaOleksandr Shpota
185317
185317
1
There are 3 main implementations of FV. Can you specify what machine you have (model year ideally) and what version of macOS? We'll need to know if you have an SSD or HDD. We might even need to know if you havediskutil cs listordiskutil apfs listto know if the conversion is still happening in the background.
– bmike♦
3 hours ago
add a comment |
1
There are 3 main implementations of FV. Can you specify what machine you have (model year ideally) and what version of macOS? We'll need to know if you have an SSD or HDD. We might even need to know if you havediskutil cs listordiskutil apfs listto know if the conversion is still happening in the background.
– bmike♦
3 hours ago
1
1
There are 3 main implementations of FV. Can you specify what machine you have (model year ideally) and what version of macOS? We'll need to know if you have an SSD or HDD. We might even need to know if you have
diskutil cs list or diskutil apfs list to know if the conversion is still happening in the background.– bmike♦
3 hours ago
There are 3 main implementations of FV. Can you specify what machine you have (model year ideally) and what version of macOS? We'll need to know if you have an SSD or HDD. We might even need to know if you have
diskutil cs list or diskutil apfs list to know if the conversion is still happening in the background.– bmike♦
3 hours ago
add a comment |
2 Answers
2
active
oldest
votes
If you have a new Mac with an SSD and T2 chip, then all data on it is encrypted always. Any election you make in FileVault just adds and removes user keys from the trust chain so that happens basically instantly.
The next time you restart, the system will notice that the first per-user key is now active and change the boot process so that the system won't unlock that storage and start the OS until your key unlocks the storage.
If I guessed wrong, we can sort out if your encryption is still being done behind the scenes by looking at diskutil output to examine any APFS and CoreStorage containers that implement the layer between the encryption on disk and the view once the volume is unlocked and mounted.
mac:~ me$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.0 GB disk1
Physical Store disk0s2
1: APFS Volume Mac 191.7 GB disk1s1
2: APFS Volume Preboot 65.4 MB disk1s2
3: APFS Volume Recovery 1.0 GB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
add a comment |
I didn't set "encryption" on while installing my System, but turning on Encryption with FileVault afterwards definitely takes time (about 45 min with a 512 Go SSD).
Decrypting the disk will take time with a background process as well.
You can check if your disk is encrypted or not (or in progress) through the Terminal with entering this command:
sudo fdesetup status
From your experience, it looks like enabling encryption during setup does the work, but doesn't show up in the "System Preferences" until you explicitly turn it on?

Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "118"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f349028%2fdoes-filevault-encrypt-the-disk-instantly%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
If you have a new Mac with an SSD and T2 chip, then all data on it is encrypted always. Any election you make in FileVault just adds and removes user keys from the trust chain so that happens basically instantly.
The next time you restart, the system will notice that the first per-user key is now active and change the boot process so that the system won't unlock that storage and start the OS until your key unlocks the storage.
If I guessed wrong, we can sort out if your encryption is still being done behind the scenes by looking at diskutil output to examine any APFS and CoreStorage containers that implement the layer between the encryption on disk and the view once the volume is unlocked and mounted.
mac:~ me$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.0 GB disk1
Physical Store disk0s2
1: APFS Volume Mac 191.7 GB disk1s1
2: APFS Volume Preboot 65.4 MB disk1s2
3: APFS Volume Recovery 1.0 GB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
add a comment |
If you have a new Mac with an SSD and T2 chip, then all data on it is encrypted always. Any election you make in FileVault just adds and removes user keys from the trust chain so that happens basically instantly.
The next time you restart, the system will notice that the first per-user key is now active and change the boot process so that the system won't unlock that storage and start the OS until your key unlocks the storage.
If I guessed wrong, we can sort out if your encryption is still being done behind the scenes by looking at diskutil output to examine any APFS and CoreStorage containers that implement the layer between the encryption on disk and the view once the volume is unlocked and mounted.
mac:~ me$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.0 GB disk1
Physical Store disk0s2
1: APFS Volume Mac 191.7 GB disk1s1
2: APFS Volume Preboot 65.4 MB disk1s2
3: APFS Volume Recovery 1.0 GB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
add a comment |
If you have a new Mac with an SSD and T2 chip, then all data on it is encrypted always. Any election you make in FileVault just adds and removes user keys from the trust chain so that happens basically instantly.
The next time you restart, the system will notice that the first per-user key is now active and change the boot process so that the system won't unlock that storage and start the OS until your key unlocks the storage.
If I guessed wrong, we can sort out if your encryption is still being done behind the scenes by looking at diskutil output to examine any APFS and CoreStorage containers that implement the layer between the encryption on disk and the view once the volume is unlocked and mounted.
mac:~ me$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.0 GB disk1
Physical Store disk0s2
1: APFS Volume Mac 191.7 GB disk1s1
2: APFS Volume Preboot 65.4 MB disk1s2
3: APFS Volume Recovery 1.0 GB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
If you have a new Mac with an SSD and T2 chip, then all data on it is encrypted always. Any election you make in FileVault just adds and removes user keys from the trust chain so that happens basically instantly.
The next time you restart, the system will notice that the first per-user key is now active and change the boot process so that the system won't unlock that storage and start the OS until your key unlocks the storage.
If I guessed wrong, we can sort out if your encryption is still being done behind the scenes by looking at diskutil output to examine any APFS and CoreStorage containers that implement the layer between the encryption on disk and the view once the volume is unlocked and mounted.
mac:~ me$ diskutil list
/dev/disk0 (internal):
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme 251.0 GB disk0
1: EFI EFI 314.6 MB disk0s1
2: Apple_APFS Container disk1 250.0 GB disk0s2
/dev/disk1 (synthesized):
#: TYPE NAME SIZE IDENTIFIER
0: APFS Container Scheme - +250.0 GB disk1
Physical Store disk0s2
1: APFS Volume Mac 191.7 GB disk1s1
2: APFS Volume Preboot 65.4 MB disk1s2
3: APFS Volume Recovery 1.0 GB disk1s3
4: APFS Volume VM 3.2 GB disk1s4
edited 3 hours ago
answered 3 hours ago
bmike♦bmike
157k46284612
157k46284612
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
add a comment |
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
This best explain why turning on FileVault didn't take any time for the author of the question (all data is encrypted always with T2 chip).
– Yoric
3 hours ago
add a comment |
I didn't set "encryption" on while installing my System, but turning on Encryption with FileVault afterwards definitely takes time (about 45 min with a 512 Go SSD).
Decrypting the disk will take time with a background process as well.
You can check if your disk is encrypted or not (or in progress) through the Terminal with entering this command:
sudo fdesetup status
From your experience, it looks like enabling encryption during setup does the work, but doesn't show up in the "System Preferences" until you explicitly turn it on?

Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
add a comment |
I didn't set "encryption" on while installing my System, but turning on Encryption with FileVault afterwards definitely takes time (about 45 min with a 512 Go SSD).
Decrypting the disk will take time with a background process as well.
You can check if your disk is encrypted or not (or in progress) through the Terminal with entering this command:
sudo fdesetup status
From your experience, it looks like enabling encryption during setup does the work, but doesn't show up in the "System Preferences" until you explicitly turn it on?

Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
add a comment |
I didn't set "encryption" on while installing my System, but turning on Encryption with FileVault afterwards definitely takes time (about 45 min with a 512 Go SSD).
Decrypting the disk will take time with a background process as well.
You can check if your disk is encrypted or not (or in progress) through the Terminal with entering this command:
sudo fdesetup status
From your experience, it looks like enabling encryption during setup does the work, but doesn't show up in the "System Preferences" until you explicitly turn it on?

I didn't set "encryption" on while installing my System, but turning on Encryption with FileVault afterwards definitely takes time (about 45 min with a 512 Go SSD).
Decrypting the disk will take time with a background process as well.
You can check if your disk is encrypted or not (or in progress) through the Terminal with entering this command:
sudo fdesetup status
From your experience, it looks like enabling encryption during setup does the work, but doesn't show up in the "System Preferences" until you explicitly turn it on?

answered 3 hours ago
YoricYoric
5206
5206
Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
add a comment |
Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
Excellent answer covering the non APFS and non-T2 situation. This dialog will show for APFS (lacking T2) and all CoreStorage FileVault situations other than the original FV that made a sparse disk image instead of encrypting the whole volume.
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
I'm just guessing - you could still be right for this case. We don't have enough data from OP yet to tell. I do know this answer will help other people +1 for that
– bmike♦
3 hours ago
add a comment |
Thanks for contributing an answer to Ask Different!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fapple.stackexchange.com%2fquestions%2f349028%2fdoes-filevault-encrypt-the-disk-instantly%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
There are 3 main implementations of FV. Can you specify what machine you have (model year ideally) and what version of macOS? We'll need to know if you have an SSD or HDD. We might even need to know if you have
diskutil cs listordiskutil apfs listto know if the conversion is still happening in the background.– bmike♦
3 hours ago