EFI Mounter

[verdazil]

3 hours ago, Anto65 said:

I believe the app identifies the topmost drive in the list as the boot drive.
When rebooting, for example, on Windows or other systems, I don't know why the disk order changes... it happens with OCAT too ( When mounting EFIs ) , but the app always marks the topmost drive as the boot disk.

This is an old known issue with macOS. After each reboot, disks can get random numbers. And this is visible not only in the discussed application, but also in Disk Utility.

 

@Cyberdevs, I was thinking about why everything works perfectly on all our computers, while our colleagues have problems. As a guess, the problem may lie in errors or incorrect user approaches to organizing disk space and hardware configuration in general. For example, they could use not only built-in MacOS tools but also Windows applications to partition disks. They could break the unwritten and not strict rule that the bootable system should be on the first (in BIOS) hard drive. And the bootloader should preferably (but not necessarily) be located on the same hard drive as the system. For example, I always observe all these nuances. Maybe that's why everything works fine for me? 😀

[Anto65]

I was about to write exactly that  😄 . I set ExposeSensitiveData to 15, I already had 14. I rebooted all the systems, and every time it gave the correct information.
With the last reboot on Tahoe, it went haywire again.

 

SN520 is the boot-disk  🤷‍♂️

 

Spoiler

 

All partitions were created by macOS... in my case... colleague

[Cyberdevs]

@verdazil

Yes that's a important factor in all systems, I'm aware of the random disk numbers but i'm almost sure beside that issue the ExposeSensitiveData in config plist plays a big roll as well.

v 0.2 was and is working ok on our end simply because the EFI Folder is placed in the EFI partition of the same disk on all of my rigs. and that disk is usually the first disk as you have it set.

I'm beginning to think it's the combination of two 😕

@Anto65

I have set it to 0x07 and it behaves the same on Ventura, Sequoia and Tahoe

[Cyberdevs]

1 minute ago, eSaF said:

I don't know if I have done the correct thing by installing the 0.2 version.

This is the result of that version after changing the  ExposeSensitiveData value to 7.

 

It is now showing the uppermost Drive as the Boot Disk which is incorrect.

Maybe I need to move the Drive containing the EFI Folder to that position??!!

No man don't touch anything in your system yet.

I need to review the code and see if I can find a way to get this fixed. It should work on all systems with any configuration. If I fail then you can change your system if you want

 

3 minutes ago, verdazil said:

@Cyberdevs, what if we recommend for problematic configurations the value ExposeSensitiveData = 32?

I need to test that and see how it plays out and then we can recommend it.

[Cyberdevs]

8 minutes ago, verdazil said:

@Cyberdevs, what if we recommend for problematic configurations the value ExposeSensitiveData = 32?

Can you tell me what exactly 32 does?

[verdazil]

10 minutes ago, Cyberdevs said:

Can you tell me what exactly 32 does?

Sorry, I counted the bits wrong. I meant 1+2+4+8 = 15

 

By the way, I have 15

Edited August 10, 2025 by verdazil

[Anto65]

32 ? Misc->Security->ExposeSensitiveData has unknown bits set! CheckMisc returns 1 error!

 

I'm already using ExposeSensitiveData 15

https://www.insanelymac.com/forum/topic/361492-esp-efi-mounter/page/3/#findComment-2838813

 

 

For now, I'm stopping here with version 0.2, it works... sometimes, during a reboot, the EFI disk changes position, and another disk is displayed that won the race and came in first place 😆 ... but this happens very rarely.
I'm already happy with the fact that I don't have to enter any passwords... thanks Cyb

 

Spoiler

 

Edited August 10, 2025 by Anto65

[Cyberdevs]

@verdazil

I'm not sure what the outcome would be let's give it a try and see.

But that's it for me for today. I'm gonna head out and I'll be back later to check out the responses.

 

Cheers all and thanks for your time and your feedback.

[Mirone]

