I'm still in the middle of dealing with my oldest son's passing and many of the documents I need to print out, sign, etc. But everytime I do and no matter what tweaking I've tried the computer shuts down hard. The printer will still spit out what I need but I always have to reboot and sometime try to recover things.

Anyone know WTH I can do to fix this crap? It happened early last year too for some if memory serves but a patch to fix it was issued.



Printer is a Brother DCP-L2540DW cable connected to the desktop.

quote:

Originally posted by bald1:
I'm still in the middle of dealing with my oldest son's passing and many of the documents I need to print out, sign, etc. But everytime I do and no matter what tweaking I've tried the computer shuts down hard. The printer will still spit out what I need but I always have to reboot and sometime try to recover things.

Anyone know WTH I can do to fix this crap? It happened early last year too for some if memory serves but a patch to fix it was issued.



Printer is a Brother DCP-L2540DW cable connected to the desktop.

Restore back to an earlier known good point or uninstall the 21H1 update.Or try looking at this article. https://higher-yearning.org/ho...dows-10-21h1-update/

You need to cruise over to the Brother support page.
Maybe confirm your driver, firmware and or software.
Usually it's a driver or the printer port us wrong.

I would try to reinstall the driver before you try restore points and uninstalling windows updates. The only thing I would add to what smschultz said is to uninstall your current driver first and any other printer drivers you aren't using. Reboot, and then install the latest driver.

You can also try to flip this setting to off.

Uninstalled everything for that printer using a Brother utility from their web site. Reinstalled the whole suite including drivers.

Same shit... doesn't matter if it is jpg, pdf, text file, whatever... go to print it and the computer shuts down hard. But the printer still spits out the task given.

Grrrrrrrrrrrrr

Searches indicate this has been an issue on and off with Win10 but I can't find a solution that works.

Plus as said I'm still dealing with my recently deceased son's related issues. As an aside it was a huge shit show with the storage units and van lines today in southern Kali. Ended up having to cancel and regroup. Don't ask....

So time spent here is critical and a much lower priority than that needed for my son.

quote:

Originally posted by bald1:
Printer is a Brother DCP-L2540DW cable connected to the desktop.

By "cable connected" do you mean using USB 2? If so: This may be a long shot, because it does sound like a printer driver problem, but perhaps try networking it, either via Ethernet (wired, preferred) or WiFi and taking to it that way?

Is your MS-Win10 system up-to-date wrt patches?

<rant>Why a flippin' printer driver is running wired so-tightly into the O/S it can crash it is beyond me.</rant>

Yes all Win10 updates have been made and are current.

Connection is via USB2 cable.

What? An ethernet cable to my router?

quote:

Originally posted by bald1:
What? An ethernet cable to my router?

Yeah. It'll probably be a PITA and I doubt it'll fix your problem, but I got nothing else. (N.B.: I'm not an MS-Win expert in the first place and I've never touched MS-Win10 at all.)

quote:

Brother DCP-L2540DW

A couple of things to check.
1. This is a MFC (multifunction printer) so be sure you are not accidently trying to print to the scanner.
2. Perhaps uninstall all the software and ONLY install the printer part.
3. Check which port the printer is connected to in your printer properties to make sure it is not point where it should not be.
3. Just in case it is a hardware issue plug into different USB port and/or change out the cable.
4. You could also connect via an ethernet cable if the printer has networking like ensigmatic said.

I've never seen any printer issues due to a Windows 10 update but you never know ~ you could check with other Brother support areas ~ my first intuition is that it is driver related ~ perhaps an older printer driver is available for rollback ~ you can also check in the Device Manager for the printer and roll back to an previous driver if in fact that is the problem.

Good Luck

quote:

Originally posted by smschulz:
A couple of things to check.
1. This is a MFC (multifunction printer) so be sure you are not accidently trying to print to the scanner.
3. Check which port the printer is connected to in your printer properties to make sure it is not point where it should not be.

Thing is: He's actually getting the print-outs, so these seem highly unlikely, no?

quote:

Originally posted by smschulz:
2. Perhaps uninstall all the software and ONLY install the printer part.
3. Just in case it is a hardware issue plug into different USB port and/or change out the cable.

Yeah, these would both be very easy to do. Much easier than...

quote:

Originally posted by smschulz:
4. You could also connect via an ethernet cable if the printer has networking like ensigmatic said.

... this ^^^^^

This seems to be the problem. Info I received from a friend.
https://www.reviewgeek.com/913...tmare-vulnerability/

FTA:
Microsoft has issued an emergency Windows update to patch the PrintNightmare vulnerability, which allows hackers to take over PCs through the Print Spooler system. This update covers a wide range of Windows operating systems, including Windows 7, which exited Microsoft’s security update cycle late last year.

