Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x0000007C

Error 0x0000007C: printer driver or print processor not supported by Windows

11 min read Updated October 5, 2026 Networking, Sharing & Printing

Fix it now

Microsoft publishes 0x0000007C as ERROR_INVALID_LEVEL, the system call level is not correct: one side made a printing call using a form of the information the other side does not support. On a shared queue that usually means the client will not take what the server is offering – an old driver model, or a print processor other than the standard one.

Run these on the print server, in an elevated PowerShell session

Get-Printer -Name "QueueName" | Select-Object DriverName,PrintProcessor
Get-PrinterDriver | Select-Object Name,MajorVersion
Set-Printer -Name "QueueName" -PrintProcessor winprint
  1. A MajorVersion of 3 is the older driver model. If the manufacturer publishes something newer for the model, install it on the server and repoint the queue with Set-Printer -Name "QueueName" -DriverName "New driver name".
  2. Set the queue back to the standard print processor unless a specific feature genuinely needs otherwise, which is what the third line does.
  3. Reshare the queue, then remove the old connection on the failing client before reconnecting, so it does not reuse cached driver information.
  4. If no newer driver exists for the model, connect the client to the device over IPP with the in-box class driver instead of going through the server.

Changing the print processor affects every client of that queue. Test one document type per workflow rather than assuming a test page proves it, particularly where stapling, secure release or accounting were the reason somebody changed it.

If the failing client connects and prints, you are done. If it does not, the next section covers why newer clients are fussier than the ones that still work.

Why it happens

Windows has carried two printer driver models side by side for a long time. The older one is installed per architecture and often arrives with manufacturer plug-ins, configuration modules and a custom print processor. The newer one is packaged and signed, and is designed so a client never has to load code it did not vet. A shared queue offers whatever the server holds, and 0x0000007C is what you get when the client will not accept the form of that offer.

The direction of travel is published and it matters for how much effort this deserves. Microsoft’s end-of-servicing plan for third-party printer drivers says that from 15 January 2026 no new printer drivers are published to Windows Update for Windows 11 and later and Windows Server 2025 and later; from 1 July 2026 driver ranking is modified to always prefer the Windows IPP inbox class driver; and from 1 July 2027, except for security fixes, third-party printer driver updates are no longer allowed. Its own wording groups legacy v3 and v4 drivers together and points at the IPP class driver.

Windows protected print mode is the same idea enforced on the client. Microsoft describes it as preventing the installation of third-party drivers and removing the need for driver management, enforcing Windows Ready Print, which works with Mopria certified printers. A machine in that state cannot consume a manufacturer driver from a print server however the share is configured, and that is by design rather than a fault to be worked around.

The companions name the specific thing being refused. 0x00000705 is ERROR_UNKNOWN_PRINTER_DRIVER, the printer driver is unknown. 0x00000706 is ERROR_UNKNOWN_PRINTPROCESSOR, the print processor is unknown. 0x0000070C is ERROR_INVALID_DATATYPE, the specified datatype is invalid, which turns up on a queue set to a raw or manufacturer-specific data type the client will not produce.

The shared queue uses the older driver model

You have this one if Get-PrinterDriver on the server shows MajorVersion 3 for the driver the queue uses, and only newer clients fail.

  1. Check the manufacturer’s download page for a package-aware or class driver for the model.
  2. Install it on the server and point the queue at it with Set-Printer -DriverName.
  3. Remove the connection on the failing client, then reconnect so it picks up the new driver information.
  4. Where the manufacturer has nothing newer, use the in-box class driver on the server so clients receive something they will accept.

The queue uses a custom print processor

You have this one if 0x00000706 accompanies the failure, and Get-Printer shows a print processor other than winprint.

  1. Set the queue back to the standard processor: Set-Printer -Name "QueueName" -PrintProcessor winprint.
  2. Test the features that made somebody change it, usually stapling, secure release or accounting.
  3. If those features genuinely need the manufacturer’s processor, that queue stays on the older model and the affected clients need a direct IPP connection instead.

The client will only accept the in-box class driver

You have this one if One group of machines fails consistently while everything else prints, and those machines are the newest builds or are centrally managed.

  1. Check whether Windows protected print mode is enabled, at Computer Configuration, Administrative Templates, Printers, Configure Windows protected print, or through the equivalent Intune policy.
  2. Where that is intended, connect those clients over IPP to the device, or to a queue published with the class driver, rather than pulling a manufacturer driver from the server.
  3. Where it is not intended, adjust the policy, run gpupdate /force and reconnect.

The server does not publish the client’s architecture

You have this one if Clients on one processor architecture fail while others on the same network succeed.

  1. On the server, read the environment column in Print Server Properties, Drivers tab, to see which architectures are published.
  2. Add the missing architecture’s driver, or move those clients to the class driver.
  3. Reconnect the client after the driver is added. It will not retry on its own.

The queue’s data type does not match what the client sends

You have this one if 0x0000070C, often on a queue set to a raw data type years ago to work around a rendering problem.

  1. Open the queue’s Advanced tab and check the print processor dialog for the default data type.
  2. Return it to the standard option unless a specific application needs raw output.
  3. Test the application that prompted the original change before rolling it out to everyone.

