Skip to content

Why did scan to folder stop working after a Windows update?

  • Home
  • Blog
  • Why did scan to folder stop working after a Windows update?
Why did scan to folder stop working after a Windows update?
Short answer

If a multifunction printer’s “scan to folder” (SMB) feature stopped after a Windows update or a move to Windows 11 24H2, the device is most likely connecting in a way Windows no longer accepts: SMBv1, an unsigned SMB session, guest (no user) access or NTLMv1. The right fix is not to turn SMBv1 back on; it is to update the device firmware so it supports SMB2/SMB3 and signing, and to configure a password-protected account used only for scanning.

Symptoms: scan to folder fails one morning

  • The copier scans the page, but at the sending stage it shows a message such as “cannot connect to server”, “SMB connection error” or “authentication error” (the wording depends on the brand).
  • The problem began right after a Windows update, an upgrade to Windows 11 24H2 or moving the scan folder to a new Windows 11 PC.
  • The same shared folder can be reached without problems from another Windows computer.
  • On the Windows side, connecting to the old device may show: “You can’t connect to the file share because it’s not secure. This share requires the obsolete SMB1 protocol…”
  • With a signing problem a Windows client may report “0xc000a000 / STATUS_INVALID_SIGNATURE – The cryptographic signature is invalid.”; with guest access you may see “You can’t access this shared folder because your organization’s security policies block unauthenticated guest access.”

Root cause: Windows changed its SMB security defaults

During scan to folder, the copier is the SMB client and the Windows computer that receives the file is the SMB server. What matters, therefore, are the rules the computer hosting the share applies to incoming connections. Microsoft has tightened these rules in four places over the years:

  1. SMBv1 is not installed: according to Microsoft Learn, a clean installation of Windows 11 contains neither the SMBv1 server nor the client; the same applies to Windows Server 2019 and later. On in-place upgrades of Windows 10 Home/Pro, SMBv1 is removed automatically if it is not used for 15 days in total. An old device that only speaks SMBv1 cannot connect at all in this case.
  2. SMB signing is required: Windows 11, version 24H2 Enterprise, Pro and Education require signing for both outbound and inbound SMB traffic. Windows Server 2025 requires outbound signing only by default, and 24H2 Home requires neither. An old scanner without signing support cannot write to a share on a Windows 11 24H2 Pro computer.
  3. Guest access is off: Windows has long blocked inbound guest access. Required signing also effectively blocks guest sessions, because a guest session cannot be signed. Scan profiles set up with an empty user name and password therefore fail.
  4. NTLMv1 has been removed: according to Microsoft’s feature lifecycle records, NTLMv1 is removed starting in Windows 11, version 24H2 and Windows Server 2025. Very old device firmware that authenticates only with NTLMv1 cannot sign in.

The most common picture in practice: the scan folder is moved to a Windows 11 24H2 Pro computer, while the copier firmware has not been updated for years and supports neither SMB signing nor SMB2/3.

Telling the causes apart quickly

  • If the device menu only offers “SMB” or “SMB 1.0”, or its firmware has not been updated for close to a decade, suspect SMBv1 first.
  • If scanning works to a Windows 10 or Windows 11 Home computer on the same network but not to a 24H2 Pro computer, the problem is most likely signing.
  • If the user name and password in the scan profile are empty, you are hitting the guest access block.
  • If you only get an authentication error although the user name and password are correct, ask the manufacturer whether the device uses NTLMv1.

Step-by-step fix

  1. Identify the Windows edition and build number of the computer hosting the share.
  2. On the same computer, read the SMBv1 status and the signing requirement (commands below). If RequireSecuritySignature is True, signing is required for incoming connections.
  3. On Windows 11 24H2 or Windows Server 2025, temporarily enable SMB server auditing to see clients that do not support signing. Events appear under “Applications and Services Logs > Microsoft > Windows > SMBServer > Audit” with IDs 3021 and 3022. If the copier’s IP address shows up there, the problem is signing.
  4. In the copier’s management web interface, check the firmware version, the SMB version setting and the authentication method. Install current firmware from the manufacturer’s support site that supports SMB2/SMB3 and SMB signing; if these are separate options on the device, enable them.
  5. On the share computer, create a local user (or domain account) with a strong password that is used only for scanning. Give it share and NTFS write permission on the scan folder only; do not make it an administrator.
  6. Enter that user name and password in the copier’s scan profile. Where possible use the computer name rather than the IP address in the path: Microsoft notes that connecting by IP address uses NTLM instead of Kerberos.
  7. Run a test scan, check the audit log again and then turn auditing off.
