MF Toolbox can't connect to scanner over the network, but printing works: registry fix (imageCLASS MF212w / MF216n / MF217w, Windows 11)
Credit for this fix goes to Claude Code, Anthropic's AI coding assistant. After years of failed attempts, it tracked down the cause and fixed the problem on my laptop in about five minutes. Please do not write me for any further assistance. This fix was all Claude Code.
For years, MF Toolbox 4.9 on one of my laptops couldn't connect to my Canon imageCLASS scanner over the network, even though printing worked fine. Reinstalling the MF drivers and the network scan patch, and checking the firewall, never helped. The same scanner worked perfectly from a new identical laptop, so the problem had to be software on the old one.
These three models share one driver package and appear in Windows as "Canon MF210 Series," so that's the name you'll see below.
BEFORE YOU START: this fix edits the Windows registry. Step 3 shows how to back up first. Please don't skip it.
THE CAUSE
MF Toolbox finds the scanner by its device name, something like Canon MF210 ser_XXXXXXXXXXXX (the part after ser_ is the printer's MAC address). On the broken laptop, the scanner's entry in Windows had a blank name. Windows Image Acquisition (WIA) listed it as "No friendly name," so Toolbox could never match it, even though the scanner was reachable on the network.
This is only one cause of Toolbox scanning failures. Run the check in Step 1 first. If your scanner's name shows up correctly, this fix isn't for you, and there's no reason to edit your registry.
STEP 1: CHECK WHETHER YOU HAVE THIS PROBLEM
Open a normal PowerShell window (not "Run as administrator"), logged in to the Windows account you normally scan from, and run:
$dm = New-Object -ComObject WIA.DeviceManager
foreach ($d in $dm.DeviceInfos) { ($d.Properties | Where-Object Name -eq 'Name').Value }
On a working PC this prints something like Canon MF210 ser_XXXXXXXXXXXX. If it prints No friendly name (or a blank line) where your Canon should be, you have this problem.
STEP 2: FIND THE NAME TOOLBOX EXPECTS
In the same normal PowerShell window, run:
(Get-ItemProperty 'HKCU:\Software\Canon\SateraMFP1\Toolbox Ver4.9\Preferences').DataSource
Write down the exact result. Run this from your everyday account, not an admin window, because it reads the settings of whichever account is running PowerShell.
If it comes back empty or shows an error, run the Step 1 check on another PC that scans from the same printer successfully, and copy the name from there. If you don't have another PC, stop here rather than guessing the name.
STEP 3: BACK UP THE REGISTRY KEY
1. Press the Windows key, type regedit, and open Registry Editor.
2. Paste this path into the address bar at the top and press Enter:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{6BDD1FC6-810F-11D0-BEC7-08002BE2092F}
3. Click through the numbered subkeys (0000, 0001, and so on) and find the one whose DriverDesc says Canon MF210 Series. The number may be different on your PC.
4. Right-click that numbered key, choose Export, and save the file somewhere safe. If anything goes wrong, double-click this file to restore the original values, then restart your PC.
STEP 4: EDIT THE VALUES
Still in that numbered key, set these four String values, using YOUR name from Step 2. Double-click a value to edit it. If a value doesn't exist, right-click in the right-hand pane and choose New > String Value.
FriendlyName = Canon MF210 ser_XXXXXXXXXXXX
DriverDesc = Canon MF210 ser_XXXXXXXXXXXX
Vendor = Canon
DeviceID = {6BDD1FC6-810F-11D0-BEC7-08002BE2092F}\0000 (replace 0000 with the number of the key you're editing)
STEP 5: RESTART THE SCANNER SERVICE
Open PowerShell as Administrator and run:
Restart-Service stisvc -Force
Restarting your computer works too. Then close and reopen MF Toolbox. It found the scanner immediately for me.
IF IT STOPS WORKING LATER
A driver reinstall or a major Windows update can rewrite this registry key and blank the name again. If scanning breaks, run the Step 1 check again and reapply the fix if needed.
This worked for me on Windows 11, but your mileage may vary. Editing the registry is at your own risk, so please make the backup in Step 3 first.
