Windows 11 KB5083769 Universal Print Bug: Per-User Fix and Konica Minolta Pending Jobs

These two problems have different causes and different scopes, and only one has a fix you can apply yourself. Here is what Microsoft says, what it does not say, and how to work out which problem you have.

The Windows 11 regression: KB5083769 and later​

Microsoft's Universal Print known-issues page says there is a regression in Windows 11 KB5083769 and later that may cause Universal Print printers that were originally installed on Windows 10 to stop functioning. Neowin dates KB5083769 to the April 2026 Patch Tuesday. It also reports that Microsoft acknowledged the problem at the end of July, which fits the age of the Learn entry. Neowin argues that this left admins without an official answer for nearly four months, and Microsoft's own timeline gives no reason to doubt that.

The symptoms​

There are two error messages to watch for:

• In the print dialog: when selecting an affected printer in the print dialog, you may see the following error, and the Print button will be disabled: "Your printer has experienced an unexpected configuration problem. 0x80004005"
• When printing a test page: Microsoft says a test page from Printer Properties fails with "The I/O operation has been aborted because of either a thread exit or an application request" and may show the error code 0x000003e3.

0x80004005 is Windows' famously vague "unspecified error." On its own it doesn't prove you have this bug, so check before you start re-adding printers across the company.

Who is actually affected​

The scope is narrower than the headlines suggest. Microsoft says the issue applies to Universal Print printers installed on Windows 10 and subsequently used on devices running Windows 11 KB5083769 or later. A printer added fresh on Windows 11 is not in this category. The trigger is a Windows 10-era installation that carried over to Windows 11.

Neowin also reports that installing the newest feature update, version 26H2, does not clear the problem. Microsoft's known-issues entry does not mention 26H2. It gives no fix date and does not say that any later feature update resolves the regression. In practice, assume that upgrading won't help and that the workaround is the remedy.

Section summary: The bug affects Universal Print printers carried over from Windows 10 onto Windows 11 machines running KB5083769 or later. The print dialog shows 0x80004005, and test pages fail, sometimes with 0x000003e3.

How to check whether a device is affected​

Microsoft gives two detection methods. Neither needs admin rights. Microsoft specifically says to run them in a window that is not elevated.

Method A: Microsoft's PowerShell script​

1. Download Microsoft's Convert-UpPrinterToPerUser.ps1 script. Microsoft hosts it in its universal-print-resources repository on GitHub.
2. In a normal, non-administrator Terminal or PowerShell window, run:
   .\Convert-UpPrinterToPerUser.ps1 -Detect
3. Read the result:
   • No per-system Universal Print printers found means this regression is not your problem. Microsoft tells you to contact Support instead.
   • A list of printer names followed by a line like "Yes, per-system Universal Print printers were found. Count: 2" means the device is affected.

Method B: Check the registry​

1. In a non-administrator Terminal, PowerShell or Command Prompt, run:
   reg query "HKLM\SYSTEM\CurrentControlSet\Control\Print\Printers"
2. Find the affected printer's name in the output.
3. Look at how its key is named:
   • Not affected: the name has a SID-style prefix, such as ...\Printers\S-1-12-1-1234567890-...:YourPrinterName.
   • Affected: the key is just the printer name, such as ...\Printers\YourPrinterName, with no S-<numbers> prefix.

The registry naming shows what is going on. Affected printers are installed per system, while unaffected ones are tied to a user identity. The regression breaks the per-system Windows 10 installation pattern. That is why both fixes convert printers to a per-user installation.

Section summary: Use the -Detect switch or the registry query. A printer key without the S-1-12-1-... prefix means the device is affected.

Option 1: Fix a single machine​

For one PC, Microsoft's fix is simple: remove the affected printer and add it back through Settings > Printers & scanners. It's not elegant, but it works for a lone executive's laptop or a small office.

Option 2: Fix the whole fleet with Intune​

For bulk repairs, Microsoft offers the same Convert-UpPrinterToPerUser.ps1 script in conversion mode. Microsoft says it suits deployment through Intune or other management tools. It also warns that this option is not meant for end users, because testing it by hand requires PsExec.

Test on one machine first​

Microsoft recommends a manual test before you deploy widely:

1. Install PsExec.
2. From an elevated Terminal or PowerShell, run .\PsExec.exe -i -s powershell to open a PowerShell session running as SYSTEM.
3. In that PsExec window, run:
   .\Convert-UpPrinterToPerUser.ps1 -AllUPPrinters -TenantId <YOUR_TENANT_ID>
4. Wait a minute or two for the Windows Print Spooler to finish restarting, then check that the affected printers work again.

