This setting is permanent from the System's perspective, so this is a bug with Google Chrome. You're probably right that the auto-update process is causing problems.
You can try completely uninstalling Chrome and installing it, since that might fix some installation issue that was causing this to manifest.
Alright, here’s what I ended up doing, which does work and doesn’t require any other installations. I tried the answer from Gilby, but wasn’t able to get fdautil to work after downloading and installing it via the LaunchControl trial version.
If it had worked, it seems it would have done so by granting LaunchControl’s fdautil utility full disk access, which ...
The program you want to run is bash, so the program arguments should be:
But I suspect that you may still get sandbox errors. To avoid this use the ...
macOS App Sandbox
~/Library/Containers is created by macOS and not the application. Sandboxed applications are effectively chroot'd into their container. You can learn more in Apple's App Sandbox Design Guide documentation.
Sandboxed applications have a com.apple.security.app-sandbox entitlement set to true.
You can view the entitlements of an application ...
I have gone through many solutions and this one is the best. Let me tell you that this also does not help to delete the files but makes life easy.
By giving the 'Full Disk Access' to terminal you can actually go inside with 'cd' and see the content and even by giving '777' permission to all the content there you can move everything outside '.Trash' in some ...
The setuid bit could be set on an executable.
When the setuid or setgid attributes are set on an executable file, then any users able to execute the file will automatically execute the file with the privileges of the file's owner (commonly root)
If setuid is applied and the binary is owned by root (and on macOS the ...
Why everyone here sticks to those cumbersome dscl and dscacheutil commands?
Why not use the much simpler id command (and its even simpler group friend command) ?
id - Gn <user>
will give you what you want for any Mac user, including those 50x "normal" Mac users.
> id -Gn 501 staff everyone localaccounts
_appserverusr admin ...
As you have discovered Time Machine and the system migration scripts handle all the little corners where files are customized per unique account or tied into a system file or just not to be backed up. I would probably rsync back the files into a new short name for which no user exists on the system.
Then take advantage of the system to fix permissions by ...