(error 0x000007d1) on Printer

Anonymous
2018-05-22T09:36:01+00:00

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]

Windows for home | Windows 10 | Devices and drivers

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 No comments
Answer accepted by question author
Anonymous
2018-06-20T01:02:32+00:00

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:

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

Workaround:

  1. Press windows key + R. Type 'regedit' in the Open box, and then click OK.
  2. Locate, and then click the following registry subkey if it exists: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\PostSPUpgrade
  3. On the Edit menu, click Delete, and then click Yes to confirm the removal of the PostSPUpgrade registry key.
  4. 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.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2018-06-12T00:38:21+00:00

Hi Everyone,

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

NOTE:

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

Workaround:

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

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2020-02-28T18:54:02+00:00

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.

Was this answer helpful?

0 comments No comments

141 additional answers

Sort by: Oldest
  1. Anonymous
    2018-08-19T00:07:55+00:00

    Hi - I deleted the "offending" Microsoft update and returned my system to the day before the update installed.  My printer began working again and I have not had further problems.  I noticed the other day that I received some Microsoft updates but the printer is still working.  Somewhere on this thread is a reply that explains which update to delete and how to restore your system.  Good luck!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2018-08-19T16:19:34+00:00

    I agree with you wholeheartedly. Microsoft **** the bed with this update. They should have come out with another update that fixed the problem. Maybe they did, but I didn't see it.

    Piss poor quality control.

    Was this answer helpful?

    0 comments No comments