Windows
Copying to the S: drive failed until the file server was rebooted
Copying a file from the local Downloads folder to the S: drive was failing with an error. The file server hosting that share was rebooted, remote access was restored, and available memory resources were verified before the user was asked to retry the copy.
Killed once by someone from XL.net, on 2026-06-11.
What you see
- Copying a file from Downloads to the S: drive returns an error.
- The copy fails when targeting the shared S: drive.
Why it happens
Likely The server hosting the S: drive likely had a temporary resource issue that was cleared by a reboot.
When it shows up
A user can read from the PC but gets an error when copying to a shared S: drive on a remote file server.
You are in this case if:
- The destination is a shared S: drive on a server rather than a local disk.
- After the server is rebooted, remote access to it returns and available memory resources are normal.
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.
Someone from XL.net killed this on a Windows computer on 2026-06-11. It is written up from that one repair, so it cites no outside page.