STATUS_ONLY_IF_CONNECTED (0XC00002CC) – Fix When Offline

I know this error is a pain – you're in the middle of something and Windows just shuts you down with a code that looks like a CD key. But let's fix it fast.

What triggers this error?

The 0XC00002CC error pops up when you try to do something that requires a live network connection, but you're not connected. Common triggers: opening a mapped network drive that's offline, running a backup to a network location, or using an app that checks license status online (like Microsoft Office or an enterprise tool). I see it most often on Windows 10 and 11 when a user switches from Wi-Fi to offline or when a VPN drops mid-session.

Fix #1: Reconnect or restart the network

Nine out of ten times, the fix is simple. Here's what to do, step by step:

1. Check your network icon in the system tray (bottom right). If it shows a red X or a globe with a yellow triangle, you're offline.
2. Right-click the network icon and select Network & Internet settings.
3. Click Advanced network settings (on Windows 11) or Change adapter options (Windows 10).
4. Find your active adapter (usually Wi-Fi or Ethernet). Right-click it and choose Disable. Wait 10 seconds.
5. Right-click it again and choose Enable. After you do this, you'll see the network icon reconnect within a few seconds – it should show full bars or a monitor icon.

After the adapter reconnects, try the operation that gave you the error again. If the error is gone, great. If not, move to the next fix.

Fix #2: Restart the Network List Service

Sometimes Windows thinks you're still disconnected even after you reconnect. The service that tracks that is the Network List Service. Here's how to restart it:

1. Press Win + R, type services.msc, and press Enter. A window full of services opens.
2. Scroll down to Network List Service. Look at its status column – it should say Running. If it does, right-click it and choose Restart. If it's stopped, right-click and choose Start.
3. While you're here, also check Network Location Awareness – same deal, restart it or start it.
4. Close the services window. Wait 30 seconds, then try your operation again.

Fix #3: Map drives differently (the real fix for persistent issues)

If you get this error trying to access a mapped network drive, the problem is that Windows cached the drive mapping when you were connected, but now it's stale. The real fix is to change how you connect. Don't use a drive letter mapping for occasional access. Instead:

1. Open File Explorer. In the address bar, type the full network path directly, like \\ServerName\ShareName.
2. Press Enter. Windows will prompt for credentials if needed. Enter them.
3. If it connects, you're good. If it still throws 0XC00002CC, the server is actually down or unreachable – check that separately.

Why does this work? Because a direct UNC path doesn't rely on Windows' offline caching. The mapped drive letter tries to reconnect automatically and fails, while a direct path checks the connection fresh each time.

Fix #4: Disable offline files (if enabled)

Some environments enable Offline Files for network shares. This can cause conflicts. Here's how to turn it off temporarily to test:

1. Open Control Panel. Search for Sync Center and open it.
2. On the left, click Manage offline files.
3. Click Disable offline files. You'll need to restart your computer.
4. After restart, try your operation.

If this fixes it, you have a conflict with the offline cache. You can re-enable it later if you need it, but I'd recommend keeping it off unless your IT policy requires it – it causes more problems than it solves.

Why this error happens (the short version)

Windows returns STATUS_ONLY_IF_CONNECTED when an application calls a function that requires an active network session. It's not a bug – it's a safeguard. The system checks if you have a connection to the target server (not just the internet) and if the target server responds. If either check fails, you get this error. The fixes above handle the most common reasons for that check failing: bad adapter state, stale service, or incorrect path.

Less common variations

Sometimes this error shows up with different wording but the same code. You might see:

• "Operation requires a connection to the server" – same 0XC00002CC. This usually comes from a custom app or a tool like Robocopy when the target is a network share that's been taken offline.
• "The requested operation requires a connection to the domain" – you see this when a domain-joined PC tries to access a resource but can't reach the domain controller. Fix: reconnect to VPN or check your DNS settings. Run ipconfig /flushdns in an admin command prompt, then nltest /dsgetdc:yourdomain.com to verify domain connectivity.
• Error in Event Viewer with source "Microsoft-Windows-Security-SPP" – this happens when Windows tries to validate a license online. If you're offline, it fails. Temporarily disable the network adapter, then re-enable it after you've moved to a connected location.

How to prevent this from coming back

Prevention is easier than you think. Here's what I tell my techs:

1. Don't map drives you only use occasionally. Use direct UNC paths in shortcuts or batch files. This avoids the stale mapping problem entirely.
2. Set your network adapter to not automatically disconnect when idle. In advanced power settings, set both Wi-Fi and Ethernet to never turn off to save power. I've seen this cause the adapter to drop and then fail to reconnect properly.
3. If you use a VPN, connect it before you try to access anything. Some apps check the connection first – if the VPN isn't up, they throw this error immediately. Run the VPN client, wait for the connection confirmation, then open your app.
4. Keep Windows updated. Microsoft has fixed some underlying service bugs in cumulative updates for Windows 10 22H2 and Windows 11 23H2. Run Windows Update and install all quality updates.

That's it. You should be back up and running. If you've tried all these and still see 0XC00002CC, then your problem is likely on the server side – the target server is down, unreachable, or has a firewall blocking you. Check with your network admin.