3 hours ago, Cyberdevs said:

@eSaF

Nah, my brain doesn't tell me what to do! I tell it what to do. Or it's the other way around I'm not sure anymore

Something that I don't understand is why the app is working on my two rigs but it doesn't show the Apple Logo on your end! and why it doesn't detect the Boot Disk on your rig. If Samsung SSD 980 Pro 500GB is your bootable disk and it has OC in the EFI partition of that disk it should be marked as Boot Disk with Apple Logo instead of the generic internal hdd icon. 

Welcome to my world...LoL

[Cyberdevs]

Here is the v 0.3

Please test and give me your feedback, just remember this is a work in progress so there are bugs and glitches all over

 

To explain the logic the disk with Apple Logo (if that shows up correctly) is the disk that macOS has booted from, it doesn't mean that this disk necessarily has OpenCore in the EFI partition of the disk (I will get to that later in the next release)

The disks color indicators:

• Boot Disk (green) - Highest priority (The disk that macOS booted form Green Boot Disk indicator shows OpenCore)
• OpenCore (orange) - Second priority
• macOS (APFS-HFS FileSystem) (blue) - Third priority
• Windows (cyan) - Fourth priority
• Linux (purple) - Fifth priority (I don't have linux on my system so I can't know for sure if this works)

 

About ExposeSensitiveData setting in config.plist we actually only need the first two settings to be enabled so the app can detect the version and the booter path correctly. Feel free to test other values and see if that changes anything in the app and share them with me.

Spoiler

 

 

I hope to get some positive feedbacks.

Cheers

 

ESP Mounter v0.3.zip

[ANTIKO]

12 hours ago, Cyberdevs said:

I hope to get some positive feedbacks.

An elegant option)), the logic is clear))

Spoiler

 

[Cyberdevs]

@eSaF

Amazing, thanks 

[Anto65]

The option that opened the EFI folder when clicking "mount" is no longer there... is this intentional?

 

I'm waiting to give final feedback.

I'm installing Linux on a separate disk because it's not being detected in a partition on the same disk... OC is evidently prevailing.

 

Anyway, after a few reboots I've done, it correctly displays the boot disk and marks Win correctly.

 

 

This is the real best and simple app for mounting and unmounting EFI partitions

[Anto65]

Bingo 

 

 

[Cyberdevs]

10 minutes ago, Anto65 said:

The option that opened the EFI folder when clicking "mount" is no longer there... is this intentional?

That should work, I haven't changed it and it works on my end

[Anto65]

I have to go out now... I'll try again later.
Thanks again.

[Cyberdevs]

@Anto65

Sure thing. I have to go too. We'll continue later

[Anto65]

I'll also provide you with the Clover log later... maybe it can be useful to you. 

[Cyberdevs]

@Anto65

Yes I'm planning to add Clover too, thanks that would be nice

[Alpha22]

boot from USB Open core

 

Spoiler

    

 

 boot from USB Clover

 

Spoiler

 

Edited August 11, 2025 by Alpha22

[Cyberdevs]

@Alpha22

thanks for the feedback 🙏🏻

I will add Clover support to the app later today and test it out.

 

The thing is I don't have Clover on my rigs so I can’t fully test it before releasing it so I’m gonna need your help.

[Anto65]

Here it is, I hope it helps.

 

2025-08-11_08-24_Clover.log.zip

 

However, clicking "mount" doesn't open the partition on the desktop like before. 😒 

[Cyberdevs]

@Anto65

Thanks. I’ll check it out when I get back. I’ll also check the open on mount as well.
 

[Alpha22]

@Cyberdevs 

 

Quote

The thing is I don't have Clover on my rigs so I can’t fully test it before releasing it so I’m gonna need your help.

okay

[ANTIKO]

12 hours ago, Anto65 said:

However, clicking "mount" doesn't open the partition on the desktop like before.

I have an opening

Spoiler