topic Re: Printer not responding, running Windows 11. in Office Printers

Printer not responding, running Windows 11.

Bobsacerdo — Wed, 05 Jan 2022 22:23:16 GMT

I am using a Dell XPS 15 7000 series laptop running Windows 11. I have a MAXIFY MB5120 multifunction printer that worked with it perfectly until recently, when I started getting "printer not responding" messages. Both the computer and printer are connected to the same LAN, both show good signal strength. I tried all the usual things - restart the router, power off/on both printer and computer, disconnect/reconnect to LAN for both, using the the problem: Any other drivers or work-arounds I can use to correct this? Thanks., using Dell online diagnostics etc. No errors or malfunctions listed for either. I tried downloading and installing new printer driver, no effect. I did get an error message when downloading, couldn't find current update information, and I checked and found no driver listed for use with Windows 11. Dell says that is the problem: Any work-around, patch or alternate drivers that might address this?

Re: Printer not responding, running Windows 11.

Bobsacerdo — Wed, 05 Jan 2022 22:26:17 GMT

NOTE: Somehow when I posted this, some words got out of order. The relevant point garbled, I have run the troubleshooter, it didn't identify the problem.

Re: Printer not responding, running Windows 11.

shadowsports — Thu, 06 Jan 2022 14:28:47 GMT

Greetings,

Was the printer installed and working under windows 10, then you upgraded to Windows 11?

Drivers for W11 are available:

Support | Small Office / Home Office Printers | MAXIFY MB5120 | Canon USA

https://pdisp01.c-wss.com/gdl/WWUFORedirectTarget.do?id=MDEwMDAwNzMzMjAz&cmp=ABR&lang=EN

I suggest you uninstall the printer, and remove all Canon software.

Restart

Now use the file above to reinstall the printer.

Re: Printer not responding, running Windows 11.

Bobsacerdo — Thu, 06 Jan 2022 16:21:48 GMT

Thanks - Indeed the printer was installed under W10, I upgraded to W11, it worked for several months then quit responding. I'll go there and get the new driver package. That said, I decided to give it one last try and removed/reinstalled again - and it worked. The only difference was this time I installed using the IVP4 address rather than a different approach. For whatever reason that did the trick.