Fix 0XC00D1055: Printer or media sink already exists in stream

What's actually happening here

Error 0XC00D1055 with the symbolic name NS_E_WMG_SINKALREADYEXISTS means Windows Media Foundation (MF) refused to insert a renderer into a stream because one's already there. You'll see this mostly in printer software, media players that talk to printers (like HP or Canon photo apps), or any app that tries to output to a device using MF's media sink pipeline.

Think of it this way: MF streams are one-renderer-per-stream. If the printer driver or app already registered a media sink (a renderer that turns data into output), trying to add a second one trips this error. The culprit is almost always a stuck reference in the driver or the app not cleaning up its previous sink.

Cause 1: Stale printer driver media sink (most common)

Printer drivers—especially those from Canon, HP, and Brother for photo printing—register themselves as a media sink with MF. If a previous print job crashed or the app closed without releasing the sink, the system thinks the sink is still alive. Next time you try to print, the app tries to add the same sink again, and MF says "no, one's already there."

Fix: Restart the print spooler and clear the sink

1. Open Services.msc (Win+R, type services.msc).
2. Find Print Spooler. Right-click, select Stop.
3. In File Explorer, go to C:\Windows\System32\spool\PRINTERS and delete everything inside. These are stuck print jobs.
4. Back in Services, right-click Print Spooler and select Start.
5. Reboot your PC. This clears any orphaned media sink references from the driver.

Why step 3 works: The PRINTERS folder holds pending print jobs that might hold a reference to the driver's media sink. Deleting them breaks that reference. The spooler restart actually reinitializes the sink registration. Without the reboot, some drivers cache the old sink ID.

Cause 2: App misbehaving — not releasing the previous sink

Some apps (I've seen this with HP Smart, Canon My Image Garden, and certain PDF-to-printer utilities) create a media sink once and never call IMFMediaSink::Shutdown() when you cancel a job or switch printers. If you open the app, print something, cancel it, then try to print again—boom, 0XC00D1055.

Fix: Force the app to release the sink

1. Close the app entirely. Don't just minimize it — kill it via Task Manager (Ctrl+Shift+Esc, find the process, End Task).
2. Open Command Prompt as admin. Run:

net stop wmpnetworksvc
net stop mfplat
net start mfplat
net start wmpnetworksvc

This stops and restarts the Media Foundation platform service and the Windows Media Player Network Sharing Service (which also hosts media sinks). Doing this forces all active sink handles to close.

Then re-launch the app and try your print job again. If that doesn't work, uninstall and reinstall the app — some store apps from HP and Canon have a habit of leaking sink references across sessions.

Cause 3: Corrupt or incompatible printer driver

This one's rarer but nasty. A driver that doesn't follow Media Foundation's rules — like one that registers a sink with a wrong stream ID or fails to unregister on uninstall — can leave a phantom sink that blocks all future use. You'll see this after a driver update from Windows Update that didn't work right, or after swapping printer models without fully removing the old driver.

Fix: Remove and reinstall the driver cleanly

1. Open Devices and Printers. Right-click your printer, select Remove device.
2. Go to Settings > Bluetooth & devices > Printers & scanners. Click your printer, then Remove.
3. Open Command Prompt as admin. Run:

pnputil /enum-drivers

Find the driver that matches your printer (look at the "Class" column for "Printers"). Note the Published Name (e.g., oem64.inf). Then remove it:

pnputil /delete-driver oem64.inf /force

Replace oem64.inf with the actual file name. /force is key — it nukes the driver even if something has a handle open.

Reboot. Then download the latest driver from your printer manufacturer's site (not Windows Update) and install it fresh. Don't use the "Add a printer" wizard — run the manufacturer's installer.

Quick-reference summary table

If none of these work, check if your printer's manufacturer has a firmware update. Some HP and Canon models had known MF sink bugs that were fixed in firmware revs after 2021. And don't bother with registry hacks or disabling Media Foundation — that breaks too many other things. The fix is always about releasing that stuck sink.