Thanks — that’s clear enough to move forward. Error 801 commonly means the scanner/MFP cannot reach or open the network share on the PC (i.e. “cannot connect to the file server”). That matches what I’ve seen after an in‑place repair of Windows 11 because such repairs often reset the network profile, firewall rules, SMB settings or share permissions.
I’ll give a short checklist you can follow now (fast checks first), then a recommended, safe script (copy/paste) to create a dedicated scan share + account and open the firewall rules. If you prefer I can walk you through each step interactively.
Quick checklist — try these first
- Confirm the target: are you scanning to a network folder on your PC (Scan to Folder / SMB)? Which model MFP/printer is it? (If not SMB, tell me how you scan — to email, to PC client, etc.)
- From the PC, confirm the server service and listening port:
- Run in an elevated PowerShell / CMD:
sc query LanmanServer
netstat -ano | findstr ":445"
If LanmanServer is not RUNNING or you don’t see port 445 LISTENING, the MFP can’t reach the SMB share.
- Check the network profile and firewall:
- Settings → Network & internet → your adapter → Network profile = Private
- Ensure File and Printer Sharing rules are enabled:
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes
- Confirm the UNC you configured on the MFP is correct:
- Use \PC-NAME\ScansD or \192.168.x.y\ScansD (use the PC’s LAN IP for testing to avoid name resolution problems).
- Test access from another machine (or the PC itself) using the same SMB creds your MFP uses:
- From CMD (run elevated): net use \PCNAME\ScansD /user
CNAME\scanuser_d <password>
- If that fails note the error (permission, path not found, network path not found).
- Make sure the PC isn’t sleeping and that the share folder exists and has correct NTFS + Share permissions for the account the MFP uses.
One-click safe fix (PowerShell, run as Administrator)
This creates a dedicated folder C:\ScansD, creates a local scan user, grants NTFS + share permissions and enables the File & Printer Sharing firewall rules. It’s reversible and a standard, secure approach for MFPs.
Important: run this in an elevated PowerShell window. You’ll be prompted for a password for the scan user.
Copy/paste-run (Admin PowerShell)
(If you prefer the one-line net commands instead I can list those — this PowerShell is more robust.)
Code:
# Run as Administrator
# 1) Create scan folder
$ScanFolder = 'C:\ScansD'
New-Item -Path $ScanFolder -ItemType Directory -Force | Out-Null
# 2) Create local scan account (you will be prompted for password)
$scanUser = 'scanuser_d'
Write-Host "Enter password for local user $scanUser"
$pass = Read-Host -AsSecureString "Password"
if (-not (Get-LocalUser -Name $scanUser -ErrorAction SilentlyContinue)) {
New-LocalUser -Name $scanUser -Password $pass -FullName "Scanner User" -Description "Account for MFP scan to folder" -PasswordNeverExpires:$false
Add-LocalGroupMember -Group 'Users' -Member $scanUser
Write-Host "Created local user $scanUser"
} else {
Write-Host "Local user $scanUser already exists — skipping creation."
}
# 3) Set NTFS permissions (Modify for the scan user)
$acct = "$env:COMPUTERNAME\$scanUser"
$acl = Get-Acl -Path $ScanFolder
$rule = New-Object System.Security.AccessControl.FileSystemAccessRule($acct,'Modify','ContainerInherit, ObjectInherit','None','Allow')
$acl.SetAccessRule($rule)
Set-Acl -Path $ScanFolder -AclObject $acl
Write-Host "Set NTFS Modify permission for $acct on $ScanFolder"
# 4) Create share and grant Change/Full as needed
if (-not (Get-SmbShare -Name 'ScansD' -ErrorAction SilentlyContinue)) {
New-SmbShare -Name 'ScansD' -Path $ScanFolder -FullAccess $acct
# Optionally limit share perms to change only:
Grant-SmbShareAccess -Name 'ScansD' -AccountName $acct -AccessRight Change -Force
Write-Host "Created SMB share \\$env:COMPUTERNAME\ScansD and granted access to $acct"
} else {
Write-Host "SMB share 'ScansD' already exists."
}
# 5) Ensure Server service is running
Start-Service -Name LanmanServer -ErrorAction SilentlyContinue
sc.exe query LanmanServer | Out-Host
# 6) Allow File and Printer Sharing through the firewall (Private profile)
netsh advfirewall firewall set rule group="File and Printer Sharing" new enable=Yes
# 7) Helpful tests for you to run from the MFP or another PC:
Write-Host "`nTest suggestions:"
Write-Host " - UNC to configure on MFP: \\$env:COMPUTERNAME\ScansD"
Write-Host " - Or use the PC IP: \\<PC-IP>\ScansD (run ipconfig to get IP)"
Write-Host " - Try from another PC: net use \\$env:COMPUTERNAME\ScansD /user:$env:COMPUTERNAME\$scanUser <password>"
Write-Host "`nScript complete. If you want the user removed later run: Remove-LocalUser -Name $scanUser"
How to configure the MFP (typical)
- In the MFP control panel or web UI choose “Scan to Folder (SMB)”.
- Folder path (UNC): \PC-NAME\ScansD or \192.168.x.y\ScansD
- Username: PC-NAME\scanuser_d (some MFPs want just scanuser_d; try PC\username if the first fails)
- Password: the password you entered above
- Domain/Workgroup: leave blank or use the PC name/workgroup value if required
Diagnostic commands to gather and paste (if it still fails)
If the scan still fails after applying the fix, paste the outputs of these three commands (run in elevated PowerShell / CMD) and I’ll interpret them:
- sc query LanmanServer
- netstat -ano | findstr ":445"
- net use \PCNAME\ScansD /userCNAME\scanuser_d <password> (replace PCNAME and password with actual values; you can obfuscate password if you want)
Also useful:
- ipconfig /all (to show PC IP)
- Test-NetConnection -ComputerName <PC-IP> -Port 445
Common gotchas and notes
- Name resolution: printers sometimes don’t resolve PC names. Using the PC’s IP address in the UNC avoids this problem.
- Firewall: Windows Reset or in-place repair often reverts firewall rules — enabling the File & Printer Sharing rule is required.
- Sleep/Power: If the PC sleeps, the MFP cannot reach it. Set power plan to prevent sleeping when sharing.
- Credentials on the MFP must match a local account on the PC (not a Microsoft account). Use a local account or create a local password for your Microsoft account by creating a local user as above.
- SMB versions: modern Windows uses SMB2/3; you shouldn’t need SMB1. Avoid enabling SMB1 for security reasons.
If you want me to do this for you
- I can provide the exact one‑line net commands instead of the PowerShell script if you prefer CMD.
- Or, paste the model of your MFP and the current UNC you configured (and whether you used a username), and I’ll give the exact values to enter on the MFP.
If you prefer to stop now, that’s fine — when you come back paste the outputs of the diagnostic commands above and I’ll pick up where we left off.
OI)(CI)M"
