the_quick Posted March 15, 2021 Posted March 15, 2021 I think it does affect PCs if you use server shared printers, as the classroom computers didn't have that KB installed but still crashing, but it was installed on the server. For time being we changed printers to direct printing and approved for removal - it takes some time to take an effect. Bit annoying situation, we have a lot of Kyocera printers.
KK20 Posted March 15, 2021 Posted March 15, 2021 (edited) I should have said, the driver I swapped to on the print server was the classic KPDL 3.3 (not PCL or XPS) - it still has support for finishing units (it worked on our Taskalfa). All our P2135, TA2551 and p6026 worked without any further changes. I didnt need to change direct printing or remove the update. If you have already changed to the v4 driver and want to change back to a v3 you will probably get an error when applying - simply remove the share, apply v3 driver, reapply the share (I had changed to the microsoft PCL6 driver as an immediate fix but I needed accounting on some printers and finisher on others) Edited March 15, 2021 by KK20
Koldov Posted March 15, 2021 Posted March 15, 2021 Does anyone know if this has been acknowleged by Microsoft or Kyocera...?
KK20 Posted March 15, 2021 Posted March 15, 2021 https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-20H2 I havent heard a dickie bird from Kyocera or our rep. Our rep said she was looking into it, but I knew more than she was letting on.
mavhc Posted March 15, 2021 Posted March 15, 2021 rundll32 printui.dll,PrintUIEntry /Xs /n "KX driver for Universal printing" attributes +direct -- this Direct Printing means "don't spool", right? But it's still a smb share printer, so does that make any difference?
Koldov Posted March 15, 2021 Posted March 15, 2021 (edited) Well, I'm not holding my breath for Kyocera or MS to fix it then... or re-issue the update... Little bit confused about the workaround (changing to direct printing). I had one user report a bluescreen while attempting to print, luckily enough I was perusing EDUGEEK at the time and saw the thread about the Cumulative update vs Printing. I might have pulled the trigger a bit quickly, but I got into our WSUS and set the update for removal. I got the user to check for updates and let it run, did a reboot and then they could print. Nobody else actually reported a BSOD, but I wanted to mitigate the issues ASAP and not have all the teachers banging on my door (I might just have been lucky nobody else printed and the update was removed). However, I've just checked and the printer IS set for direct anyway... Checked on the printer properties 'advanced tab' not the CMD way (I presume that's the same thing)... If there are V4 drivers on the KYOCERA site, I'm wondering if I install those and then somehow get the Cumulative update back on WSUS? Should we all be on V4 drivers anyway if we can... seems like it's a big change? The first few Google hits make it sound like a right can of worms... is it something MS are trying to push (by destroying the ability to use Type 3)...? Or am I being a bit Are we going to have to choose between an MS security Update or a solid and reliable print driver that's been working fine for years...? Edited March 15, 2021 by Koldov
ass17 Posted March 15, 2021 Posted March 15, 2021 Microsoft are working on a fix (lol) for next week. If you can uninstall KB5000802 or KB5000808 then do that, other wise you will need to follow this for a temporary fix: https://www.ghacks.net/2021/03/13/microsoft-publishes-workaround-for-printing-bluescreen-issue-in-windows/?amp
Danp Posted March 15, 2021 Posted March 15, 2021 Thought I'd got away with this, but no, Dymo label machines printing blank labels https://www.dymo-label-printers.co.uk/news/troubleshooting-dymo-labelwriter-prints-blank-labels-or-advances-incorrectly.html
ass17 Posted March 15, 2021 Posted March 15, 2021 Well, I'm not holding my breath for Kyocera or MS to fix it then... or re-issue the update... Little bit confused about the workaround (changing to direct printing). I had one user report a bluescreen while attempting to print, luckily enough I was perusing EDUGEEK at the time and saw the thread about the Cumulative update vs Printing. I might have pulled the trigger a bit quickly, but I got into our WSUS and set the update for removal. I got the user to check for updates and let it run, did a reboot and then they could print. Nobody else actually reported a BSOD, but I wanted to mitigate the issues ASAP and not have all the teachers banging on my door (I might just have been lucky nobody else printed and the update was removed). However, I've just checked and the printer IS set for direct anyway... Checked on the printer properties 'advanced tab' not the CMD way (I presume that's the same thing)... If there are V4 drivers on the KYOCERA site, I'm wondering if I install those and then somehow get the Cumulative update back on WSUS? Should we all be on V4 drivers anyway if we can... seems like it's a big change? The first few Google hits make it sound like a right can of worms... is it something MS are trying to push (by destroying the ability to use Type 3)...? Or am I being a bit Are we going to have to choose between an MS security Update or a solid and reliable print driver that's been working fine for years...? Not much in terms of detailed changes between v4 and v3 but if you have paper cut then read this and why at the moment you should stay v3 for now https://www.papercut.com/kb/Main/WindowsType4PrintDrivers
ass17 Posted March 15, 2021 Posted March 15, 2021 rundll32 printui.dll,PrintUIEntry /Xs /n "KX driver for Universal printing" attributes +direct -- this Direct Printing means "don't spool", right? But it's still a smb share printer, so does that make any difference? This is why I’m going down the compatibility fix route. What’s even worse is you can’t uninstall the update on some versions of Windows 10, as you get an error saying that the update is part of the operating system, latest 20H2 especially.
Koldov Posted March 16, 2021 Posted March 16, 2021 Microsoft are working on a fix (lol) for next week Have they fixed it already...? "Out-of-band Update for Windows 10 fixes Printer-BlueScreen issue" https://www.ghacks.net/2021/03/16/out-of-band-update-for-windows-10-fixes-printer-bluescreen-issue/?amp 1
jezi55 Posted March 16, 2021 Posted March 16, 2021 We currently have this issue with Office 2019 and Windows 10 LTSC with Kyocera printers. I have approved the update for removal in WSUS and will also decline the update in a week. Users are able to check for updates which even though it says it is installing the march 2021 update it actually removes it... After about 10 minutes they reboot and can print again. The funny side of this is that we were supposed to replace all our Kyocera printers last march
mavhc Posted March 16, 2021 Posted March 16, 2021 New patch now available. V4 drivers don't include the advanced stapling, folding, etc etc
Koldov Posted March 16, 2021 Posted March 16, 2021 So, what a PITA! New patch now available. Now a patch is available, do we get the 2021-03 Cumulative Update back somehow in WSUS and reinstall it... and then install the patch? Or is the patch a new improved version of the CU? I'm only on 22% removal and there's other admins that have only just started removing it! What happens when my other machines come back on-line that have the original version downloaded.... gets installed... gets uninstalled.... gets patched... gets reinstalled....? V4 drivers don't include the advanced stapling, folding, etc etc Yes that's what I read about V4 drivers, the user doesn't see the advanced printing options, only a generic print dialogue... is that right? What's the point of that? Strange even the 'official' MS advice video for mitigating/workaround uses Kyocera drivers as an example...
mavhc Posted March 16, 2021 Posted March 16, 2021 The point is the drivers aren't in the kernel so they don't BSOD when there's a bug
Boredguy Posted March 16, 2021 Posted March 16, 2021 Well I installed the hotfix patch on a station that did not already have 5000808 installed, and printing to Kyocera Type 3 drivers was all happy. So far doing a check for additional updates online still has not pulled 5000808 to might not be that MS has re-released it yet, or not needed since it was a 400mb patch in the first place.
Koldov Posted March 16, 2021 Posted March 16, 2021 (edited) Yes, seems to be about right... Following the links and going to the Windows Update Catalogue leads me to a new KB number. It still says it is the 2021-03 CU and it also states: "If you installed earlier updates, only the new fixes contained in this package will be downloaded and installed on your device." So, I'm presuming if you have the original CU installed it's a patch, if you haven't (or have removed it) it's a fixed version of the CU... Edited March 16, 2021 by Koldov
caffrey Posted March 16, 2021 Posted March 16, 2021 Is that KB5001566 for 1909 ? Says that it won't be made available to WSUS and do we need to install the SSU too ? KB5000908 ?
Koldov Posted March 16, 2021 Posted March 16, 2021 Can't give you the numbers as I'm not on 1909. But I've imported the CU with the new KB into WSUS from the catalogue. Presumably the original SSU stands as is and should have already been installed. 1
Koldov Posted March 16, 2021 Posted March 16, 2021 (edited) Interesting to note this (just to say KB numbers are not for versions I have - just the first page I Googled - so don't take them as read): https://support.microsoft.com/en-us/topic/march-9-2021-kb5000802-os-builds-19041-867-and-19042-867-63552d64-fe44-4132-8813-ef56d3626e14 Microsoft now combines the latest servicing stack update (SSU) for your operating system with the latest cumulative update (LCU). If you encounter the error, 0x800f0823 – CBS_E_NEW_SERVICING_STACK_REQUIRED, close the error message and install the last standalone SSU (KB4598481) before installing this LCU. You will not need to install this SSU (KB4598481) again for future updates. If you want to remove the LCU To remove the LCU after installing the combined SSU and LCU package, use the DISM/Remove-Package command line option with the LCU package name as the argument. You can find the package name by using this command: DISM /online /get-packages. Running Windows Update Standalone Installer (wusa.exe) with the /uninstall switch on the combined package will not work because the combined package contains the SSU. You cannot remove the SSU from the system after installation. My bold... Edited March 16, 2021 by Koldov
ass17 Posted March 16, 2021 Posted March 16, 2021 Doesn’t anyone else, once installing the patch, now have an issue with printing images via the old photo viewer app or the new photos viewer app? It just prints lines for us on our Konica Minolta MFPs.
Boredguy Posted March 16, 2021 Posted March 16, 2021 Is that KB5001566 for 1909 ? Says that it won't be made available to WSUS and do we need to install the SSU too ? KB5000908 ? Yes 1566 was for 1903/1909, 1567 for 2004, 1568 if your on 1803, anything older and well.. it's out of the support window really. Our stations already had 908 as we only pulled 808 from deployment 1
caffrey Posted March 16, 2021 Posted March 16, 2021 Managed to import after fixing the WSUS server...
Boredguy Posted March 16, 2021 Posted March 16, 2021 Easier to just download the file and deploy it out.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now