Parallels Shared Network Dead After Update? Here's the Fix

It's the Same Old Culprit

You updated Parallels Desktop or macOS, and now your VM can't reach the internet. Shared network is dead. Guest pings nothing. Host sees it but no traffic flows. I've seen this after every major macOS release since Big Sur. Had a client last month who spent two hours with Parallels support before I fixed it in five minutes. Here's the exact fix.

The Fix: Reset the Network Adapter

1. Shut down the VM completely. Not suspend, not save state. Full shutdown.
2. Open Parallels Desktop, go to Control Center.
3. Right-click the VM, choose Configure.
4. Go to Hardware tab, then Network.
5. You'll see the adapter there. Click the minus button (–) to remove it.
6. Click Add (+), select Network, choose Shared Network.
7. Start the VM.

That usually restores connectivity within ten seconds. But don't stop there—the network stack is still dirty until you reinstall the guest tools.

Why This Works

Parallels updates often push a new version of the virtual network adapter driver. But the upgrade process sometimes leaves the old driver config in place. That mismatch kills DHCP and routing. Removing the adapter forces Parallels to rebuild its virtual switch and DHCP server for that VM. Adding it back with Shared Network re-initializes everything clean.

The real problem is that Parallels doesn't always reinstall the guest tools after a host update. And the guest tools include the networking component. So you end up with a host-side driver mismatch and a guest-side driver that's stale.

Reinstall Parallels Tools (Do This Every Time)

After the reset above, do this while the VM is running:

1. From the Parallels menu bar, click Actions > Install Parallels Tools.
2. If it says already installed, choose Reinstall.
3. Follow the guest OS prompts. For Windows VMs, it'll autorun. For Linux, mount the ISO and run sudo ./install.
4. Reboot the VM after it finishes.

This pushes the current network driver for the guest, matching the host-side version. I've never had a shared network failure after this sequence that wasn't caused by something else like a firewall rule.

Less Common Variations

Bridge Mode Also Broken

If Shared Network works but Bridge Mode doesn't, it's usually a permission issue on macOS. Go to System Settings > Privacy & Security > Network and make sure Parallels has access. You may need to remove and re-add the network service.

DHCP Lease Stuck

Sometimes the VM gets an IP from the Parallels DHCP server but can't route. Open Terminal on the host and run:

sudo launchctl unload /Library/LaunchDaemons/com.parallels.desktop.plist
sudo launchctl load /Library/LaunchDaemons/com.parallels.desktop.plist

That restarts the Parallels networking daemon. Wait 30 seconds, then restart the VM.

Firewall or VPN Conflicts

If you use Little Snitch, Little Flocker, or a corporate VPN, they can block the prl_dhcp and prl_naptd processes. Check your firewall logs. Temporary disable the firewall, test, then re-enable with rules to allow these processes.

Old Network Preference in macOS

macOS Sonoma and Ventura sometimes corrupt the network preference list after a Parallels update. Go to /Library/Preferences/SystemConfiguration/ and delete NetworkInterfaces.plist. Restart your Mac. Parallels will rebuild it. I've done this twice this year for clients running Sonoma 14.4.

Prevention for Next Time

Don't just hit Update and hope. Before you run a Parallels update—or a major macOS update:

• Take a snapshot of each VM.
• Update Parallels first. Reboot the Mac.
• Then update macOS. Reboot again.
• Reinstall Parallels Tools in every VM.

That order matters. Updating macOS first can break the Parallels network extension before it gets a chance to update. Doing Tools last ensures the guest driver matches the new host version.

And if you're on an Intel Mac, also reset the NVRAM/PRAM after the macOS update. Helps clear any leftover network state from the previous boot.

Bottom line: Shared network dying after an update is almost always a driver mismatch between host and guest. Reset the virtual adapter, reinstall Tools, and you're back online in five minutes.