The Printer Still Prints. Windows Protected Print Mode Removed Its Custom Options.

A printer that still prints normally but has lost every option the manufacturer used to put in front of the user is almost never a broken driver. Open Settings → Bluetooth & Devices → Printers & scanners, scroll down to Printer Preferences, and read the control labelled Windows protected print mode. If the button beside it says Turn Off, the mode is already enabled, and that one fact accounts for the whole symptom set: the vendor print preferences dialog replaced by a plain Windows one, the custom options that dialog used to expose now absent, and in many cases one or more printers missing from the list entirely.

Nothing failed. Windows changed which print path it is willing to use, and the old path is the one the manufacturer software lived on. Microsoft documents the switch plainly: "Windows protected print mode exclusively uses Windows Ready Print which provides additional print security benefits on PCs." The consequence is stated just as plainly on the same Windows Protected Print Mode page at Microsoft Learn: "Upon enabling Windows protected print mode, printers that use third-party drivers are uninstalled."

The One-Minute Confirmation

Three checks settle it. They take longer to read than to perform.

1. Read the button, not the toggle. Go to Settings → Bluetooth & Devices → Printers & scanners and scroll to Printer Preferences. The entry for Windows protected print mode offers Set up when the mode is off and Turn Off when it is on. The label states the action available, not the current state, which is exactly the wrong way round for a fast diagnosis and is why the setting gets misread.
2. Look for the compatibility icon on the printer tiles. Microsoft's setup instructions have a step for this: "Check if installed printers are compatible with Windows protected print mode by looking for this icon", followed by the icon itself. A printer without that icon cannot be reinstalled while the mode is on; one with it can, though Microsoft's own steps note that some printers may still need to be reinstalled.
3. Check whether the software printers went with it. This is the strongest single tell, and it is covered below.

If the button reads Set up, the mode is off and the missing options have some other cause. In that case the printer is worth checking the same way any post-update regression is checked, by establishing whether a Windows setting changed the rules or a component actually failed. That distinction is the same one behind a Windows Security warning about an older boot trust configuration, where the machine is reporting a policy decision rather than a fault.

The Tell That Rules Out a Driver Problem

Driver faults are specific. A driver that fails, or a driver that an update replaced with a generic one, affects the printer it belongs to. It does not reach across the system and remove unrelated print destinations.

Windows protected print mode does exactly that, and the documentation is explicit about which destinations go. On XPS and fax, the wording is "XPS and fax are removed when Windows protected print mode is turned on." On OneNote, the mode "uninstalls all unsupported software printers on Windows", and a replacement entry named OneNote (Desktop) – Protected virtual printer is provided in its place.

So the diagnostic is a list, not a guess. Open the printer list and check for these three signatures at once:

• Microsoft XPS Document Writer is gone.
• The Fax destination is gone.
• OneNote (Desktop) has been replaced by an entry whose name ends in Protected virtual printer.

No printer driver failure removes those three together, because they do not share a driver. If all three signatures are present, the mode is on, and there is no need to touch the vendor software at all. If none of them are present and the vendor dialog is still missing, the cause is elsewhere.

This pattern of a system-level policy producing what looks like a hardware fault shows up repeatedly. It is the same reasoning that explains a 5 GHz network that vanishes for exactly 31 minutes: a documented rule is running, the timing is deterministic, and replacing hardware changes nothing.

What Changed Underneath

The legacy Windows print path loads vendor code inside the print spooler. That is where the manufacturer preferences dialog and its custom options came from. The enterprise and developer background page describes why that design was changed: vendor drivers carry complex parsing logic, run with spooler privileges, and in many cases predate binary mitigations such as Control Flow Guard and Arbitrary Code Guard. Those mitigations are described there as all or nothing, meaning every binary in the process has to support them for any of them to apply.

