Blue Screen Day - Office 2016 and Printing related

[_techie_]

Blue Screen Day - Office 2016 and Printing related

Anyone else experiencing freezing surrounding printing and office 2016 today?

Mine is occuring at random but the tie in seems to be surrounding printing and office!

 

Hope I'm not alone.

 

Thanks

Mark

[bondbill2k2]

This is due to this weeks patch Tuesday update KB5000802 and KB5000808 I've seen reported as causing this issue with certain printers. Mostly Kyocera models. I've checked out systems neither of these patchs are installed, also approved removed from WSUS but still having the issue.

[CHiLL]

Here's a thread created yesterday about the issues mentioned by @bondbill2k2:

http://www.edugeek.net/forums/enterprise-software/220874-urgent-disable-updates-sccm.html

[_techie_]

Hi.

 

Thats interesting, as I don't have those updates installed, but we are using Kyocera printers!

I'll update as I know more.

 

Cheers

[caffrey]

I read about it this morning, but it was too late

 

approving it for uninstall in WSUS has done the trick

[Jay241]

Yep so we have had this issue on practically all our PC's. We've gone with switching over to the PCL6 Driver and that has cured the blue screen issue.

 

We have Kyocera TASKalfa 4053ci's and it seems to be ok them.

[Koldov]

Had my first report of BSOD today from our admin staff.

 

Asked her what she was trying to do when it happened (print an email), just as I was browsing through EDUGEEK and voila!!! This thread appeared....

 

What a life (job) saver this forum is!

 

Approved the update for removal and 10 minutes later calm was restored - how much hassle would this have been without you guys?

 

Does anyone know if:

 

a) It's prudent to just remove all 2021-03 Cumulative Updates for all Windows 10 versions?

 

b) Once approved for removal, should I decline the update?

 

c) I decline it, when they release a new version will I get it back in WSUS (different version number or something)?

 

EDIT: First time I've had to do this in WSUS...

 

2nd EDIT: d) What happens on machines that have it downloaded and it is pending install...?

Edited March 11, 2021 by Koldov

[caffrey]

a) Yes

b) Yes (Well I did)

c) Yes it'll probably be a new KB

 

not sure of the last one, in theory once declined and they recheck for updates it should dissapear

[petben]

Hello - does anyone have a PowerShell/command line way of removing these KB500082 and 58 updates at startup?

 

wusa /unintall doesnt work anymore with /quiet so it will hang

 

PowerShell ideas on web involve the dism command which doesn't run at startup...

 

 

 

any ideas?

[Boredguy]

For 1909 Windows 10 clients, we are using this powershell script via SCCM and it's working well

 

DISM.exe /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.1440.1.7

 

(Oh this is just to remove 5000808 as thats the only one thats stopped our printer issue due to BSoD)

[petben]

DISM.exe /Online doesnt work as startup script. we don't have SCCM.

[Boredguy]

DISM.exe /Online doesnt work as startup script. we don't have SCCM.

 

Try it with the following in front of it, as it seems to work for the other schools in our MAT without SCCM

 

start /wait /min DISM.........

[petben]

that still hangs, I dont think you can run DISM at startup.

[Boredguy]

Your other option is to use it in a logon script if it's not working for you as a start up script.

[petben]

That might work, it’s a shame there’s not a startup option, it takes ages to remove. Did u check your non sccm schools?

[Boredguy]

Believe the other schools have resolved it, we have Impero so it's easy to bulk logon all the stations if needed to get the logon script to run

[_techie_]

It was kb5000822 for us.

Removing via script seems to have killed most of it, let's hope tomorrow is more stable.

[petben]

What script did you use? How did u deploy it?

[mavhc]

For 1909 Windows 10 clients, we are using this powershell script via SCCM and it's working well

 

DISM.exe /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~18362.1440.1.7

 

(Oh this is just to remove 5000808 as thats the only one thats stopped our printer issue due to BSoD)

 

For 20xx:

 

DISM.exe /Online /Remove-Package /PackageName:Package_for_RollupFix~31bf3856ad364e35~amd64~~19041.867.1.8

 

Weirdly and I copied and pasted your line it had an extra space before ~amd

[petben]

Thanks - how did you bulk/remotely run that command on your machines?

[DrCheese]

It set it as a startup script and told staff to reboot once, wait 10 minutes then reboot again.

 

I stopped netsupport powering off our machines in the evening & just en mass rebooted any computers left on twice late at night - Dirty way of doing things, but it got the job done.

[petben]

That’s very strange I tried this many ways, I found dsim /online just hung at startup, there seemed to be a service that it relied on not running at startup, this was quite well documented online. Do you have any other commands running that would explain how you ran this successfully?

[zaibshah]

Hello,

I would love to share my experience regarding this security patch update issue which is occurred in latest update on 11th March, 2021.

 

We have Printonix P7000 dot matrix printer and the same issue had occurred on some of our end users (PC automatically restarts while clicking on print button).

 

Follow the steps to get rid of this issue:

 

- Uninstall security patch -which caused problem with printing and office products (KB5000802)

wusa /uninstall /kb:(Patch number)

Example: wusa /uninstall /kb:5000802

- Delete the printer driver

- Reboot the machine

- Reinstall printer driver and software

 

Windows 10 Pro

 

It had worked for me and now working fine.

[mavhc]

Some workarounds are now available, a) Set direct printing should fix it for 32 bit apps on 64 bit OS, b) something more complicated for 64 bit apps, c) switch to Type 4 printer drivers

 

https://docs.microsoft.com/en-us/windows/release-health/status-windows-10-20H2#1570msgdesc

[KK20]

we got round it by swapping our up to date modern kyocera drivers with a 15 year old XP driver (papercut went a bit mad with the v4 driver). That worked just fine. I say XP driver, it had a folder for "legacy OS" as well as the XP driver....