Windows 10 BSOD When Printing
-
@Dashrender Same issue for my office this morning. Good news is that uninstalling the update took care of it.
-
Today, I got confirmation that this same KB is effecting DYMO label printers. They have a working version of the DYMO LabelWriter software out, but not the DYMO Connect software we use.
-
@travisdh1 said in Windows 10 BSOD When Printing:
Today, I got confirmation that this same KB is effecting DYMO label printers. They have a working version of the DYMO LabelWriter software out, but not the DYMO Connect software we use.
What software did you find that is compatible? I don't see a new version of Windows based Dymo Labelwriter software...
-
Dymo's post about the problem.
-
@Dashrender said in Windows 10 BSOD When Printing:
Dymo's post about the problem.
Removing the update didn't work for us. Still getting blank labels. Monday I'll check if that software from that article is a working version of DYMO Connect.
They've had a working version of the DYMO LabelWriter software out, but that doesn't provide an API that a website can use to print labels with, which is what this client uses the printers for.
-
@travisdh1 said in Windows 10 BSOD When Printing:
@Dashrender said in Windows 10 BSOD When Printing:
Dymo's post about the problem.
Removing the update didn't work for us. Still getting blank labels. Monday I'll check if that software from that article is a working version of DYMO Connect.
They've had a working version of the DYMO LabelWriter software out, but that doesn't provide an API that a website can use to print labels with, which is what this client uses the printers for.
The uninstall has worked the the crappy new version Dymo has...
That said, version 8.x is the only version that works with our software,
-
@travisdh1 said in Windows 10 BSOD When Printing:
@Dashrender said in Windows 10 BSOD When Printing:
Dymo's post about the problem.
Removing the update didn't work for us. Still getting blank labels. Monday I'll check if that software from that article is a working version of DYMO Connect.
They've had a working version of the DYMO LabelWriter software out, but that doesn't provide an API that a website can use to print labels with, which is what this client uses the printers for.
We've had to fix this over 200 times this past week.
WHEN IT INVOLVED A PC WITH ONLY a DYMO, not every case had the KB5000802 update, so we just stopped removing that update and went straight to this process every time. It had work every time for us. If there was a Dymo AND a Kyocera, we continued removing KB5000802.
- BACKUP UP YOUR Labels if you created any labels with a newer version of Dymo. 8.5.4 will not see than, but it will delete them.
- Unplug the USB Cable from the Dymo.
- Uninstall Dymo Software.
- Load Print Management and remove the Dymo Driver and Package.
- Restart the PC.
- Open Print Management again and WAIT for the DYMO driver to go away (can take up to 3 minutes after the reboot in our experience).
- Open Device Manager, Expand Printers and make sure the Dymo is gone from the Printers area.
- Install Dymo 8.5.4
- Plug USB cable back in.
This procedure has work every single time on more than 200 workstations this week.
-
Came in this morning to several end users that with kb:5000802 re-installed. I though MS took it down?
There is a PSWindowsUpdate module that can be used to block a single update, but it comes from Microsoft Gallery with is user populated and not verified by MS. So I m looking for another command-line-only wau to block KB5000802
If you're a brave soul, or want to go verify the module yourself, here are the commands:
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
Install-Module PSWindowsUpdate
Install-WindowsUpdate -NotKBArticle "KB5000802" -AcceptAll -
@JasGot said in Windows 10 BSOD When Printing:
@travisdh1 said in Windows 10 BSOD When Printing:
@Dashrender said in Windows 10 BSOD When Printing:
Dymo's post about the problem.
Removing the update didn't work for us. Still getting blank labels. Monday I'll check if that software from that article is a working version of DYMO Connect.
They've had a working version of the DYMO LabelWriter software out, but that doesn't provide an API that a website can use to print labels with, which is what this client uses the printers for.
We've had to fix this over 200 times this past week.
WHEN IT INVOLVED A PC WITH ONLY a DYMO, not every case had the KB5000802 update, so we just stopped removing that update and went straight to this process every time. It had work every time for us. If there was a Dymo AND a Kyocera, we continued removing KB5000802.
- BACKUP UP YOUR Labels if you created any labels with a newer version of Dymo. 8.5.4 will not see than, but it will delete them.
- Unplug the USB Cable from the Dymo.
- Uninstall Dymo Software.
- Load Print Management and remove the Dymo Driver and Package.
- Restart the PC.
- Open Print Management again and WAIT for the DYMO driver to go away (can take up to 3 minutes after the reboot in our experience).
- Open Device Manager, Expand Printers and make sure the Dymo is gone from the Printers area.
- Install Dymo 8.5.4
- Plug USB cable back in.
This procedure has work every single time on more than 200 workstations this week.
Used that this arvo to great success
-
@JasGot said in Windows 10 BSOD When Printing:
Came in this morning to several end users that with kb:5000802 re-installed. I though MS took it down?
There is a PSWindowsUpdate module that can be used to block a single update, but it comes from Microsoft Gallery with is user populated and not verified by MS. So I m looking for another command-line-only wau to block KB5000802
If you're a brave soul, or want to go verify the module yourself, here are the commands:
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
Install-Module PSWindowsUpdate
Install-WindowsUpdate -NotKBArticle "KB5000802" -AcceptAllI used the guide here as a base
DISM.exe /Online /Remove-Package /PackageName:$package /quiet /norestartTo find the packagename, I used
dism /online /get-packages /format:tableThen I dropped that into a task sequence and deployed via MS Config Manager... allowing users to rerun it.
Not perfect but it got us out of a jam while we tested the Kyocera XPS drivers... which have brought their own set of interesting issues -
Windows 10 2004 - KB5000802 was also causing BSOD when opening a PDF file in Adobe Illustrator.
Confirmed removal resolved the issue.
-
-
Looks like this update fixed my BSOD for Kyoceria printers.
Tested and didn't die.
-
@Dashrender said in Windows 10 BSOD When Printing:
Looks like this update fixed my BSOD for Kyoceria printers.
Tested and didn't die.
Did you uninstall the "faulty" update first?
Also did you get the fix one from Windows update or a standalone download? -
@hobbit666 said in Windows 10 BSOD When Printing:
@Dashrender said in Windows 10 BSOD When Printing:
Looks like this update fixed my BSOD for Kyoceria printers.
Tested and didn't die.
Did you uninstall the "faulty" update first?
Also did you get the fix one from Windows update or a standalone download?err... I can't recall if the faulty update was removed first. From what I can tell, you're not supposed to need to remove it though.
As for where did I get it? It came from Windows Update.
KB5001566 - v1909
-
@Dashrender said in Windows 10 BSOD When Printing:
As for where did I get it? It came from Windows Update.
KB5001566 - v1909
Saw the first one on a server this morning
-
@hobbit666 said in Windows 10 BSOD When Printing:
@Dashrender said in Windows 10 BSOD When Printing:
As for where did I get it? It came from Windows Update.
KB5001566 - v1909
Saw the first one on a server this morning
LOL and RDS server I hope - otherwise I'm hoping that printing from a server isn't a big deal...(save a print server)
-
@Dashrender said in Windows 10 BSOD When Printing:
LOL and RDS server I hope - otherwise I'm hoping that printing from a server it's a big deal...(save a print server)
Yeah RDS server
-
@JasGot said in Windows 10 BSOD When Printing:
Came in this morning to several end users that with kb:5000802 re-installed. I though MS took it down?
There is a PSWindowsUpdate module that can be used to block a single update, but it comes from Microsoft Gallery with is user populated and not verified by MS. So I m looking for another command-line-only wau to block KB5000802
If you're a brave soul, or want to go verify the module yourself, here are the commands:
Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
Install-Module PSWindowsUpdate
Install-WindowsUpdate -NotKBArticle "KB5000802" -AcceptAllWe've reached the point where it is often safer to trust random unverified strangers on the Internet than something signed by Microsoft!
-
@hobbit666 in one instance we had to install the fix as @Dashrender posted and it worked.
The update does take a long time to update though.