Windows protected print mode removes the variable. In its place sits Windows Ready Print, which the Windows Ready Print documentation defines as "Windows' preferred means of communicating to printers, including the Internet Printing Protocol (IPP), eSCL scanning, and Universal Print." The point of it is stated in the next breath: "Windows Ready Print doesn't require the installation of third-party drivers. This provides a simple, streamlined, and secure printing experience compared to legacy printers, regardless of the PC's architecture."

That architecture clause matters more than it looks: because nothing vendor-specific has to be compiled for the machine, the same printer behaves the same way regardless of the PC's architecture. The trade is the one being felt. The printer has to speak IPP for any of this to work, which is why "Windows protected print mode is designed to work with Mopria certified printers."

Whether a given model qualifies is a lookup, not a judgement call. Microsoft points at the vendor-neutral Mopria certified products database for both printers and scanners, and the answer there determines which of the branches below applies.

Getting Manufacturer Features Back Without Turning It Off

Turning the mode off is the blunt answer and it is usually the wrong first move. The supported answer is a Print Support App, and Microsoft's FAQ states it directly. Asked whether custom driver features are lost, the answer given on the Windows Protected Print Mode FAQ is: "Your printer manufacturer will still be able to provide custom features via Print Support Apps (PSAs)."

A Print Support App is the replacement vehicle for exactly the thing that went missing. The Print Support App design guide frames the gap it fills: "Some printer features aren't presented in print dialogs shown by Windows as they're special features that need help from a manufacturer app to be configured correctly." The guide describes an optional extension contract that "can be activated by the user from all Windows print dialogs and custom print dialogs that use API provided by Windows", and notes that manufacturers can also improve output after rendering by optimizing content for the specific printer.

In practice this means the sequence below, in this order.

1. Reinstall the printer while the mode is still on. If the model is certified, it comes back on the Windows Ready Print path. The documentation describes this case precisely: "If a Mopria Certified printer was originally installed using a third-party driver: The printer is uninstalled, but can be reinstalled. When reinstalled, it uses Windows Ready Print instead of its third-party driver."
2. Open the print dialog and look for an extra preferences entry. If the manufacturer ships a Print Support App for the model, its custom interface is reached from the standard Windows print dialog rather than from a separate control panel applet.
3. Check the manufacturer's current support page for the exact model. Availability of a Print Support App is a per-model decision made by the vendor, not something Windows can supply on their behalf.
4. Only then consider disabling the mode. Treat it as the fallback, not the fix.

There is a scheduling argument for doing it in that order too. The FAQ notes that "Windows protected print mode will be enabled by default at a future date." A workflow rebuilt around a disabled mode has to be rebuilt again later; a workflow rebuilt around a Print Support App does not.

The Three Branches After Confirmation

Once the mode is confirmed as the cause, which branch applies depends on one lookup and one glance at the settings control.

Branch one: the printer is certified

Reinstall it and stay on the protected path. Custom features return through a Print Support App if the vendor publishes one. Scanning is a separate question, and it can fail independently: "Not all scanners are compatible with Windows protected print mode." A multifunction device can therefore keep printing while losing its scan function, which is worth checking before declaring the branch closed.

Branch two: the printer is not certified

The mode has to come off for that device to work at all. The FAQ is unambiguous about the state it is in meanwhile: "Non-compatible printers are uninstalled and will be not able to be reinstalled while Windows protected print mode is enabled. Compatible printers will be able to be reinstalled." Expect manual work afterwards, because disabling does not restore anything by itself: "If you disable Windows protected print mode, you'll have to manually reinstall any non-compatible printers."

Branch three: the control will not respond

On a managed device, the decision was made centrally and the local setting cannot override it. That case is covered in the next section.

When the Setting Is Locked

On a work or school device the mode is frequently switched on centrally, and in that case the Settings control is not the decision point. The documentation states the outcome without hedging: "If Windows protected print mode is enabled as group policy, you won't be able to disable it without contacting your administrator."

Escalating with the exact policy name saves a round trip, because it tells the administrator precisely which object to look at rather than asking them to hunt. Two identifiers cover almost every deployment, and both appear in Microsoft's enterprise guidance for the mode.

