How to Disable FileVault During a Fresh Installation (Clover & OpenCore)

[XanthraX]

2 hours ago, Max.1974 said:

Hi all, I discovered that if we add these two UEFI drivers from the V2 Off folder, we can log in directly and there will be no encryption process. In other words, there's no need to log in without signing into an Apple account and then do it again. Slice's tips from another post worked.

 

 

 - AppleKeyFeeder.efi

 

 - HashServiceFix.efi

 

But you still have an apple account to the system? Nevermind, I saw these drivers are for Clover.

Edited November 21, 2025 by XanthraX

[luxinhaus]

Proper patch for Clover

 

bdmesg result:

 

FilevaultDisabler.plist

Edited November 21, 2025 by luxinhaus

[Max.1974]

HI my friend, thanks so much! Works for you? 😁 Big Thanks!!!! 

 

I will test and change first page  

 

Look this @LockDown  

Edited November 21, 2025 by Max.1974

[Max.1974]

7 hours ago, XanthraX said:

But you still have an apple account to the system? Nevermind, I saw these drivers are for Clover.

Yes my friend, for Opencore not need drivers, its only for Clover users...sorry not said before...

[LockDown]

7 hours ago, luxinhaus said:

Proper patch for Clover

FilevaultDisabler.plist 810 B · 2 downloads

This worked!

 

@Max.1974 already tried it earlier 👍

Edited November 21, 2025 by LockDown

[Max.1974]

Thanks my brothers !!! You are the best!! 

 

 

I will edit first page !! Thanks !!! 

 

 

 

[maly70]

On 11/16/2025 at 4:05 PM, Max.1974 said:

Thanks to @LockDown and  @luxinhaus for perfect patch for Clover

 

And @Luchina for Opencore video tutorial on Youtube.

 

This tutorial aims to disable FileVault during installation or updates using patch key in Clover and OpenCore through a kernel patch, simply by adding the following keys:

 

Clover

 

FilevaultDisabler.plist 810 B · 3 downloads

 

 

 

 

Optionally its possible add this Drivers UEFI/Off from Clover V2 

 

 - AppleKeyFeeder.efi

 

 - HashServiceFix.efi

 

 

Opencore

 

 

FileVault-Disable Patch - Opencore - Hackintosh.plist.zip 1.32 kB · 2 downloads

 

 

The tests were performed using Clover 5164 (latest release), Opencore 1.0.6 and FileVault was not enabled during installation. 

 

If you need to enable it, you must remove or disable the patch in the config.plist.

 

Good Lucky 

 

 

 

Credits:  @Luchina 

 

https://youtu.be/9Wjvh--emWY

 

 

Thank you my Friend and thanks to @Luchina, it is working great .... thanks again

[verdazil]

I was interested in this topic because I've never encountered forced disk encryption. Today, I installed macOS 26.1 twice (4 and 5 PC in signature), and, as always, I was given the choice of encrypting or not. I didn't use any patches, special UEFI drivers or any other tricks.

 

I have a guess. A combination of two factors can cause the FileVault prompt to disappear:

1. Selecting an SMBIOS specific to a Mac with a T2 chip (one of the iMac20,1; iMac20,2; MacBookPro16,1; MacBookPro16,2; MacBookPro16,4; MacPro7,1)

2. Enabling SecureBootModel, which causes macOS to assume Secure Boot mode is active.

 

This causes macOS to behave as if a T2 chip is installed, which leads to side effects such as FileVault prompt disappear.

[FirstCustomac]

Hm. maybe this it? I am using T2less SMBIOS and whenever installing macOS 26, it always offered a choice of encryption as well. 

[Anto65]

Unm, but did you log in to your Apple ID during installation ?

 

 

[deeveedee]

One of my hacks uses SMBIOS MBP16,2 and others use MM8,1 (with boardid Booter Patch for Tahoe compatibility).  Both of these SMBIOS models have T2 and none of these hacks are forcing me to enable FileVault when I install or update macOS Tahoe.  For me, "forced" FileVault was only a problem with early Betas of Tahoe.  I thought Apple had fixed this problem and I wasn't aware that others were still experiencing forced FileVault with later versions of Tahoe until reading this thread.

[Anto65]

I repeat , in my opinion you should try enabling/logging into Apple ID during installation / upgrade . I believe this is what triggers the FV, regardless of smbios.
If you don't log into Apple ID or skip it during installation, you'll be asked whether to activate FV.

 

At least, that's what happened in my case.

 

Login into Apple ID = FV On
Not login into Apple ID = Offer to activate FV or not

 

( Obviously using the patch by @luchina and luxinhaus 🙏  ( Clover ) even after logging in with my Apple ID the FV does not activate )

Edited November 24, 2025 by Anto65

[deeveedee]

I thought I was logging into my Apple Account during the upgrade/install on my MBP16,2 and my MM8,1s, but now I'm not certain.  I will be sure to pay attention to this during my next install / upgrade.

[verdazil]

@Anto65, This seems plausible and doesn't contradict my experience - I never log into Apple ID during installation. But does everyone who encounters this problem log in?

[Matgen84]

Hi my friend @Max.1974

Just a question: FileVault Disabler patch must be disable after encryption  from macOS Tahoe session?

 

Sorry for my poor English.

[Matgen84]

On 11/21/2025 at 3:17 PM, Max.1974 said:

Yes my friend, for Opencore not need drivers, its only for Clover users...sorry not said before...

 

Hi @Max.1974  The two drivers is mandatory or optional as mentioned on the first post. Let me know, please.

[Anto65]

15 minutes ago, verdazil said:

@Anto65, This seems plausible and doesn't contradict my experience - I never log into Apple ID during installation. But does everyone who encounters this problem log in?

It's very likely they signed in during installation, or were already signed in to their Apple ID before upgrading to Tahoe... if you have a way to test it, it would be further confirmation.

I've tried multiple installations and upgrades with and without Apple ID, and the results are as described above.

Many users (macOS X86) who encountered the problem had the same experience, but were signed in or not signed out during the upgrade.

[FirstCustomac]

Aight, I am attempting an upgrade from Sequoia to macOS 26.1 after having to sign in with an account with no 2FA. Will report back indefinitely. 

 

Update: OK, I am still offered a encryption choice upon completion.

 

Spoiler

 

Edited November 24, 2025 by FirstCustomac

[strangeron]

I'm upgrading with my Apple ID. Filevault is always enabled and there is no preference screen. SMBios iMacPro 1.1 (Booter/Patch).

[strangeron]

Disable

[Anto65]

I forgot, do you have autologin enabled?
I also noticed that this prevents it from activating.

 

" FileVault cannot be activated because automatic login is enabled. " 

[Anto65]

I meant automatic login during upgrade, obviously with a clean install automatic login will not be enabled by default

Edited November 24, 2025 by Anto65

[verdazil]

1 minute ago, Anto65 said:

I meant automatic login during upgrade, obviously with a clean install automatic login will not be enabled by default

Yes, autologin was enabled during the test update.

[FirstCustomac]

34 minutes ago, strangeron said:

I'm upgrading with my Apple ID. Filevault is always enabled and there is no preference screen. SMBios iMacPro 1.1 (Booter/Patch).

iMacPro1,1 has T2.

[Anto65]

I'll try upgrading from Sequoia to Tahoe 26.1 , disabling automatic login and leaving Apple ID access enabled.
I'll simply launch the full installer (I already own the Tahoe 26.1 Release 25B78 ).
Unfortunately, I can't do it from Software Update due to my connection; it would take days to download 15-17 GB

... I think it's the same thing.