I am posting this here, since it might help others with similar TCC permissions issues preventing apps from functioning.
I ran into a perplexing issue that was most likely TCC-related. My “Windows App,” formerly also known as "Microsoft Remote Desktop", could no longer connect to Windows instances on my LAN. There was no problem on all my other systems with this. I use it to connect to a couple of VMs occasionally running on my Intel-based Synology NASs.
To make several hours of misery short, this “error 104” was not solved by removing all Windows App Sandbox items and reinstalling from the App Store. It worked fine from another account on the system, so it had to be bound to my account. I even deleted the TCC database elements for the account. The problem stubbornly remained. Windows would show the request for Local Network access, but accepting it would never succeed. I concluded that it was some undocumented security structure tracking the networking that was corrupted.
My solution was this:
This probably also would have fixed my wallet, reported as disabled due to "changed security settings." I struggled with that several weeks ago and ended up doing a full recovery install and rebuild of the system.
I ran into a perplexing issue that was most likely TCC-related. My “Windows App,” formerly also known as "Microsoft Remote Desktop", could no longer connect to Windows instances on my LAN. There was no problem on all my other systems with this. I use it to connect to a couple of VMs occasionally running on my Intel-based Synology NASs.
To make several hours of misery short, this “error 104” was not solved by removing all Windows App Sandbox items and reinstalling from the App Store. It worked fine from another account on the system, so it had to be bound to my account. I even deleted the TCC database elements for the account. The problem stubbornly remained. Windows would show the request for Local Network access, but accepting it would never succeed. I concluded that it was some undocumented security structure tracking the networking that was corrupted.
My solution was this:
- Log my account out of Find My.
- Reboot the system, and log into another Admin account I have an every system for salvage reasons.
- Delete my Account, but keep the Home folder.
- The system renames that to username (Deleted). I rename it username.
- Its ownership UID is now an unknown 501, since I always create my account on a new system, and the numbering starts with 501
- I recreate my account username. It will reuse the UID 501.
- If you end up with a different UID for some reason, you will have to change ownership of the home folder with a zsh command:
Code:sudo chown -R username:staff /Users/username
This probably also would have fixed my wallet, reported as disabled due to "changed security settings." I struggled with that several weeks ago and ended up doing a full recovery install and rebuild of the system.
