Contribute
Register

How to Update + Current and Past apfs.efi Downloads

Sorry, but the instructions 1,2,3,4 below are ambiguous. Could you clarify please? Thanks.
I see no ambiguity, which part are you struggling with ?

This is quite an old thread and most people now would just use ApfsDriverLoader-64.efi instead of updatiing apfs.efi.
 
I see no ambiguity, which part are you struggling with ?

This is quite an old thread and most people now would just use ApfsDriverLoader-64.efi instead of updatiing apfs.efi.

3. Navigate to /usr/standalone/i386/
4. Copy apfs.efi to /Volumes/EFI/EFI/CLOVER/drivers64UEFI/

So i navigate to the folder /usr/standalone/i386.

Then copy afps.efi to /volumes/etc.

Where did afps.efi come from?
Why did I navigate to /usr/standalone/etc?

I am sucessfully using Mojave 14.1 but trying to get sound working and keep following threads that i don't properly understand.
 
Where did afps.efi come from?
It comes from the OS installer.

Why did I navigate to /usr/standalone/etc?
Because that is where apfs.efi is placed by the installer but it must be copied to the EFI partition for Clover's use.

As stated previously, constantly updating apfs.efi has been rendered redundant by use of ApfsDriverLoader-64.efi.

I am sucessfully using Mojave 14.1 but trying to get sound working and keep following threads that i don't properly understand.
apfs.efi will have absolutely no bearing whatsoever on audio problems.
 
So i navigate to the folder /usr/standalone/i386.

Then copy afps.efi to /volumes/etc.

Where did afps.efi come from?
Why did I navigate to /usr/standalone/etc?

I am sucessfully using Mojave 14.1 but trying to get sound working and keep following threads that i don't properly understand.
newer versions of clover already has ApfsDriverLoader-64 so you don't need to get apfs.efi
 
Thanks, Pilgrim.

I'm now looking at Lilu threads.


It comes from the OS installer.


Because that is where apfs.efi is placed by the installer but it must be copied to the EFI partition for Clover's use.

As stated previously, constantly updating apfs.efi has been rendered redundant by use of ApfsDriverLoader-64.efi.


apfs.efi will have absolutely no bearing whatsoever on audio problems.
 
Hi,
I read somewhere that the Mojave 10.14.2 update has improved boot time.
Do you think it's a good idea to grab apfs.efi file from a 10.14.2 installation and put it on my High Sierra system to get a faster boot?
 
Hi,
I read somewhere that the Mojave 10.14.2 update has improved boot time.
Do you think it's a good idea to grab apfs.efi file from a 10.14.2 installation and put it on my High Sierra system to get a faster boot?

Why do you think it would give you a faster boot time in High Sierra?
It is a Mojave optimised file for a Mojave optimised file system, it wouldn't change the file system on your drive?
 
APFS is the default file system for Mojave AND High Sierra, so why not?
Anyway, I was just asking for some opinions and I don't think it is such a dumb question...
Nonetheless, thanks for your input.

All other thoughts are welcome.
 
Last edited:
APFS is the default file system for Mojave AND High Sierra, so why not?

But file systems evolve and the apfs in High Sierra will be slightly different to the apfs in Mojave. It will be backward compatible as far as the apfs driver is concerned but still different. That is why it is best to use ApfsDriverLoader-64.efi as that reads the current apfs.efi from your system. Without it you need to copy the latest apfs.efi to your efi/clover/drivers64UEFI folder every time there is an update to gain the benefits it provides and to ensure the updated file system is fully optimised. Just loading the apfs.efi to an older system will not provide any of the benefits of the newer system.

Just trying to be helpful!
 
Mojave APFS is not different from High Sierra APFS. It is the same file system with the same features. The logical structure of a Mojave APFS volume is strictly the same as a High Sierra APFS volume.

If something evolves, it is only the performance of the "engine" behind APFS, not the functionality. And because it's a very new file system, no doubt that Apple is trying hard to optimize it to speed up read/write operations, among other improvements and bugs hunt.

I know ApfsDriverLoader-64.efi and use it from the beginning, but that has nothing to do with my initial question.

For your information, boot time of my Skylake rig has doubled from Sierra HFS+ to High Sierra APFS. I know boot time is not essential, but in some manner, it reflects the performance of global volumes access.

I am sure Apple, in the near future, will improve APFS performance, and not only for Mojave users... In the meantime, all workarounds are welcome! ;)
 
Back
Top