“Operation could not be completed (error 0x00000709)” Windows 11 Default Printer Fix

When Windows refuses to set your default printer and shows the operation could not be completed error 0x00000709, the printer itself is usually fine. Windows is failing to write the default printer setting, often after a cumulative update changed how that setting is stored.

Error snapshot
Exact error code	0x00000709 (0x709)
Error message	Operation could not be completed (error 0x00000709). Double check the printer name and make sure that the printer is connected to the network.
Applies to	Windows 11 and Windows 10, shared and network printers
Environment	Settings and Control Panel, after certain cumulative updates
Severity level	Medium printer works locally but cannot be set as default
Quickest fix	Run the Printer troubleshooter, then set LegacyDefaultPrinterMode to 1 in the registry.

What the error actually means

Error 0x00000709 appears when you try to make a printer the default, or when an app tries to print to a printer Windows can no longer mark as default. Microsoft changed default printer handling in newer builds, and on some machines that change leaves the old setting half written.

Because the message mentions the printer name and the network, people often reinstall drivers and chase the printer for hours. In most cases the printer is reachable. The block is the default printer registry entry.

Before you start

Step by step fixes

Try the troubleshooter and the registry value first. The later steps cover the cases where a bad update is the cause.

#	Step
1	Run the Printer troubleshooter. Go to Settings, System, Troubleshoot, Other troubleshooters, and run Printer. It can reset the default printer handling without any manual edits.
2	Let Windows manage the default. In Settings, Bluetooth and devices, Printers and scanners, turn on Let Windows manage my default printer, then turn it off and pick your printer manually. This rewrites the setting cleanly.
3	Set the registry value. Open Registry Editor, go to HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows, and set LegacyDefaultPrinterMode to 1. Create it as a DWORD if it does not exist.
4	Restart the Print Spooler. Open Services, find Print Spooler, right click and Restart. This reloads the printing subsystem with the new setting.
5	Set the default again. Reopen Printers and scanners, select your printer, and choose Set as default. With the legacy mode on, the assignment now holds.
6	Uninstall a recent bad update. If the error started right after an update, go to Windows Update, Update history, Uninstall updates, and remove the most recent cumulative update, then reboot and retest.
7	Recreate the printer. As a last resort remove the printer, restart, and add it again by IP or share path so Windows writes a fresh entry.

The technical context (the why)

Windows stores which printer is the default in the registry, per user, under the Windows NT key. The LegacyDefaultPrinterMode value tells Windows whether to use the older, manual default printer behaviour or the newer automatic one that picks the last printer you used.

When an update toggles that behaviour, the manual assignment you make in Settings can collide with the automatic logic, and the write fails with 0x00000709. Forcing legacy mode removes that collision, which is why the registry edit is the reliable cure when the troubleshooter alone is not enough.

Key points to remember

• The printer is usually reachable, the default printer setting is the real blocker.
• Always create a restore point before editing the registry.
• LegacyDefaultPrinterMode set to 1 forces stable manual default behaviour.
• If the error began after an update, removing that update is a valid fix.

Still broken? Your safety net

If the value is set, the spooler restarted, and you still cannot assign a default, check that the Print Spooler service is set to Automatic and running, and that no group policy is locking the default printer. On managed work machines, your IT admin may control this setting. Microsoft support can help confirm whether a specific update is the culprit on your build.

Microsoft printer supportMore Error Fix guides