Why Scan to Folder Fails on SMBv1-Only MFPs in Windows 11

Quick fix: Windows 11 disables SMBv1 by default. Older multifunction printers that scan via SMB still use it. Re-enable SMBv1 client only via Control Panel → Programs and Features → Turn Windows features on or off → SMB 1.0/CIFS File Sharing Support → SMB 1.0/CIFS Client. Don’t enable the server component — it’s a known security risk.

Your office printer/scanner has a Scan to Folder feature where it writes scanned documents directly to a shared folder on a PC. It worked on Windows 10. On Windows 11, the printer reports a connection error. The protocol that printer uses — SMBv1 — is disabled by default in Windows 11 because of WannaCry-era vulnerabilities.

What SMBv1 is and why it’s disabled

SMB1 (and the CIFS protocol it’s based on) was the file-sharing protocol from the 90s/early 2000s. It has well-known vulnerabilities (EternalBlue, used in WannaCry). Modern protocols (SMB2/SMB3) are secure and faster, but older devices that haven’t been updated still use SMB1 exclusively. Windows 11 removes the server-side SMB1 entirely; the client-side can be re-enabled if you need to connect to old SMB1-only servers (note: this is backwards from the typical printer scenario, where the printer is the client writing to your share).

For Scan to Folder where the printer sends data to your Windows share, the relevant component is the SMBv1 server on Windows. Re-enabling it is risky.

Method 1: Update printer firmware (preferred)

1. Check the printer manufacturer’s site for firmware updates that add SMBv2/v3 support.
2. Many MFPs released in the last 5 years have firmware that supports SMBv2 — install it.
3. After firmware update, the scanner uses SMBv2/v3 against modern Windows.
4. This is the safe solution. No protocol downgrade.

Method 2: Use FTP or WebDAV instead of SMB

1. Many MFPs support multiple Scan to Folder protocols.
2. Set up an FTP server on Windows (via IIS or a lightweight FTP server like FileZilla Server).
3. Configure the printer to use FTP instead of SMB.
4. Alternatively, set up WebDAV (also via IIS).

Method 3: Re-enable SMBv1 server (risky, last resort)

1. Only do this if you can’t update the printer firmware and FTP isn’t practical.
2. Open Control Panel → Programs and Features → Turn Windows features on or off.
3. Scroll to SMB 1.0/CIFS File Sharing Support. Expand.
4. Check SMB 1.0/CIFS Server. Do NOT check “Automatic Removal.”
5. Click OK. Reboot.
6. The PC now accepts SMBv1 connections. The printer can scan to folder again.
7. Mitigate the risk: only allow SMB1 inbound from the printer’s IP via Windows Firewall, not from the whole network.

How to verify the fix worked

• Test Scan to Folder from the printer. Document arrives in the target share.
• If using Method 1/2: protocol is SMBv2 or FTP, not SMBv1.
• If using Method 3: Get-SmbServerConfiguration | Select EnableSMB1Protocol shows True.

If none of these work

If the printer absolutely cannot use anything but SMBv1 and you don’t want SMBv1 server enabled, dedicate an old PC or a Raspberry Pi running Samba to be the scan destination, isolated from your main network. Scan-and-forward is a common compromise. For chronic legacy device issues, consider buying a modern MFP — entry-level multifunction printers with SMB2/v3 cost under $400.

Bottom line: SMBv1 is a security risk. Update the printer firmware or switch to FTP. Re-enable SMB1 server only as a last resort, scoped to the printer’s IP via firewall.