# Windows edition and build number
Get-CimInstance Win32_OperatingSystem | Select-Object Caption, Version, BuildNumber

# SMBv1 and inbound signing requirement
Get-SmbServerConfiguration | Format-List EnableSMB1Protocol, RequireSecuritySignature
Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

# Temporary audit: log clients that do not support signing (elevated PowerShell)
Set-SmbServerConfiguration -AuditClientDoesNotSupportSigning $true
Get-WinEvent -LogName 'Microsoft-Windows-SMBServer/Audit' -MaxEvents 20

# Turn auditing off after testing
Set-SmbServerConfiguration -AuditClientDoesNotSupportSigning $false

Quick fixes found online usually suggest re-enabling SMBv1, disabling signing with Set-SmbServerConfiguration -RequireSecuritySignature $false or enabling guest access. Microsoft recommends none of them: SMBv1 has known security issues related to ransomware and other malware, and disabling signing opens the door to relay and adversary-in-the-middle attacks. Even if the device cannot be updated, consider these settings only on the single machine hosting the scan folder, temporarily and with the risk understood, never across all company computers.

If the device cannot be updated at all

If the manufacturer no longer offers SMB2/3 or signing support, Microsoft’s recommendation is to update or replace the device. In the meantime you can use scan to email, scan to USB or another transfer method the device supports. Re-enabling SMBv1 should be considered only when no other option remains, when the manufacturer explicitly requires it, and only on that one machine.

Permanent prevention

  • Keep a maintenance schedule that checks the firmware of copiers, printers and NAS devices before every Windows version change.
  • Before a fleet-wide move to Windows 11 24H2, enable SMB auditing on a pilot computer and list the devices that do not support signing.
  • Do not use guest (no user) profiles for scanning; use a separate, limited, password-protected account for each device.
  • Consider keeping the scan folder on an up-to-date file server or NAS instead of a personal computer.

When should you call a specialist?

When several copiers, domain policies and different Windows versions are involved, working out which device is rejected for which reason and fixing it without weakening security takes time. For problems like these, which we encounter in the field at businesses in Denizli, Workas reviews the audit logs, updates device firmware and rebuilds the scan accounts with the correct permissions as part of its system maintenance and support service. For emergencies we respond with priority during working hours.

Frequently Asked Questions

Will re-enabling SMBv1 fix the problem?

It may work temporarily if the device only supports SMBv1, but Microsoft strongly advises against it. Update the device firmware to support SMB2/SMB3 first.

Why does scanning to Windows Server 2025 work but not to Windows 11 24H2 Pro?

By default Windows Server 2025 requires signing for outbound SMB traffic only, while Windows 11 24H2 Pro also requires it for inbound traffic. A scanner without signing support is therefore rejected only by the 24H2 Pro computer.

Do I need an administrator account for scanning?

No. A separate account with a strong password and write permission on the scan folder only is enough and safer.

Does this also happen on a Windows 11 Home computer?

Windows 11 24H2 Home does not require signing, but the missing SMBv1, guest access and NTLMv1 restrictions still apply there.

Sources

  1. Microsoft Learn: Control SMB signing behavior
  2. Microsoft Learn: Overview of Server Message Block signing in Windows
  3. Microsoft Learn: SMBv1 not installed by default in Windows Server and Windows
  4. Microsoft Learn: Enable insecure guest logons in SMB2 and SMB3
  5. Microsoft Learn: Deprecated features in the Windows client (NTLM)

Let's Get Started

Let's Work Together!

Let's plan your company's IT needs together — we'll quickly find the right solution for you.

x

Since 2002, Workas Software Technology has provided businesses in Denizli with ERP, cybersecurity, network, server and backup, custom software and AI solutions.

Address
Kınıklı, Hüseyin Yılmaz Cd. No:67,
B Blok Z06, 20160 Pamukkale/Denizli, Türkiye
Get in Touch
0549 669 99 06
0535 089 29 29
Working Hours
Mon - Sat: 8:00 - 18:00