Update, 7/7/21 4:31 pm Eastern: It turns out that this patch is somewhat useless. As reported by Bleeping Computer, hackers can easily gain SYSTEM privileges on older machines by leveraging PrintNightmare’s local privilege exploit component. On newer machines, hackers simply need to enable the Point and Print Restrictions policy to bypass Microsoft’s patch, which is a small hurdle for someone who really wants to gain control of a PC or network.
For the time being, the only way to defend yourself from PrintNightmare is to disable the Windows Print Spooler—Microsoft’s Security Response Center has a step-by-step guide on this subject. We will continue to report on the PrintNightmare exploit as new information comes to light.

Yet another Windows Update issue!

More Info...

https://www.windowslatest.com/...-10-printing-issues/

https://www.bleepingcomputer.c...atch-tuesday-update/

https://docs.microsoft.com/en-...-10-20h2#1647msgdesc

The issue may be associated with KB5004945 (installed 7/6/21), which was supposed to be fixed by KB5004237 (installed 7/13/21), but apparently not in your case. The issue seems to specifically affect many printers connected via USB Cable.

From the WindowsLatest link:

"On July 6, Microsoft released the emergency security updates to supported Windows 10 versions. While the updates brought the important bug fixes for PrintNightmare vulnerability, several users began reporting printing failures and Blue Screen of Death errors.

The bug – supposedly introduced with three cumulative updates (KB5003690, KB5004760 and KB5004945) affects Windows 10 versions 21H1, version 20H2, and version 2004 (May 2020 Update). It causes issues when printing documents and Blue Screen of Death crashes in the worst case."

I don't have your answer, but this is the problem. Sorry I couldn't be of more help.

kb5003690 update gave my Dell the BSOD. Uninstalled, fixed issue. Then it installed itself. Did a Restore to an earlier date. No issues. kb5003690 reinstalled itself, no issues since.

Have you tried turning off the print spooler? Even if the problem isn’t PrintNightmare, it sounds like the problem could be with the spooler.

Open the Start menu.
Search for “PowerShell.”
Right-click on the result and select the “Run as administrator” option.
Paste the below command and press Enter.
Stop-Service -Name Spooler -Force
Next, type the below command and press Enter.
Set-Service -Name Spooler -StartupType Disabled
Close the PowerShell window.
Restart the computer.

quote:

Originally posted by sigcrazy7:
Have you tried turning off the print spooler? Even if the problem isn’t PrintNightmare, it sounds like the problem could be with the spooler.

Open the Start menu.
Search for “PowerShell.”
Right-click on the result and select the “Run as administrator” option.
Paste the below command and press Enter.
Stop-Service -Name Spooler -Force
Next, type the below command and press Enter.
Set-Service -Name Spooler -StartupType Disabled
Close the PowerShell window.
Restart the computer.

Not that stopping will help but it might be easier just to go to the Services GUI (search services > find Print Spooler) and stop it or restart it.

quote:

Originally posted by smschulz:
Not that stopping will help ...

At this point, were I him, I'd be ready to try about anything.

Here's another idea: Assuming the printer will work with one, maybe he could try wiping out the printer--incl. un-installing Brother's stuff, and re-setting it up with a generic driver? Just to see if it'll print w/o crashing the computer.

If that works, and it doesn't crash the system, it might prove it is indeed the driver.

I don't know how that would help him, but at least then he'd know where to look.

Maybe.

quote:

Originally posted by smschulz:

quote:

Originally posted by sigcrazy7:
Have you tried turning off the print spooler? Even if the problem isn’t PrintNightmare, it sounds like the problem could be with the spooler.

Open the Start menu.
Search for “PowerShell.”
Right-click on the result and select the “Run as administrator” option.
Paste the below command and press Enter.
Stop-Service -Name Spooler -Force
Next, type the below command and press Enter.
Set-Service -Name Spooler -StartupType Disabled
Close the PowerShell window.
Restart the computer.

Not that stopping will help but it might be easier just to go to the Services GUI (search services > find Print Spooler) and stop it or restart it.

My understanding is using MSConfig to stop the process will not keep programs from starting it again, whereas stopping it in powershell prevents it from relaunching.

That printer supports postscript level 3. If I were in your situation, I'd try removing all Brother software, disabling the print spooler, and install a generic postscript or PCL6 driver, or perhaps only installing Brother's BR-Script driver. Or you should be able to use Adobe's PS driver, or a HP PCL6 driver. Or perhaps you could save your docs as PS files and send them directly to the printer without using any driver.

Been a long time since I dealt with this stuff. Just throwing out ideas.

quote:

Originally posted by sigcrazy7:

My understanding is using MSConfig to stop the process will not keep programs from starting it again, whereas stopping it in powershell prevents it from relaunching.

You can keep it from starting back up in the GUI services app as well if that is what you want.
I still don't see much benefit from stopping it permanently - you can't print with it stopped.

Maybe do a system restore to a time before the misbegotten Win 10 updates?

From nhracecaft's post above, if I had a valid system restore point made before July 5 I would try that. Those would be before those particular issues.