After KB5026363 "Remote Desktop Easy Print" stopped working

Question

Microsoft Windows Server 2016 Standard, 10.0.14393 on PowerEdge R530

"Remote Desktop Easy Print" was working until KB5026363 was installed. We confirmed that by restoring a backup before installing the Update, confirm that Easy Print is working and the installing KB5026363 again. After reboot "Remote Desktop Easy Print" stopped working.

The locally connected printers are shown a redirected on the Server, used driver on the server is "Remote Desktop Easy Print" version 10.0.14393.3442. If the device settings are opened, the local printer settings dialog is viewed (for example from Brother or Kyocera) which is the essential key feature why someone wants to use Easy Print so obviously there is a connection between the Server and the local installed printer driver.

But as soon as you start a printer job, for example from notepad you get "Das Handle ist ungültig" in english something like "the handle is invalid".

PS C:\Users\weber> "Hello World" | Out-Printer -v -Name "\\jupiter\OneNote (Desktop) (umgeleitet 2)"
out-lineoutput : Das Handle ist ungültig
In Zeile:1 Zeichen:1
+ "Hello World" | Out-Printer -v -Name "\\jupiter\OneNote (Desktop) (um ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [out-lineoutput], Win32Exception
    + FullyQualifiedErrorId : System.ComponentModel.Win32Exception,Microsoft.PowerShell.Commands.OutLineOutputCommand

Printing a testpage also fails with "Die Testseite konnte nicht gedruckt werden.... Das System unterstützt den angeforderten Befehl nicht"

Eventviewer for PrintService just shows info Event-ID 823 (DefaultPrinterSelectedBySpooler), no errors are shown in the eventviewer

Answer 1

I had the same issue on our Windows Server 2016 Server Datacenter RDS (German). Disabling Remote Desktop Easy Print Driver was not a solution, as we had other Problems with that.

We fixed it currently by coping the MXDWDRV.DLL from another Server to the Folder "C:\Windows\System32\spool\drivers\x64\3".

Both Servers are patched to 2024-01, I don't know why there are different DLL-Version on this two Servers. The only difference is, that one is an Application-Server and the other is an RDS-Server (Both 2016 DC German).

The not working DLL has a last changed Date of 29.08.2023.

The working DLL has a last changed Date of 09.05.2023.

Answer 2

Hello there,

As this error is due to a Windows update we might need to wait for an official workaround or hotfix from Microsoft.

The 823 error message usually indicates that there is a problem with underlying storage system or the hardware or a driver that is in the path of the I/O request. You can encounter this error when there are inconsistencies in the file system or if the database file is damaged. In the case of a file read, SQL Server will have already retried the read request four times before it returns 823.

You can raise feedback to the Microsoft team. The Feedback Hub app lets you tell Microsoft about any problems you run into https://support.microsoft.com/en-us/windows/send-feedback-to-microsoft-with-the-feedback-hub-app-f59187f8-8739-22d6-ba93-f66612949332

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 3

Have you already found a solution?