With the release of Windows 10 and 11, there has been an increase in customers using Windows Store Apps such as the Edge browser. Windows Applications are those which can be obtained from the Windows Store, such as Microsoft Reader, the Edge browser, OneNote, Maps, and Photos.
To handle print jobs from these applications, Microsoft introduced a new datatype for print jobs called XPS2GDI which generates two spool files for each document printed. We’ve seen a couple complications happen because of this new rendering method.
For example:
Jobs can get logged twice in older versions PaperCut Jobs may be stuck in a “printing” state in rare situations Thankfully we’ve found an easy way to prevent these issues by forcing the setting Render print jobs on client computers on your Windows Print Server. For more best practices check out our article on how to set up Windows Print queues to get the most out of PaperCut.
Articles in this section
- Share ARM64 Drivers from Windows Print Servers
- Printing from Microsoft Edge Browser and other Windows 10 and 11 Store Apps
- Top 10 best practices for implementing Print Quotas in education
- PaperCut Hive and SentinelOne
- Troubleshooting Mobility Print and Lightspeed
- Troubleshooting PaperCut Pocket & Hive Login
- Smooth MFD Upgrades: A Step-by-Step Guide
- PaperCut NG/MF Security Bulletin (December 2024)
- Redirected Printers on Windows Servers
- Windows ARM64 Support across the PaperCut portfolio
Comments
0 comments
Please sign in to leave a comment.