Set it up in Intune​

Intune doesn't pass parameters to scripts in this case, so you have to edit the script:

• Hardcode the parameters. Set AllUPPrinters and your TenantId inside the script's param() block. Microsoft's example sets [string]$TenantId = "YOUR_TENANT_ID" under the ConvertAll parameter set.
• Run as System. Make sure the script does not run with the logged-on user's credentials.
• Use 64-bit PowerShell. Turn on the 64-bit PowerShell host option.

Expect the Spooler to restart on each device. If that happens mid-print, the user will notice, so plan the rollout window with that in mind.

The catch: system-wide installs are gone​

Microsoft is clear that the workaround has a cost. After either mitigation, printers that were installed system-wide become per-user only, and the known-issues page states that Universal Print printers can no longer be installed system-wide.

That matters most in a few setups:

• Shared and kiosk PCs. One system-wide printer used to serve everyone. Now each user needs the printer provisioned for their own profile.
• Labs and hot-desking. A new user who signs in won't automatically see printers another user had.
• Provisioning baselines. Any imaging or deployment process that assumed machine-level Universal Print queues needs another look.

This is a supported workaround, not a patch that changes nothing. It may also be where Microsoft wants Universal Print to go anyway. Its own documentation has long listed complaints that on Windows 10 shared PCs, printers were installed for every user who signed in. Per-user installation avoids that problem, but nobody asked for the change to arrive like this.

Section summary: The fix works, but it permanently moves affected printers to per-user installation. Check that against your shared-device and provisioning plans before deploying.

A separate problem: Konica Minolta printers going silent​

The second issue has nothing to do with Windows 11 updates. Microsoft's list of Universal Print Ready printers now carries a warning, last updated October 16, 2026, at 18:03 UTC. It says some listed Konica Minolta printers have an ongoing problem in which they intermittently stop communicating with Universal Print.

When that happens:

• The printer stops retrieving print jobs. Jobs stay Pending and become Aborted if the printer doesn't collect them within three days.
• The printer's Last Seen timestamp in the Azure portal stops updating. Microsoft says admins can use this to confirm the device has gone quiet.

Microsoft says it is in close contact with Konica Minolta, which is investigating. No root cause and no fix timeline have been confirmed. For now, Microsoft's advice is to contact Konica Minolta support and open a case for the affected printers.

Note the word "some." The warning sits above a long list of bizhub models, including the 300i, 450i, 550i, 650i, C250i, C300i and C450i families. Microsoft does not say every listed model is affected. Before you blame your fleet, check a specific device's Last Seen behavior.

Also, nothing in Microsoft's documentation links this to the KB5083769 regression. The per-user conversion script is not described as a fix for Konica Minolta communication failures, so running it on those devices is unlikely to help.

Which problem do you have?​

One caution on Last Seen: Microsoft's known-issues page also says the timestamp can be inaccurate on some printers. Connector-based printers, and Universal Print Ready printers that don't keep an active channel open, may only update it when they process a job. A stale Last Seen on an idle printer is a clue, not proof.

The bigger picture​

This isn't the first time Windows 11 changes have upset Universal Print. In late 2024, admins on Microsoft's Q&A forum reported that updating some devices to Windows 11 24H2 caused Microsoft Universal Print (Cloud) to stop working. In that case, the accepted answer blamed a third-party connector. It said Microsoft had tightened enforcement of Mopria specifications that PaperCut had not followed to the letter.

The pattern is familiar. Cloud printing was supposed to replace fragile print servers, but the client side still lives inside Windows' print stack and changes with every cumulative update. And when a regression stays unacknowledged for months, admins pay for it in help-desk tickets.

To be fair, Microsoft's write-up is unusually practical. It includes detection logic, a registry check that doesn't need admin rights, a bulk remediation script and notes for deploying through Intune. Konica Minolta customers get less: a confirmed problem and an instruction to call the vendor.

What admins should do now​

1. Triage first. Use the table above to work out which issue you're dealing with.
2. For Windows 10 carry-over printers: run -Detect on a sample of machines, test the bulk script under PsExec, then deploy through Intune as System in 64-bit PowerShell.
3. Warn shared-device owners that affected printers will become per-user.
4. For Konica Minolta fleets: watch Last Seen and jobs stuck in Pending, and open a vendor support case for affected units.
5. Keep an eye on Microsoft's notices. The Konica Minolta warning says it will be updated as more information becomes available, and the Windows 11 entry still has no fix date.

So far, the only fix for the Windows 11 regression is a script and a permanent switch to per-user printers.