Fix FFS networking after upgrade MacOS

It sounds like the macOS Tahoe update has “orphaned” your FreeFileSync (FFS) permissions. This is a relatively common occurrence during major OS jumps where the TCC (Transparency, Consent, and Control) database doesn’t properly migrate an app’s specific entitlements, even if Full Disk Access remains checked. Since FFS is missing entirely from the Local Network list, macOS isn’t triggering the request for permission, effectively “silently failing” when you try to run your routines. Why this happens When you upgrade macOS, the system sometimes loses the link between the app’s binary signature and its entry in the Privacy database. Because FFS is no longer “requesting” the permission (it thinks it already has it, or the OS is blocking the prompt), it won’t appear in the Local Network settings toggle. How to Fix It

1. The “Trigger” Method The easiest way to fix this is to force macOS to realize FFS needs local network access again.

• Open FreeFileSync.
• Try to create a new folder comparison targeting a networked drive using its IP address (e.g., smb://192.168.1.50).
• Watch for the native macOS pop-up asking: “FreeFileSync would like to find and connect to devices on your local network.” Click Allow.

2. Reset the TCC Database via Terminal If the pop-up doesn’t appear, you can manually reset the Local Network permissions for FFS using the Terminal. This clears the “stale” entry and forces a fresh request.

• Close FreeFileSync.
• Open Terminal (found in Applications > Utilities).
• Copy and paste the following command and hit Enter: tccutil reset LocalNetwork net.freefilesync.FreeFileSync
• Restart FreeFileSync and attempt a sync. The permission prompt should now appear.

3. The “Drag and Drop” Manual Add If the toggle still isn’t showing up in Settings -> Privacy & Security -> Local Network:

• Open the Local Network settings window.
• Open your Applications folder in Finder.
• Try dragging the FreeFileSync app icon directly into the list on the Settings window. (Note: This works on some versions of macOS Tahoe, but not all, depending on the app’s signing). A Quick Note on Full Disk Access Since you mentioned Full Disk Access is still enabled, it is worth toggling it Off and then On again. Sometimes the “Checked” status is a UI ghost, and toggling it refreshes the actual system permissions for the new OS version. Would you like me to walk you through the Terminal steps for checking if there are any other underlying permission errors in your system logs?