Also Brother QL-700 Label Printer has the same problem. Rolled back to previous build, Ok now
Printer Troubleshooting on Build 21354
For information to everyone:
It’s disable to use printer HP LaserJet M1132 MFP after upgrading to build 21354.1: Printer is missing in the Device Manager, Settings/Printers & Scanners shows “HP LaserJet M1132 MFP Offline”, Print Queues shows the documents sent for printing, but printing doesn’t run. Troubleshooter Windows does not detect any problem. Returning to the build 21343.1000 resolves the trouble.
Feedback https://aka.ms/AAbw91b
Windows Insider program | Windows Insider preview | 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.
50 answers
Sort by: Newest
-
Anonymous
2021-04-10T00:01:55+00:00 -
Anonymous
2021-04-09T21:16:35+00:00 Question; You said that the printer did not work under 21354 but did under 21343. Did you compare the driver for the printer in Device Manager on each build?
@lacrumb,
Yes, they changed the usbprint.sys driver and also the spoolsv.exe, by doing that they screwed up, some USB printers are no longer working with 21354 while they work fine with 21343 or any previous build.
-
Anonymous
2021-04-09T20:10:30+00:00 Hopefully, Microsoft will solve the problem in the next builds?
I don't know the answer to this question, in the meantime we should try to understand if the Microsoft engineers or developers are aware of the problem and how long it will take to fix the bug
If you compare usbprint.sys in build 21343 versus the one in 21354 you can see that they are completely different and they seem to have dropped the support for some types of USB printers.
Also you cannot save the printer properties settings because the parameters they prepare are incorrect.
The spoolsv.exe is also changed.
It looks like opening a can of worms 😜
-
Anonymous
2021-04-09T19:58:46+00:00 Question; You said that the printer did not work under 21354 but did under 21343. Did you compare the driver for the printer in Device Manager on each build?
-
Anonymous
2021-04-09T15:38:55+00:00 Hopefully, Microsoft will solve the problem in the next builds?
I don't know the answer to this question, in the meantime we should try to understand if the Microsoft engineers or developers are aware of the problem and how long it will take to fix the bug