Also, to get the old toolbox uninstalled, I had to reboot into safe mode. Otherwise the uninstaller just hung. Then booted back into regular mode, removed all traces of the existing printer, then reinstalled the new software and it works great.
I have a MF212w printer. I have a new computer with windows 10 was having problems with the scanner. I called Canon customer service and spoke with a very nice and helpful man. Wfindows 10 wasnt compatable with my scanner and he walked me through uninstallng and reinstalling the new drivers to fix the problem. My suggestion is to call Canon customer service they helped me and I'm sure they will help anyone with the same problem
I had previously tried running the MF Toolbox as an admin (compatibility, all users, as someone else here mentioned) but the problem according to procmon was that mf network scan wasn't able to fire off MF Toolbox. Tried UAC, etc, nothing. That's when it occurred to me it wasn't mf toolbox for me, it was the network scan.
Some incompatibility, when some other software felt the need to update a boatload of .NET assemblies or virtual engines or redistributables, and it's broken. Now, the toolbox doesn't know what scanner it's talking to. Probably because some WSDL XML got screwed with and the RPCs are all messed up...
Hi. I'm at my wit's end with this. I've used VS2017 for years, it was mostly solid. Just a few little quirks. I recently installed 2019 Community so I could use .NET 5 and it's nothing but headache after headache. It's laggy, has a lot more quirks (like toolbox taking 30+ seconds to load, component properties blank, last opened class totally blank when opening a project, etc) but the most aggravating is constant crashing. I've lost so much work to it. It crashes and in the event log I have two errors:
760c119bf3