Another day, another (personal?) problem. Context menus. The Cut/Copy commands displayed on the Context menus one time and then disappeared. I’m going to uninstall and reinstall and see if that clears the problem. Right now, the Context menu is about 1/3 normal size with the Copy command at the very bottom and no resemblance to the TF menu at all (or for that matter, the standard MacOS menu either).
1 Like
@Ken This is a known issue with macOS 13. The “Cut/Copy/Paste” buttons that TotalFinder adds to the right-click context menu will not work correctly until TotalFinder is properly updated for macOS 13.
Thanks for letting me know. I was getting ready to uninstall and reinstall (nice thing about testing, nobody gets upset when you blow everything away and start over). I’m looking forward to the updated version when it arrives.
-ken
1 Like
Hi @akemin_dayo thanks for everything you are doing, we and binaryage guys are really lucky to have you.
I’m using the first public beta of MacOS 13 on a mbp14, I followed any suggestion you wrote in this thread (and I was using TF on BigSur without any problem) but anything I can see is a window with a “read only” contextual menu and noone TotalFinder feature working… I know you are still working on Ventura but I can’t figure out why somebody can run it but not myself.
I disabled debug, sf and nvram (tested with status), tried sudo nvram boot-args="-arm64e_preview_abi" also the suggestion here, and I see TF in privacy/automation. I can open TF preferences but disabling any setting helps, enabling color labels causes a crash and I can only solve it disabling color labels from terminal.
1 Like
Hi All, the updated TotalFinder has been working perfectly for me on Monterey 12.4 on my 16" M1 thanks to @akemin_dayo. Apple now wants me to update to 12.5. Has anyone had any experiences with 12.5? I’m nervous about updating. I don’t want to lose my Colorful SideBar!!!
thanks…for any feedback in advance
1 Like
Is there a way to submit a crash report when TotalFinder crashes or causes the Finder to crash?
1 Like
@Sames TotalFinder 1.14.2 works with macOS 12.5 (21G72)!
I do try to test TotalFinder with each developer seed beta version of macOS released by Apple on a test machine I have just to see if there were any breaking changes. (There generally aren’t any changes like that made this late towards the end of a macOS version’s lifecycle, though.)
One thing of note that I noticed during my macOS 12.5 testing cycle is that… Apple actually accidentally broke AppleScript as a whole in one specific beta version of macOS 12.5 — specifically developer seed beta 5 21G5063a.
This caused… many things, including TotalFinder, to stop working completely. It also made me question my sanity for a good while trying to understand the bizarre error I was suddenly getting (since 12.5b1〜12.5b4 all worked perfectly), until I realised that AppleScript as a whole was broken. ;P Luckily for everyone, Apple did promptly fix that issue in the very next developer build.
@strafer If you run the included TotalFinder diagnostics script at /Applications/TotalFinder.app/Contents/Resources/diagnose-totalfinder.sh in a Terminal session, it will generate a totalfinder-diagnostics.tar.gz file on your Desktop that includes (among other things) any recent Finder crash logs that you can send to me via email.
It would be helpful if you could give a description of what you were doing (or trying to do) before Finder crashed, too.
@eBara TotalFinder 1.14.2 has known compatibility issues with macOS 13, including the crashing when enabling coloured labels (due to Apple renaming some classes as they… often do).
The only suggestion I really have regarding your “no TotalFinder features are working” issue is to completely reset your TotalFinder preferences.
You can do this by opening the TotalFinder preferences, going to About, and clicking on the “Reset TotalFinder to defaults” button.
Regarding the -arm64e_preview_abi boot-arg: I think I know why it suddenly became required as of macOS 13 — I should be able to address that in future TotalFinder versions, if all goes well.
1 Like
Thank you Karen, i tried it but it still not working, neither cmd+x (for me, the most important feature… Is it possible to detach this feature from TF and make an independent app that does only this? 
). The app opens and runs, no problem entering the preferences, but no feature seems to work. Pretty unlucky 
Hi, no problems here with 12.5 and M1 Mini. The colourful sidebar is my main concern, too.
thanks for the info,i have buy the pro version and its amazing
I’m having trouble with TF (mac mini1), os Ventura latest beta Version 13.0 Beta (22A5331f), csrutil is disabled, also I have run the commandsudo nvram boot-args=“-arm64e_preview_abi”, totalFinder run once , crashed and when the computer restarted I got the following warnings “System events” added items that can run in the background, and also “Antonin Hildebrand” added items that can run in the background.
My post I deleted above had irrelevant information. I was unable to edit, so I deleted. It simply stated the last version of TF (1.12.3) that would run AFTER doing OCLP post-install root patch.
With that said, I can confirm 100% that the Post-Install root patch is what breaks TF for my machine.
MacBookPro6,2 - macOS 12.6 (21G115) - OCLP 0.4.11.
Reverting root patch, reboot, TF works. I don’t know what in these 3 available patches would mess something like that up?
After root patch:
Installing 1.12.3 post root patch I get this alert, no version since will show this post root patch.
Any more info needed, let me know. Thank You.
@ChrisOSX I’ll set up an OpenCore test machine and see if I can reproduce this issue. Thank you for the detailed information and testing — it’s very helpful and lets me know what to look for in OCLP!
@eBara @oscaro The only thing I can really say at this point is that TotalFinder 1.14.2 (as well as the upcoming 1.14.3 that I’ll release to fix a new compatibility issue with macOS 11.6.8 Big Sur) just doesn’t have proper macOS 13 support yet. It’ll take some time for support to be properly added.
(※ Also, the notification you’re receiving about software written by “Antonin Hildebrand” being added to your system is intentional — TotalFinder is codesigned, notarised, and published by Antonin of BinaryAge. Apple is simply notifying you of that fact.)
1 Like
Sounds good 
The crash report for Finder in Console has been the same termination reason:
- Termination Reason: Namespace DYLD, Code 4 Symbol missing
If you need any more info let me know.
1 Like
Thanks for your reply. I use native tabs in addition to the TF tabs for greater flexibility when moving files around in dual mode.
1 Like
@JB76 Ah, I see.
I assume you’re using the right-click → Open in New Tab button to open a directory in a native tab?
(※ This is actually technically a bug, since TotalFinder is ideally supposed to hook all calls for creating a new tab and replace it with a TotalFinder tab…)
Following this.
Is there a working step-by-step tutorial on getting this to work on Ventura OS?
1 Like
@Ronald_Epstein Not at this time, no.
TotalFinder is not yet compatible with macOS 13 Ventura.
2 Likes
And yet it’s working (minus cut in paste) on my M1 MacBook Pro Max.
Hi thanks again for your awesome work to keep TotalFinder working on M1 macs. I’m not sure if anyone has reported this but it seems that if you have your System Preferences->General->Appearance set to auto, when it switches to night time mode (or I’m assuming daytime mode) it kills TotalFinder. I’m curious to know if this is something that can be addressed or not.
Thanks!