Full reference

Four codes, and what each one is published as

Code Published meaning
0x0000007C ERROR_INVALID_LEVEL: the system call level is not correct
0x0000070C ERROR_INVALID_DATATYPE: the specified datatype is invalid
0x00000706 ERROR_UNKNOWN_PRINTPROCESSOR: the print processor is unknown
0x00000705 ERROR_UNKNOWN_PRINTER_DRIVER: the printer driver is unknown

0x0000007C is generic by design. Nothing in its published meaning mentions printing at all: it says a call was made with an information level the other side does not support. That is why it appears in this situation rather than being defined by it, and why the diagnosis is comparative – what does the server offer, what will this client accept – rather than a lookup.

The published timeline for third-party drivers

Date What Microsoft says changes
15 January 2026 For Windows 11 and later and Windows Server 2025 and later, no new printer drivers are published to Windows Update. Existing drivers can still be updated, approved case by case
1 July 2026 Printer driver ranking order is modified to always prefer the Windows IPP inbox class driver
1 July 2027 Except for security-related fixes, third-party printer driver updates are no longer allowed. Existing drivers can still be installed from Windows Update or from a manufacturer’s installation package

Read that as a scheduling input rather than a deadline to panic about. A queue on an old driver model is not going to stop working on any of those dates, but the effort you spend keeping it alive buys progressively less, and the replacement – the IPP class driver against a Mopria certified device – is already the preferred option on current builds.

Where the class driver costs you something

  • Finishing options. Class drivers expose a common set of features and may not surface every option on a high-end device.
  • Manufacturer accounting and secure release, where those are implemented in the driver or the print processor rather than in the device.
  • Per-queue default settings that were configured in the manufacturer’s driver interface and have no equivalent.
  • Anything relying on a raw data type, which is usually an application printing something the class driver will not reproduce.

Test those before you remove the old driver from the server, and test them with the documents that matter rather than with a test page. A test page proves the path works and nothing about whether the finance system’s cheque run still lines up.

Connecting to the device instead of to the server

Through the print server Direct over IPP
Driver Supplied by the server In-box class driver on the client
Central defaults Yes No
Job accounting on the server Yes No
Works on a client that refuses manufacturer drivers Only if the queue uses an acceptable driver Yes
Effort to deploy One change on the server One connection per client, or a policy

When the queue looks correct and one client still fails

  • Remove the connection on that client and reconnect. Cached driver information survives a great deal and is the most common reason a fixed queue still fails on one machine.
  • Check whether that client is in protected print mode while the others are not.
  • Check the client’s PrintService Admin log during the attempt, which names what it refused.
  • Compare the driver actually installed on a working client with the one on the failing one, rather than comparing both with the server.
  • Check whether a policy is restricting which servers the client will accept drivers from, which produces a similar failure for a different reason.

Every code this article covers

Code What it points at Source
0x0000007C ERROR_INVALID_LEVEL: the system call level is not correct Microsoft Learn
0x0000070C ERROR_INVALID_DATATYPE: the specified datatype is invalid Microsoft Learn
0x00000706 ERROR_UNKNOWN_PRINTPROCESSOR: the print processor is unknown Microsoft Learn
0x00000705 ERROR_UNKNOWN_PRINTER_DRIVER: the printer driver is unknown Microsoft Learn

Confirm the fix worked

  1. Run Get-Printer -Name "QueueName" | Select-Object DriverName,PrintProcessor on the server and confirm both are what you intended.
  2. Remove the old connection on the failing client, reconnect, and confirm it completes without an error.
  3. Print a test page, then a real document from the application that matters most.
  4. Check the client’s PrintService Admin log for new driver or processor errors written during the test.
  5. Test one machine from each build in the estate, since this failure is specific to what the client will accept.

Questions people ask about this

Does moving to the in-box class driver cost anything?

No. The class driver ships with Windows and repointing a queue is a configuration change. The cost is time, and occasionally a device feature that only the manufacturer’s driver exposed.

Will I lose stapling and finishing options?

Sometimes. Class drivers expose a common set of features and may not surface every finishing option on a high-end device. Test the workflows that matter before you remove the old driver from the server.

Why does the same queue still work from older machines?

Because those machines still accept the older driver model. The queue has not changed; the clients have. As they are replaced the queue will fail for more of your users, so treat this as work to schedule rather than avoid.

Is there a deadline I need to work to?

Microsoft has published a timeline rather than a cut-off: no new drivers on Windows Update from January 2026, driver ranking preferring the IPP class driver from July 2026, and no third-party driver updates except security fixes from July 2027. Existing drivers keep working; what stops is the supply of new ones.

Can I print without a print server at all?

Yes, for devices that support IPP. The client talks to the printer directly with the in-box driver and there is no server-supplied driver to refuse. You give up central defaults and job accounting in exchange.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix 0xC0000234 account locked out and other logon states that block shares Free Fix Error 0x80070052: the directory or file cannot be created on a share Free Fix The semaphore timeout period has expired: 0x80070079 copying to a share Free Fix Error 0x8009030C: logon denied when NTLM is blocked or restricted
โ† Back to Knowledge Base