Why Does Chrome Appear Multiple Times in Mac Privacy Settings?
After upgrading to macOS Sequoia, I noticed something strange: Google Chrome appeared multiple times under Privacy & Security → Local Network.
I wasn’t the only Mac user experiencing this. Others reported repeated permission prompts, duplicate Chrome entries, and an inability to connect to devices on their local networks.
Even uninstalling Chrome didn’t always remove the entries.
Here’s what I found about the problem, what the symptoms suggest, and which troubleshooting steps are worth considering before changing system-level security settings.
Why Does Chrome Appear Multiple Times in Local Network Settings?
macOS uses Local Network permissions to control whether apps can communicate with devices on your local network, such as routers, network-attached storage (NAS) devices, and local servers.
When an app first attempts to access the local network, macOS may ask you to allow or deny access. You can review the permission under System Settings → Privacy & Security → Local Network.
The problem is that some Mac users have reported seeing multiple entries for the same app, particularly Google Chrome, after upgrading to macOS Sequoia.
What users have reported
The symptoms aren’t limited to duplicate entries:
- Repeated permission prompts: Chrome asks for local network access more than once.
- Unresponsive permission switches: Turning Chrome’s access off and on doesn’t resolve the problem.
- Entries that remain after uninstalling: Removing Chrome doesn’t necessarily clear its old entries from the settings.
- Failed local connections: Chrome may be unable to access a router or another device on the local network when permission isn’t working correctly.
These symptoms suggest that the issue may involve how macOS identifies applications and manages Local Network permissions, rather than a problem with Chrome’s browsing functions alone.
However, duplicate entries don’t establish a single cause. Multiple installed versions of an app can also lead to unexpected permission behavior, and reinstalling Chrome won’t necessarily fix an underlying macOS permission-state problem.
How to Troubleshoot Duplicate Chrome Entries
Before attempting a fix, identify the actual problem.
If Chrome can access local devices normally and the only issue is duplicate entries, you may not need to make risky system changes. If Chrome repeatedly requests permission or cannot connect to local devices, troubleshooting the permission state becomes more relevant.
Fix 1: Reinstall Chrome and Reset Permissions
Some users have reported resolving duplicate Chrome entries by removing Chrome, resetting a system permission database, and reinstalling the browser.
The following procedure is a community-reported workaround, not a guaranteed or officially supported fix for Local Network permissions.
Step 1: Back up your Chrome data.
Before uninstalling Chrome, make sure your bookmarks, passwords, and other important browser data are backed up or synced. Don’t assume that every piece of local data will be recoverable after removal.
Step 2: Start your Mac in Safe Mode.
The startup procedure depends on whether your Mac uses Apple silicon or an Intel processor. Follow the appropriate procedure for your Mac.
Step 3: Remove Chrome.
Open Finder, go to Applications, and move Google Chrome to the Trash.
Step 4: Consider the permission-reset command carefully.
Get Jenny Zeng’s stories in your inbox
Join Medium for free to get updates from this writer.
A command that has appeared in community reports is:
sudo tccutil reset SystemPolicyNetworkVolumes
This command resets permissions associated with network volumes. It is not a documented, dedicated reset for the Local Network privacy permission, so don’t assume that running it will clear duplicate Chrome entries.
Step 5: Restart your Mac and reinstall Chrome.
If you proceed with a reinstall, download Chrome from Google’s official download page. Open Chrome and try accessing a device on your local network.
If macOS displays a Local Network permission prompt, review it and select Allow if you want Chrome to access those devices.
Finally, revisit System Settings → Privacy & Security → Local Network to see whether the duplicate entries remain.
If the problem persists, avoid repeatedly uninstalling and reinstalling Chrome without evidence that the process is helping.
Fix 2: Avoid Deleting System Preference Files Without a Verified Procedure
Another approach discussed by Mac users involves resetting macOS’s network-related preference files.
These files are protected by System Integrity Protection (SIP), a security feature that helps prevent unauthorized changes to critical system components.
Disabling SIP and deleting protected files is not a routine troubleshooting step. An incorrect command or an incomplete recovery procedure can create additional problems, and the process may not resolve the underlying issue.
For that reason, I wouldn’t recommend disabling SIP simply to remove duplicate Chrome entries unless you have a verified procedure for your exact macOS version and understand the risks.
If the permission entries are still duplicated or Chrome cannot reach local devices, consider checking for additional Chrome installations, installing the latest compatible macOS updates, and consulting Apple Support or an experienced Mac technician before attempting a system-level reset.
What If Chrome Still Can’t Access Your Local Network?
Duplicate entries and failed network connections can occur together, but they aren’t necessarily the same problem.
Start by checking whether the problem affects only Chrome or also affects Safari and other applications.
If other apps can access the same local device but Chrome cannot, focus on Chrome’s permission state and installation.
If multiple apps are affected, investigate the network connection and macOS configuration instead of assuming Chrome is responsible.
Also, distinguish between accessing a website on the public internet and connecting to a device on your private network. A browser may work normally for public websites while still having trouble reaching a local router or server.
This distinction helps narrow the investigation before you attempt more disruptive fixes.
What I Learned From Investigating This Issue
When a Mac setting shows the same app multiple times, it’s tempting to assume that deleting and reinstalling the app will solve the problem. But that approach may not address the system state responsible for the duplicate entries.
Here are three principles I would use when troubleshooting this issue.
1. Separate the visible symptom from the underlying problem.
Duplicate entries are a symptom, not proof of a particular cause. Determine whether the problem is cosmetic, affects permission prompts, or prevents local network access.
2. Verify what a Terminal command actually resets.
A command that resets one category of macOS permissions doesn’t necessarily reset another. Check the command’s documented purpose before running it, especially when it uses administrator privileges.
3. Escalate gradually.
Start with low-risk checks, such as verifying the installed Chrome version and determining whether other apps can access the same device. Back up important data before reinstalling software, and reserve protected system-file changes for situations where the procedure is verified and the risks are understood.
These principles apply beyond Chrome. Whenever a macOS privacy setting behaves unexpectedly, understanding which component manages the permission is more useful than trying unrelated reset commands.
