Windows
P: share was unavailable until the hosting VM was started
The shared P: drive could not be reached remotely or on site. The technician identified the virtual machine hosting that share, started it, and remapped P: so the files were accessible again.
Killed once by someone from XL.net, on 2026-10-21.
Affects
Apps
- Hyper-V
What you see
- P: drive would not connect remotely or on site
- Shared files on the public drive were unavailable
Why it happens
Likely Likely the virtual machine hosting the P: share was not running when access was attempted.
When it shows up
A shared P: drive is hosted inside Hyper-V and users cannot map it.
You are in this case if:
- Hyper-V Manager shows the file-server virtual machine is not running.
- The share becomes available after the virtual machine is started.
1 fix below
The steps that killed it
The steps are behind a quick check
There are two ways in and both take a few seconds. Signing in opens the steps on every bug page; so does reading the picture.
Or answer this
Drawing a picture for you.
Can't read it? Sign in instead.
Keeping it away
- Keep the virtual machine that hosts the shared drive running before users need access.
Someone from XL.net killed this on a Windows computer on 2026-10-21. It is written up from that one repair, so it cites no outside page.