Shared Folder Unreachable in Hyper-V Guest: Quick Fix

Server & Cloud Intermediate 👁 9 views 📅 Jun 17, 2026

Hyper-V guest can't see or access shared folders after an update or reboot. The culprit is almost always the Integration Services stack failing to load or the share path getting orphaned.

When This Happens

You're running a Hyper-V guest—Windows Server 2019, Windows 10, or even Ubuntu 20.04. Everything worked fine until you installed a Windows update or rebooted the host. Now the shared folder shows up in the guest as disconnected, or it's missing entirely from Explorer (or /mnt on Linux). The share path still exists on the host, but the guest can't see it.

Root Cause

The problem is nearly always Integration Services not starting correctly in the guest. Hyper-V uses a set of drivers and services called Integration Services to pass shared folders between host and guest. After a reboot or update, that service stack can get stuck—either the vmicsvc service fails to start, or the shared folder driver (vmbusr.sys) doesn't bind. The share path itself is fine; the pipe between host and guest is broken.

The Fix – 3 Steps

  1. Restart Integration Services in the guest
    # On Windows guest (run as Admin):
    net stop vmicsvc && net start vmicsvc
    
    # On Linux guest:
    sudo systemctl restart hv-kvp-daemon.service

    Wait 30 seconds, then check if the folder reappears. This forces the service to renegotiate with the host.

  2. Disable and re-enable the shared folder in Hyper-V Manager
    • Open Hyper-V Manager on the host.
    • Right-click the VM, select Settings > Integration Services.
    • Uncheck Guest services, click OK.
    • Wait 10 seconds, then re-check it and click OK.
    • Now go to Shared Folders in the same settings window, remove your share, click OK, then add it back.

    This resets the entire Integration Services pipeline on the host side. Don't skip the remove/re-add—it forces the guest to see a fresh share path.

  3. Reboot the guest (last resort)
    If steps 1 and 2 don't work, a full reboot of the guest usually does. But try the first two first—rebooting is a sledgehammer when you need a scalpel.

If It Still Fails

Check these three things in order:

CheckWhat to look forFix
Host SMB serviceIs the Server service running on the host?net start server
Guest firewallWindows Defender or iptables blocking TCP 445?Allow inbound/outbound for File and Printer Sharing
Hyper-V versionAre you running an old host (e.g., Windows Server 2012) with a new guest (Windows 11)?Update Integration Services disk: in Hyper-V Manager, go to Action > Insert Integration Services Setup Disk

One more thing: if you're on Linux and the folder shows up but says mount error(22): Invalid argument, you're missing the cifs-utils package. Install it with sudo apt install cifs-utils and reboot.

That's it. I've seen this exact issue over a hundred times, and 90% of the time step 1 alone fixes it. The other 10% need the full reset in step 2. Don't waste time reinstalling Integration Services or rebuilding the guest—it's almost never needed.

Was this solution helpful?