Fix 0X000004B1: Device not connected but saved

This error pops up on Windows when a network drive or printer is saved but the device is gone or unreachable. The fix is straightforward: remove the stale entry or fix the connection.

When you see this error

You're on Windows 10 or 11, and you try to open a mapped network drive or a shared printer. Instead of the folder or print queue, you get a pop-up with ERROR_CONNECTION_UNAVAIL (0X000004B1) and a message that says "The device is not currently connected but it is a remembered connection."

Real talk: I see this most often after someone moves a NAS to a different subnet, changes a workgroup, or reboots a router that gave temporary IPs to shared folders. One client last month had an old mapped drive pointing to an office PC that had been replaced. Every time they clicked it, Windows tried to reach a machine that didn't exist anymore.

What's actually happening

Windows keeps a list of mapped network drives and shared printers in the registry. When you map a drive with the "Reconnect at sign-in" box checked, Windows stores a reference to that device. But if the device goes offline, changes its name, or gets a new IP, Windows can't reconnect. Instead of showing an empty folder, it throws this error.

The root cause is almost always a stale mapping. The fix is to remove that mapping and re-create it fresh.

The fix – remove the stale mapping

Open File Explorer. Press Win + E on your keyboard.
Go to This PC. In the left sidebar, click This PC (or Computer on older Windows).
Find the bad drive. Under Network locations, you'll see the drive that's giving the error. It usually has a red X or a disconnected icon.
Right-click it and choose Disconnect. Confirm if it asks. That kills the saved mapping.
Re-map the drive. Click the Map network drive button in the toolbar. Pick a drive letter, type the correct share path (like \server\share), and make sure Reconnect at sign-in is checked. Click Finish.

If the drive letter is still in use, Windows will tell you. Pick a different letter or disconnect the old one first.

Alternative – use command prompt

If File Explorer is being stubborn or you can't even see the drive, open a command prompt as admin and run:

net use * /delete

That removes all network drive mappings. Then re-add the one you need with:

net use Z: \\server\share /persistent:yes

Replace Z: with the drive letter you want and \\server\share with the real path.

If it's a printer

For shared printers, the error shows up in Devices and Printers. Open Control Panel > Devices and Printers. Right-click the printer with the error, choose Remove device, then add it again from Add a printer > Add a network, wireless or Bluetooth printer.

Still failing? Check these

Is the device actually online? Ping it from a command prompt: ping server-name. If you get no reply, the device is down or the network is blocked.
Firewall or antivirus can block SMB traffic. Temporarily disable Windows Defender Firewall or the third-party one to test.
Workgroup or domain mismatch – both machines need to be in the same workgroup (or joined to the same domain). Check in System Properties > Computer Name tab.
Credentials – if the shared folder requires a username and password, make sure you saved the correct ones. Use Credential Manager (search for it in Start) to edit or remove saved credentials for the target device.
Turn off IPv6 if you're on a pure IPv4 network. I've had cases where Windows tried to reach a device over IPv6 and failed. Uncheck IPv6 in the network adapter properties.

One last thing: if you're on a domain-joined machine and the error won't go away, check with your IT team. Group Policy can force certain drive mappings that override your local ones. They might need to fix the policy or remove the mapping on their end.

Bottom line: 90% of the time, it's a dead mapping. Disconnect and reconnect. Done.