• Group Policy. The setting lives under Computer Configuration → Administrative Templates → Printers, and the policy is named Configure Windows protected print. The same location and policy name are repeated in the Windows 11, version 24H2 feature summary for IT pros, which is where the mode is documented as a feature of that release.
• Intune or another MDM. The configuration is delivered through the OMA-URI ./Device/Vendor/MSFT/Policy/Config/Printers/ConfigureWindowsProtectedPrint.

A request that names the policy and the uncertified model is a compatibility exception for one device. A request to turn off a security feature sounds like a request to weaken the fleet, and tends to be refused on those grounds. Framing matters here the same way it does when a dock quietly drops its USB ports to USB 2.0 because four DisplayPort lanes are already claimed: the fix depends on naming the specific constraint rather than reporting that something is broken.

Turning It Off, and What Has to Be Redone

If branch two applies and the device is not managed, the documented sequence is short.

1. Select Start.
2. Navigate to Settings → Bluetooth & Devices → Printers & scanners.
3. Scroll down to Printer Preferences and under Windows protected print mode, select Turn Off.
4. Select Yes.

Microsoft's own note on the final state is worth reading as a warning rather than a reassurance: "Windows protected print mode is now disabled. You can now install non-compatible printers." The phrasing is about what is now permitted, not about what has been restored. Three items usually need attention afterwards.

• Non-compatible printers. They do not return on their own and have to be added again by hand, along with whatever vendor software they depend on.
• XPS and fax. These are Windows optional components rather than printers in the usual sense, and Microsoft's documentation does not state how they are restored, so confirm in the printer list whether the destination has reappeared rather than assuming it has.
• OneNote. Anything that was pointed at the protected virtual printer entry during the period the mode was on needs pointing back, including saved presets in other applications that store a destination by name.

One more item belongs on the checklist. Turning the mode off restores the situation the security change was designed to end, so record which printer forced the decision and revisit it when that printer is replaced. The setting is documented as heading toward default-on, which makes this a deferral rather than a resolution.

When This Doesn't Apply

Several nearby symptoms look identical from the user's chair and have nothing to do with this mode.

• The printer does not print at all. Windows protected print mode either removes a printer from the list or leaves it working on the Windows Ready Print path. A printer that is present, accepts a job, and then produces nothing is a different problem, and the mode is not a productive place to start.
• Only one application lost its options. The mode operates below the application layer, so its effects are system-wide. A print dialog that changed in one program while the rest of the system is unchanged points at that program.
• The button reads Set up. That means the mode is off, and the missing features have another cause. Nothing in this article applies.
• The device runs an older Windows release. The mode is documented as a feature of Windows 11, version 24H2. Microsoft's enterprise page does not state a minimum version, so where the control is absent from Printer Preferences the mode is not the explanation, and its absence is not a fault.
• Universal Print or a print server is in the path. Printers arriving through a managed print service follow that service's own configuration, and a change there can produce a similar loss of vendor options for reasons unrelated to the local mode setting.
• The printer connects only over a vendor cloud service. Some models expose features exclusively through the manufacturer's own application rather than through the print subsystem. Those features are unaffected either way, and their disappearance points at the application or the account behind it.

The principle holds across all of these: confirm the state of the mode first, because it is a single control with a documented set of consequences, and only then treat what remains as a separate problem.

Sources

Microsoft Learn, Windows Protected Print Mode; Microsoft Learn, Windows Protected Print Mode FAQ; Microsoft Learn, Windows Ready Print and Windows Protected Print Mode; Microsoft Learn, More information on Windows protected print mode for enterprises and developers; Microsoft Learn, Windows Protected Print Mode for Enterprises; Microsoft Learn, What's new in Windows 11, version 24H2 for IT pros; Microsoft Learn, Print Support App v1 and v2 Design Guide; Mopria Alliance, Certified Products.