(error 0x000007d1) on Printer

Anonymous

Hello;

Since I have updated to the new version 1803, my Brother's HL-L2340DW Mono Laser printer will not print, and receive this error code. I have uninstalled this drivers and program 3 time and reinstalled it. It is setup for wireless. It says that the printer is there and working, but no print. It says that it has a invalid driver. So, somewhere in your programming of 1803 version Microsoft had changed something. Because it used to work flawlessly. I don't think this is a Brother's driver problem, but a Microsoft drivers problem. Fix it please! I want my printer to work again. And don't tell me it is a Brother's problem when I know it all started with the version of 1803. This is a screen shot of the error code that I get. I was trying to print a test page.

Thank You

[Moved from: Windows / Windows 10 / Windows update, recovery, & backup]

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

Answer accepted by question author

Anonymous

I did this and it fixed the problem.

Hi Everyone,

Engineering has asked for you guys to try the following workaround to see if it fixes your issue:

NOTE:

Please submit feedback on Feedback Hub before trying this workaround
Please reply/mark this as helpful if you it works for you

Workaround:

Press windows key + R. Type 'regedit' in the Open box, and then click OK.
Locate, and then click the following registry subkey if it exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PostSPUpgrade
On the Edit menu, click Delete, and then click Yes to confirm the removal of the PostSPUpgrade registry key.
Restart your PC (OR run ‘net stop spooler’ followed by ‘net start spooler’ from an elevated command prompt).

it finally worked after hours of attempts.

0 comments

Answer accepted by question author

Anonymous

Hi Everyone,

Engineering has asked for you guys to try the following workaround to see if it fixes your issue:

NOTE:

Please submit feedback on Feedback Hub before trying this workaround
Please reply/mark this as helpful if you it works for you

Workaround:

Press windows key + R. Type 'regedit' in the Open box, and then click OK.
Locate, and then click the following registry subkey if it exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PostSPUpgrade
On the Edit menu, click Delete, and then click Yes to confirm the removal of the PostSPUpgrade registry key.
Restart your PC (OR run ‘net stop spooler’ followed by ‘net start spooler’ from an elevated command prompt).

0 comments

Answer accepted by question author

Anonymous

Based on your post on printing, I think that the Microsoft Virtual Agent can help you troubleshoot your issue. It'll walk you through the right troubleshooting steps based on the specific problem you're facing.

Please let us know if this solved your issue.

0 comments

141 additional answers

Anonymous

2018-06-08T21:29:20+00:00

It is true that the Feedback hub takes time, but it is far from useless. The more logs created and sent to Microsoft ahould allow for more eyes on the issue. If few people report it, Micorsoft will not see it as a big problem.

I do agree that the Printer Manufactures have little fault in this... the best option is to submit feedback and wait or roll back to 1709.
Was this answer helpful?

0 comments No comments
Anonymous

2018-06-11T11:39:57+00:00
Don't panic. Just:

ignore the guidelines of MS guy, they are not connected with reality and therefore useless

search for the Feedback Hub with the search tool and follow your intuition

you might as well sit back and relax as I sent the feedback via FH 2 weeks ago with no result whatsoever

I happen to have an older computer with Win8 and it works perfectly fine, so printer and its manufacturer really have no fault.

Good luck!
You know what is funny. Did do a search for it on windows. Wasn't in my system. Had to go to the MS Store and download it. Followed everything sent the feedback to Microsoft about.

Thanks for all your help. And I really don't want to roll back to 1709 now. Just, hope that Microsoft will listen to what people are saying that they did a major screw up somewhere down the line.
Was this answer helpful?

0 comments No comments