Edge crashes on print via extension
Summary: We have an extension which registers a printer. When opening the print dialog, selecting our extension registered printer and clicking "Print", the Edge browser crashes. Here's a minimal print extension example (not made by me) which reproduces the issue: https://github.com/hendrik-weiler-gtm/printerTestBare/tree/main Context: We have created an extension which uses the PrinterProvider API to print a page, and then sends the printed page somewhere. The extension is published in Chrome and Edge stores. It works in Chrome but crashes in Edge. We found this similar example (which is where we got the example extension). https://github.com/MicrosoftEdge/WebView2Feedback/issues/3795 This related bug was posted in September of 2023. Why hasn't this bug been addressed yet? We need this bug to be fixed, as our customers depend on this behavior working in critical business flows. Please have a look at this issue urgently. Demo/more info: Attaching a recording demonstrating the behavior. When clicking Print in the printer dialog, the browser crashes. To Microsoft Support: More details can be found in the linked Feedback Hub ticket: https://aka.ms/AAp45ui
Microsoft's PrintNightmare update is causing a lot of problems with network printers
Dears, the latest Windows updates is causing a lot of problems with network printers mapped on a print server. Reference: https://support.microsoft.com/en-us/topic/kb5005652-manage-new-point-and-print-default-driver-installation-behavior-cve-2021-34481-873642bf-2634-49c5-a23b-6d8e9a302872 https://support.microsoft.com/en-us/topic/managing-deployment-of-printer-rpc-binding-changes-for-cve-2021-1678-kb4599464-12a69652-30b9-3d61-d9f7-7201623a8b25 The two recent patches (KB5004945, KB5004760, or KB5003690) causes these two main problems: 1) unable for users without administrative rights to install new print drivers. The end user receive this error 2) unable to use the print server with the new registry key RpcAuthnLevelPrivacyEnabled **The system logs reports this error: 0x0000011b** The two workarounds that you have to apply to survive and allow corporate users to be able to use the print server are: 1) Even if you have a GPO with "Point and Print Restrictions=disabled", you have to apply this registry key to allow non administrative users to install the latest print drivers from the print server HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows NT\Printers\PointAndPrint RestrictDriverInstallationToAdministrators = 0 2) Apply this registry key to disable the new default settings related to the print spooler vulnerabilities HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print RpcAuthnLevelPrivacyEnabled = 0 The above workarounds are only a temporary solution to survive and allow users to print. What is unclear to me is what should be the right way to manage these settings in a corporate environment without any end user interaction. So, if I want to be protected and apply the recent security fixes without asking the end users to do something, what should I do? Microsoft states that you need to set "RpcAuthnLevelPrivacyEnabled" to "1" on both Client and Print Server in order to be protected, but if you do this, you can't print. So, what should we do in a Corporate environment to be secure and print without any end user interaction about "driver installation" etc.? Thanks in advance
Can't print or export pdf in Word on mac
Microsoft Word (latest) on macOS monterey 12.3.1. Nothing happens if click on print option. Not from file, toolbar or shortcut. Also get an error message after trying to save as pdf - best for printing: The document “...” could not be saved as “...”. Share-send as pdf does nothing as well. Any thoughts?
DateTime-Sent-to-Printer as File Property Detail in Windows 10
Printer sometimes taking day(s) creates challenge (impossible) identifying printouts of different documents (footer having filename is insufficient when names can be same while different folders). Having time-sent-to-printer as footer to me is simplest solution (I only need to record DateTime of folder I have printed; as match to printouts if it contains DateTime-Sent-to-Printer). Although printer is capable of add print time to printout, it is NOT time-sent-to-printer. DateTime-Sent-to-Printer as file attribute would ease my job to search for files printed for certain time frame. I have thought of following alternatives: Using printout order not viable; it is not necessarily same order sent to printer. Adding folderpath into filename as a way to differentiate (sorting) printouts is a solution but cumbersome requiring programming.
