OM Workspace + Sonoma update help

[Triskele]

Hi everyone, asking for your help here with the OM Workspace not working after I updated my Mac to Sonoma (MacBook Pro 16", 2023 Chip Apple M2 Pro macOS Sonoma 14.6.1).

After the update, it keeps asking for the extension to be enabled:

System Extension Blocked

A program tried to load new system extension(s) signed by "OM Digital Solutions Corporation". You can enable these extensions in Privacy & Security

System Settings.

I have already tried to follow these steps but with no luck.

I have the same problem with Paragon NTFS but I managed to solve it following step 4 here and command

If you receive an error, or the problem persists, please try to reset pending KEXT library. To do so,you need to know the Volume Name of your macOS Volume. It can be checked using this command:

diskutil apfs list

check the Name of the volume with the System Role (for instance, Macintosh HD).

Boot into Recovery Mode

Execute the following command in Terminal:

kmutil trigger-panic-medic -R “/Volumes/SystemVolumeName“

where SystemVolumeName is the volume with the system role from “diskutil apfs list” command

(for instance

kmutil trigger-panic-medic -R “/Volumes/Macintosh HD”)

Reboot as usual, then check if it’s now possible to Allow our extension.

However, after allowing Paragon the problem is still there with the OM Workspace asking to be enable.

At this point I tried to uninstall OM Workspace manually deleting also all the possible leftovers + also trying Cleanmymac X but the problem is still there, OM Workspace is still listed under system settings -> privacy & security.



Also, I don't have any "allow" option, just the "details" one. If I select it it shows the screenshot here above but the toggles don't work.

To be able to see the allow option I need to go back into recovery mode and command kmutil trigger-panic-medic -R “/Volumes/SystemVolumeName“. After that, I can see the allow button but allowing everything doesn't work, after restarting the Mac I am just left in the situation as shown in the screenshot here above (OM asking to be enabled, no allow option, no toggles).

I also tried to disable SIP but again no luck as I get the error:

-bash-3.2# csrutil disable Turning Systen Integrity Protection requires modifying system security. Allow booting unsigned operating systems and any kernel extensions for 0s "Macintosh HD? [y/n]:y
Enter password for user: *****
Icsrutil: Failed to update security configuration for "Macintosh Failed to create paired recovery local polícy -bash-3.28

Trying csrutil clear it says

-bash-3.2# csrutil clear
Enter password for user *****
csrutil: failed to clear system integrity configuration: Failed to create paired recovery local policy
-bash-3.2#

Is there a way of getting rid of the OM completely and/or solve this problem? Only option I am left with at this point is formatting the Mac but I'd like to avoid that if possible.

Thank you!

 

[Danielvr]

The more popular forum section for M43 cameras and software is Micro Four Thirds Talk, so if you don't find a solution here in Olympus SLR, you could still give it a try there.

Earlier this year, someone else reported Workspace-related problems on Mac/OS Sonoma. His problems were different, but I thought that some of the proposed solutions might still be helpful to you, so I'll give you the link anyway:

Help with saving/loading custom settings from/to my Mac

 

[bmoag]

Its unusual for macOS. Windows too, not to preserve apps in an OS upgrade, the same cannot be said for drivers in macOS.

It does not help you to know that when I upgraded, if its an upgrade, to Sonoma OM Workspace was preserved. I updated it in Sonoma without problems.

It also does not help you to know that I didn't encounter problems installing Paragon on Sonoma, both suggest there's an issue with the way your particular installation of macOS is configured.

If you manually hunted down and deleted every file that referenced OM or Olympus you could have compounded the problem given the way APFS and Apple security works, or doesn't work. You likely also missed something.

Windows users blame Microsoft for their idiosyncratic problems, mac users blame themselves.

What I would suggest, assuming you have Time Machine and a lot of spare time and that you can identify in Time Machine a Ventura backup prior to the Sonoma installation:

Reinstall Sonoma (or go back to Ventura) and restore from Time Machine to see if that fixes the problem. You might want to do a TM backup of whatever dysfunctional installation you have before you do that, just in case, but to a different drive than you used previously. If you can wade through the command line interface of macOS you can figure out how to reinstall the OS.

Or just forget about OM Workspace. I keep looking for reasons to use it.