This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(54.400000000000006, 50%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPS%3C/text%3E%3C/svg%3E)
We've been using a Type 4 printer driver and Printer Driver extension successfully for quite some time on both Windows 10 and Windows 11 machines
Since October 2022 Cumulative Updates: KB5018418 (Windows 11) and/or KB5018410 (Windows 10), invoking printing preferences no longer uses the printer extension.
Uninstalling the updates resolves the issue and restores the desired behavior. Has anybody else experienced this?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(313.6, 19%, 40%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EP%3C/text%3E%3C/svg%3E)
V4 printer drivers now appear to work, after the November 2023 Windows updates that include KB5031445. Can anyone else confirm or refute this?
We've an actual case opened with Microsoft regarding our specific trouble and have been pressing for resolution.
We've provided diagnostic traces and a variety of information.
It was described to us as a known issue, being worked on but nothing more at this time
We continue to inquire and press for resolution regularly.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(67.2, 22%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESR%3C/text%3E%3C/svg%3E)
Hi, thanks for an update.
Then we are hopefull for a solution. For every update I hold my fingers crossed but no success yet :-(
/S
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(192, 93%, 28%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVJ%3C/text%3E%3C/svg%3E)
Any luck with this particular issue? Is it still being worked on internally?
As a V4 printer driver developer, I have also reproduced the failure of the driver after the previously mentioned Windows updates. It seems the updates caused the drivers to now fail if the driver packages employ ".js" JavaScript files, either signed of unsigned. Has anyone else experienced this or found a solution? These files are used to transfer data between Devmode and the V4 PrintTicket.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(96, 82%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EM%3C/text%3E%3C/svg%3E)
Yes we've had issues with this as well. Haven't found a solution yet.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 34%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAF%3C/text%3E%3C/svg%3E)
Same issue for us here too
Hi Marc, Hi Andrew,
What make/model of printer/driver(s) are you using?
Also, have you been able to even print (for example a standard test page)?
