Fix Universal Print Error 0x8086000c on Windows 11

Universal Print error 0x8086000c on Windows 11 stops jobs from reaching the cloud print queue, usually due to a stuck print job, a stale printer registration, or a network/authentication hiccup. The fix is to clear the print queue, re-register the printer, and verify your Azure AD and network connectivity—most users resolve it in under 10 minutes without reinstalling drivers.

What Is Universal Print and Why Does This Error Happen?

Universal Print is Microsoft’s cloud-based print service that replaces traditional on-premises print servers. Instead of installing vendor-specific drivers on every PC, you add a printer that exists in your Azure AD tenant, and jobs are routed through Microsoft’s cloud to a connector or a natively supported printer. Error 0x8086000c is a generic client-side failure that appears when Windows 11 cannot complete that cloud handoff.

Common triggers include:

• A print job stuck in the local spooler that never reaches the cloud.
• The printer object in Azure AD is out of sync with the local device.
• Network changes (VPN, Wi-Fi switch) that break the connection to Microsoft’s endpoints.
• Expired or invalid authentication tokens for the user’s Azure AD account.
• Outdated Windows 11 build or missing Universal Print client component.

Because the error is generic, the fix is a process of elimination rather than a single switch.

Before You Start: Check the Basics

Spend 30 seconds on these checks—they resolve a surprising number of cases:

1. Sign out and back into Windows (not just lock). This refreshes your Azure AD token.
2. Verify the printer shows as “Online” in Settings > Bluetooth & devices > Printers & scanners. If it shows “Paused” or “Offline,” click it and select “Resume printing” or “Use printer offline” to toggle it back.
3. Check the date and time are set to automatic. A skewed clock breaks the TLS handshake with Microsoft’s servers.
4. Test another cloud app (e.g., OneDrive) to confirm your Azure AD login is healthy.

If none of these help, move to the systematic fixes below.

Fix 1: Clear the Stuck Print Queue

A corrupted spooler file is the most frequent culprit. The error often appears after a job gets stuck mid-transfer. Here’s how to clear it safely:

1. Press Win + R, type services.msc, and press Enter.
2. Find Print Spooler, right-click it, and select Stop.
3. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS. Delete all files inside (they are just temporary job data).
4. Go back to Services, right-click Print Spooler, and select Start.
5. Try printing again.

If the queue won’t clear because a job is stuck, restart the spooler service again and immediately delete the files. If that fails, reboot into Safe Mode with Networking and repeat—this prevents any third-party print monitor from re-adding the job.

Fix 2: Re-register the Printer in Windows 11

Sometimes the local printer object is out of sync with the cloud. Removing and re-adding it forces a fresh registration:

1. Go to Settings > Bluetooth & devices > Printers & scanners.
2. Click the Universal Print printer, then select Remove device.
3. Click Add device and wait for Windows to find it. Universal Print printers appear under “Universal Print” in the list—select it and follow the prompts.
4. If it doesn’t appear, click The printer that I want isn’t listed, choose Add a Universal Print printer, and sign in if prompted.

This re-creates the local printer object and re-fetches the cloud configuration. After re-adding, set it as default and print a test page.

Fix 3: Verify Network and Endpoint Access

Universal Print requires access to specific Microsoft endpoints. A firewall, proxy, or VPN can block them, causing error 0x8086000c. The required URLs include:

• *.universalprint.microsoft.com
• *.print.microsoft.com
• login.microsoftonline.com (for authentication)

To test connectivity, open a browser and visit https://print.microsoft.com. If the page loads and shows your printers, the network path is fine. If it doesn’t, check your proxy settings or temporarily disable the VPN and try again.

Also, ensure your DNS resolves correctly. Flush the DNS cache by opening Command Prompt as administrator and running ipconfig /flushdns. Then restart the Universal Print Connector service if you’re using a connector-based printer (not a native cloud printer). The connector service is called Universal Print Connector in Services.msc—right-click and restart it.

Fix 4: Reset the Universal Print Client Component

If the above fails, the client component itself may be corrupted. Windows 11 includes a built-in troubleshooter for printers, but for Universal Print specifically, you can reset the client state:

1. Open Settings > Apps > Installed apps.
2. Search for Universal Print—you may see a component called “Universal Print Client” or similar.
3. Click the three-dot menu and choose Advanced options, then Reset. This clears cached data without removing the printer registration.
4. Restart your PC and re-add the printer if necessary.

If you don’t see a Universal Print app, run Windows Update to ensure you have the latest cumulative update, as Microsoft frequently ships fixes for cloud print issues.

Fix 5: Reinstall the Printer Driver (or Use the Native Driver)

Universal Print uses a generic driver, but some printers require a specific driver for advanced features. If the error persists, try switching to the built-in Microsoft Universal Print Class Driver:

1. Remove the printer as in Fix 2.
2. Re-add it, but when prompted, choose Add a local printer.
3. Select Microsoft as the manufacturer and Universal Print Class Driver as the driver.
4. Set the port to Universal Print (if listed) or leave it as the default.

This bypasses any vendor driver that might be interfering. If you need the vendor driver for features like duplex or color management, download the latest version from the manufacturer’s site and install it, then re-add the printer.

Frequently Asked Questions

Will this error fix itself after a reboot?

Sometimes. A reboot clears the spooler and refreshes tokens, so if the error is transient, it may disappear. But if the underlying cause is a corrupted printer registration or a blocked endpoint, it will come back. The fixes above target those root causes.

Is error 0x8086000c specific to a printer brand?

No. It’s a client-side error from the Universal Print service, so it can happen with any printer registered in Universal Print—HP, Brother, Ricoh, or a connector-based legacy printer. The fix is the same regardless of brand.

Do I need to be an administrator to fix this?

Yes for most steps. Stopping the Print Spooler service, deleting files in the spool folder, and resetting the Universal Print component require administrator rights. If you’re on a managed work device, you may need to contact your IT department for those steps.

Can I bypass Universal Print and use a regular network printer?

Yes, if your printer supports standard IPP or Wi-Fi Direct. You can add it as a local network printer instead of a Universal Print printer. However, you’ll lose the cloud benefits like access from any device and centralized management. If your organization mandates Universal Print, you should stick with it.

Why does the error appear only for one user account?

That usually points to an authentication issue. The user’s Azure AD token may be expired or the account lacks the Universal Print license. Have the user sign out of all Office apps, clear the Windows credential manager for Microsoft accounts, and sign back in. If it persists, check the user’s license assignment in the Azure portal.

Will reinstalling Windows fix it?

Almost never. The error is a cloud service issue, not a core OS corruption. Reinstalling Windows is a last resort and would likely not resolve it unless the local client component is severely damaged, which is rare. Stick to the targeted fixes first.

Related

• Old Phone Robot: Secure & Prep Guide
• iOS 18 Apps Crashing? Fixes That Work
• How to Set a Windows Service to Start Manually