Share via

universal print

abdo elbarbary 60 Reputation points
2026-06-02T11:16:59.5466667+00:00

We are experiencing this known issue from Microsoft, and the article https://learn.microsoft.com/en-us/universal-print/macos/universal-print-macos-known-issues#known-universal-print-issues states that it was fixed in macOS Sonoma 14.2. However, we are still experiencing the problem.

Windows for business | Windows Client for IT Pros | User experience | Print, fax, and scan
0 comments No comments

2 answers

Sort by: Most helpful
  1. Quinnie Quoc 11,485 Reputation points Independent Advisor
    2026-06-02T12:01:37.27+00:00

    Hello abdo elbarbary,

    I reviewed the Microsoft documentation you referenced. The article states that the Universal Print issue on macOS was resolved in Sonoma 14.2, but if you are still experiencing the same behavior, it indicates that the fix may not be fully effective in your environment. The most common reason is that the Universal Print connector or printer driver cache has not been refreshed after the OS update, so the client continues to use the old workflow. In practice, this means you should remove the affected printer from System Preferences, clear the print spooler cache, and re‑add the printer using the latest Universal Print configuration profile.

    Another important point is that the fix in 14.2 only addressed the core OS printing stack. If your environment uses conditional access, proxy settings, or custom certificates, those can still trigger the same error symptoms. Microsoft’s guidance is to validate with the latest Universal Print client package and ensure that the macOS device is fully updated to 14.5 or later, since subsequent point releases included additional reliability fixes. If the issue persists even after a clean reinstall of the Universal Print queue, it should be escalated with Microsoft support as a regression case, since the official fix was confirmed but may not cover all deployment scenarios.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you,

    QQ.

    Was this answer helpful?

    0 comments No comments

  2. AI answer

    2026-06-02T11:17:09.4433333+00:00

    The known issue where print jobs do not appear in the print queue is documented as fixed in macOS Sonoma 14.2, but the documentation also notes that even when this symptom occurs, the job is still processed.

    For environments still seeing the behavior:

    1. Confirm OS version
      • Verify that the affected Macs are running macOS Sonoma 14.6.1 or later, which is the minimum supported version for the Universal Print app.
    2. Validate printing behavior
      • From any app, use Cmd+P and send a job to a Universal Print printer.
      • Even if the job does not appear in the local print queue, check whether it completes successfully on the printer.
      • If the job does not complete as expected, follow the general Universal Print print‑job troubleshooting guidance referenced from the macOS setup article: “If your job is not completing as expected, try these steps” in the Universal Print troubleshooting article for print jobs that do not complete successfully.
    3. Check for printer‑specific issues
      • Confirm whether the affected printer models are listed under Printers with known issues for Universal Print on macOS. If so:
        • If the printer is registered directly with Universal Print, consider registering it using the Universal Print connector instead. This is the recommended workaround to allow those printers to work correctly from macOS.
        • If the connector cannot be used, consider disabling those partially supported printers from being shown to users to avoid ongoing incidents.
    4. If the issue persists beyond these conditions
      • Collect logs as per the macOS troubleshooting guidance:
        • Copy the Universal Print app log from ~/Library/Group Containers/UBF8T346G9.com.microsoft.universalprintmac/Library/Caches/log.txt.
        • Use Console.app → Start Recording → reproduce the issue → Stop → select all messages (Cmd+A) and save to a text file.
      • With these logs, contact Microsoft support so the behavior can be investigated as a potential regression or environment‑specific issue.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.