Windows Cannot Find the Network Path (Error 51)

Why This Error Happens

This error occurs when Windows 11 is unable to resolve or reach the destination computer or shared resource over the network, typically due to name resolution failures, disabled network discovery, or the target device being offline or unreachable. It can also stem from firewall rules blocking SMB (Server Message Block) traffic on ports 445 or 139, or from disabled NetBIOS/SMB protocols required for legacy network path resolution. Additionally, incorrect network profiles (Public instead of Private) often prevent Windows from establishing the necessary trust for file and printer sharing.

Step-by-Step Resolution Guide

1. Verify Network Connectivity and Path Syntax
   Open Command Prompt and run ping <destination-computer-name-or-IP> to confirm the target is reachable. Ensure the UNC path is correctly formatted (e.g., \\ComputerName\ShareName), not using incorrect slashes or typos.

2. Enable Network Discovery and File Sharing
   Go to Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings. Under your current profile, enable “Turn on network discovery” and “Turn on file and printer sharing,” then click Save changes.

3. Set Network Profile to Private
   Navigate to Settings > Network & Internet > Wi-Fi/Ethernet, click on your active connection, and change the network profile from Public to Private. This allows Windows to trust other devices on the same network.

4. Enable SMB 1.0/CIFS Support (If Connecting to Older Devices)
   Open Control Panel > Programs > Turn Windows features on or off, scroll down, and check SMB 1.0/CIFS File Sharing Support. Restart your PC afterward. Note: only enable this if connecting to legacy NAS devices or older systems.

5. Check Windows Firewall Rules
   Go to Control Panel > System and Security > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall. Ensure “File and Printer Sharing” is checked for both Private and Public networks.

Alternative or Verification Steps

• After applying changes, try accessing the network path again via Run (Win + R) and typing the UNC path directly (e.g., \\192.168.1.10\SharedFolder) to confirm connectivity.
• If the issue persists, try connecting using the target device’s IP address instead of its hostname, as this bypasses potential DNS or NetBIOS name resolution failures.

Why This Error Happens

Error 52 occurs when Windows detects that another device on the network is already using the same computer name or NetBIOS identifier. This commonly happens after cloning a Windows 11 image/VM without changing the default hostname, or when DHCP/DNS caches retain stale records pointing to a duplicate name. It can also surface when a previously joined machine was removed improperly, leaving orphaned name registrations in the domain controller or network switch’s ARP/NetBIOS tables.

Step-by-Step Resolution Guide

1. Check and change the computer name:

• Go to Settings > System > About > Rename this PC (or Control Panel > System > Advanced system settings > Computer Name tab).
• Click Change, enter a unique name, and restart the PC.

1. Verify no duplicate exists on the network:

• Open Command Prompt as Administrator and run:
  
nbtstat -A <IP_address_of_conflicting_device>

• Check if another live device is broadcasting the same name; if so, rename one of them.

1. Flush DNS and NetBIOS cache:

• In an elevated Command Prompt, run:
  
ipconfig /flushdns
ipconfig /release
ipconfig /renew
nbtstat -R
nbtstat -RR

• This clears stale name resolution entries that may be causing the false duplicate detection.

1. Remove stale computer object from Active Directory (if domain-joined):

• Open Active Directory Users and Computers on the domain controller.
• Locate the old/duplicate computer object under the relevant OU and delete it.
• Rejoin the PC to the domain afterward.

1. Restart the network switch/router DHCP lease table (if applicable):

• Reboot the router/switch or manually clear the DHCP lease for the conflicting IP/hostname to force fresh registration.

Alternative or Verification Steps

• After renaming and rebooting, attempt to join the domain or workgroup again — if successful without the Error 52 prompt, the issue is resolved.
• If the problem persists, temporarily disconnect the PC from the network, rename it locally, then reconnect and rejoin the domain/workgroup to avoid transient name broadcast conflicts.

Troubleshooting Guide: Error 53 – “The Network Path Was Not Found”

Why This Error Happens

Error 53 typically occurs when Windows 11 cannot resolve or reach a remote computer name over the network, often due to disabled NetBIOS/SMB services, a misconfigured firewall blocking File and Printer Sharing, or DNS/name resolution failures. This can also happen if the target machine has “Network Discovery” turned off, or if the client is using an outdated SMB protocol (SMBv1) that the target no longer supports. In domain environments, it may also stem from an interrupted trust relationship or blocked ports (139/445) between the two devices.

Step-by-Step Resolution Guide

1. Verify Network Discovery and File Sharing are enabled:
   Go to Control Panel > Network and Internet > Network and Sharing Center > Change advanced sharing settings. Ensure “Turn on network discovery” and “Turn on file and printer sharing” are enabled for your current network profile (Private/Public).

2. Check Windows Defender Firewall rules:
   Navigate to Control Panel > Windows Defender Firewall > Allow an app or feature through Windows Defender Firewall. Confirm “File and Printer Sharing” is checked for both Private and Public networks.

3. Test name resolution using IP address instead of hostname:
   Open Command Prompt and run ping <target-computer-name>. If this fails but ping <IP-address> succeeds, the issue is DNS/NetBIOS resolution. Try accessing the share via \\<IP-address>\sharename instead of the computer name.

4. Enable NetBIOS over TCP/IP (if disabled):
   Go to Network Connections > (Your Adapter) > Properties > Internet Protocol Version 4 (TCP/IPv4) > Properties > Advanced > WINS tab, and select “Enable NetBIOS over TCP/IP.”

5. Restart the Function Discovery and Server services:
   Open services.msc, locate Function Discovery Resource Publication, Server, and Workstation services. Ensure they are set to “Automatic” and running. Restart them if needed.

Alternative or Verification Steps

• After applying the fixes, try mapping the network drive again via This PC > Map network drive, entering the full UNC path (\\ComputerName\ShareName), to confirm connectivity is restored.
• If the issue persists, temporarily disable third-party antivirus/firewall software to rule out interference, then test the connection again.

Troubleshooting Guide: Error 54 – “The Network Is Busy” on Windows 11

Why This Error Happens

Error 54 typically occurs when a network resource (such as a shared drive, printer, or remote server) is temporarily overloaded, unreachable, or when the SMB (Server Message Block) protocol encounters a conflict during file or resource sharing. This can result from network congestion, an unstable NIC (Network Interface Card) driver, corrupted network stack components, or a misconfigured firewall blocking retries. In some cases, outdated SMB versions (like SMBv1) or timeout mismatches between client and server also trigger this error.

Step-by-Step Resolution Guide

1. Reset the TCP/IP Stack and Winsock Catalog
   Open Command Prompt as Administrator and run:

   netsh int ip reset
   netsh winsock reset

Restart your PC after running these commands.

2. Update or Reinstall the Network Adapter Driver
   Go to Device Manager > Network Adapters, right-click your active adapter, select Update driver. If the issue persists, choose Uninstall device, then restart Windows to let it reinstall the driver automatically.

3. Enable SMB 2.0/3.0 and Disable SMBv1 (if legacy compatibility isn’t needed)
   Open Control Panel > Programs > Turn Windows features on or off, uncheck SMB 1.0/CIFS File Sharing Support, and ensure SMB Direct is enabled if using compatible hardware.

4. Adjust Network Timeout Settings via Registry
   Open regedit, navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
   Add/modify a DWORD value named SessTimeout and set it to 60 (decimal) to allow more time before a busy response is triggered.

5. Check Firewall and Antivirus Rules
   Navigate to Windows Security > Firewall & network protection > Advanced settings, and ensure no rules are blocking outbound/inbound traffic on ports 445 (SMB) or 139 (NetBIOS).

Alternative or Verification Steps

• Verify the Fix: Try accessing the network resource again (shared folder, printer, or drive). Run ping <server-IP> and net use \\server\share in Command Prompt to confirm stable connectivity without delays.
• Alternative Fix: If the error persists, try connecting via a different network (e.g., mobile hotspot) to isolate whether the issue is local network congestion or a server-side problem.

Windows 11 Error 55: “The Specified Network Resource or Device Is No Longer Available”

Why This Error Happens

Error 55 typically occurs when the NTFS file system detects corruption on a disk volume, often triggered by improper shutdowns, failing storage hardware, or file system metadata damage. This error can also surface when accessing network shares if the underlying disk on the server side has bad sectors or logical inconsistencies. In most cases, the root cause is a corrupted file system table (MFT) or a degrading physical/virtual disk that Windows can no longer reliably read from or write to.

Step-by-Step Resolution Guide

1. Run CHKDSK to scan and repair the disk:
   Open Command Prompt as Administrator and run:

   chkdsk C: /f /r /x

Replace C: with the affected drive letter. If prompted, schedule the scan on next restart by typing Y and rebooting your PC.

2. Update or reinstall the disk/network adapter drivers:
   Go to Device Manager → expand Disk drives (or Network adapters if accessing a shared resource) → right-click the affected device → Update driver. If the issue persists, uninstall the device and restart Windows 11 to force a clean driver reinstall.

3. Check disk health using PowerShell:
   Run PowerShell as Administrator and execute:

   Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus

If HealthStatus returns “Warning” or “Unhealthy,” the physical drive may be failing and require replacement.

4. Verify network share permissions (if error occurs over network):
   Navigate to the shared folder on the host machine → right-click → Properties → Sharing tab → Advanced Sharing → Permissions. Ensure the connecting user account has at least Read access, and confirm the share hasn’t been deleted or renamed.

5. Check for disk connection issues (external/USB drives):
   If the error involves an external drive, try a different USB port or cable, and test the drive on another PC to rule out a failing enclosure or connector.

Alternative or Verification Steps

• Verify the fix: Reboot your PC, then attempt to access the previously failing resource (file, folder, or network drive) to confirm the error no longer appears. Re-run chkdsk C: /scan to ensure no further corruption is flagged.
• Alternative solution: If CHKDSK repeatedly finds the same errors or the disk shows as “Unhealthy” in PowerShell, back up your data immediately and consider replacing the drive, as this indicates impending hardware failure rather than a software-fixable issue.

Why This Error Happens

Error 56 occurs when the Server service’s NetBIOS command queue becomes saturated, typically because the “Server” or “Workstation” service resource allocation is too low for the current network load. This is common on Windows 11 machines acting as file/print servers, syncing large amounts of SMB traffic, or connected to older network hardware/switches with duplex mismatches. Corrupted network driver bindings or outdated NIC drivers can also cause the buffer queue to overflow faster than it’s cleared.

Step-by-Step Resolution Guide

1. Increase Server Service Buffer Registry Values
   Open Registry Editor (regedit) and navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
   Add or modify the following DWORD (32-bit) values:

• MaxWorkItems = 65535
• MaxMpxCt = 800
• MaxRawWorkItems = 128
• MaxFreeConnections = 64
• MinFreeConnections = 20
  Restart the PC after applying changes.

1. Update Network Adapter Drivers
   Go to Device Manager > Network Adapters, right-click your active NIC, select Update Driver, then choose Search automatically. If a newer driver exists on the manufacturer’s website (Intel, Realtek, Broadcom), install that version instead, as it often resolves buffer handling bugs.

2. Check Duplex/Speed Settings
   In Device Manager > Network Adapters > [Your NIC] > Properties > Advanced, ensure the Speed & Duplex setting matches your switch/router (e.g., “1.0 Gbps Full Duplex”) rather than “Auto Negotiation,” which can cause packet retransmission storms leading to command queue backups.

3. Disable NetBIOS Over TCP/IP (If Not Required)
   Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your adapter → Properties → select Internet Protocol Version 4 (TCP/IPv4) → Properties → Advanced → WINS tab → select Disable NetBIOS over TCP/IP. This is safe on modern networks relying solely on DNS/SMB direct hosting.

4. Restart the Server and Workstation Services
   Open Command Prompt as Administrator and run:

   net stop server
   net stop workstation
   net start workstation
   net start server

Alternative or Verification Steps

• Open Event Viewer (eventvwr.msc) and check Windows Logs > System for recurring Event ID 56 entries after 24–48 hours of normal use to confirm the error has stopped.
• If the issue persists, temporarily connect the machine to a different switch/port to rule out a faulty physical network component causing excessive retransmissions.

Troubleshooting Guide: Error 57 – Network Adapter Hardware Error (Windows 11)

Why This Error Happens

Error 57 is logged by the Event Log (source: e1dexpress, rtwlane, or similar NIC drivers) when the network adapter’s driver detects a hardware-level malfunction, such as a failed self-test, a communication breakdown between the driver and the physical NIC chip, or power delivery issues to the adapter. This is commonly triggered by outdated or corrupted network drivers, a NIC that has entered a faulty power-saving state, or genuine hardware degradation (loose connection, overheating, or a failing adapter). In laptops, aggressive USB/PCIe power management is a frequent culprit, as it cuts power to the adapter unexpectedly.

Step-by-Step Resolution Guide

1. Update or Reinstall the Network Driver

• Press Win + X → Device Manager → expand Network adapters.
• Right-click your adapter → Update driver → Search automatically.
• If that doesn’t resolve it, right-click again → Uninstall device → check Delete the driver software for this device → restart your PC so Windows reinstalls a fresh driver.

1. Disable Power Management for the Adapter

• In Device Manager, right-click your network adapter → Properties → Power Management tab.
• Uncheck Allow the computer to turn off this device to save power.
• Click OK and restart the system.

1. Reset Network Settings

• Go to Settings → Network & Internet → Advanced network settings → Network reset.
• Click Reset now and confirm. This reinstalls all network adapters and resets related components (Winsock, TCP/IP stack).

1. Check for Firmware/BIOS Updates

• Visit your PC or motherboard manufacturer’s support page and check for a BIOS/UEFI update and any chipset driver updates, as these can resolve adapter communication issues at the hardware level.

1. Inspect Physical Hardware (if using Ethernet or PCIe NIC)

• Reseat the network cable or the PCIe card itself.
• Test the adapter in another USB port (for USB NICs) or try a different Ethernet cable/port to rule out a faulty physical connection.

Alternative or Verification Steps

• Open Event Viewer (eventvwr.msc) → Windows Logs → System, and confirm Error 57 no longer reoccurs after a reboot and normal usage period (24–48 hours).
• If the error persists despite driver/firmware fixes, test with a different network adapter (e.g., a USB Wi-Fi/Ethernet dongle) to confirm whether the onboard NIC hardware itself has failed and needs replacement.

Windows 11 Error 58: “The Specified Server Cannot Perform the Requested Operation”

Why This Error Happens

Error 58 typically occurs when attempting to access shared resources (files, printers, or network drives) over SMB/CIFS protocols, and stems from a mismatch in SMB protocol versions, disabled network services, or corrupted network configurations. This commonly happens when connecting to older NAS devices, legacy servers, or third-party SMB implementations that don’t support the SMB version Windows 11 defaults to. Additionally, insufficient permissions on the target server or a disabled “Server” service on the host machine can trigger this same error code.

Step-by-Step Resolution Guide

1. Enable SMB 1.0/CIFS Support (if connecting to legacy devices)

• Open Control Panel → Programs → Turn Windows features on or off
• Scroll down and check SMB 1.0/CIFS File Sharing Support
• Click OK and restart your PC

1. Verify the Server Service is Running

• Press Win + R, type services.msc, and press Enter
• Locate Server in the list, ensure Status shows “Running”
• Right-click → Properties → set Startup type to Automatic
• Click Start if not already running

1. Reset Network Configuration via Command Prompt

• Open Windows Terminal or Command Prompt as Administrator
• Run the following commands sequentially:
  
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

• Restart your computer after completion

1. Check and Repair File and Printer Sharing Settings

• Go to Settings → Network & Internet → Advanced network settings
• Select Advanced sharing settings
• Ensure File and printer sharing is turned On for your active network profile

1. Verify Permissions on the Target Server

• On the server/host machine, right-click the shared folder → Properties → Sharing tab → Advanced Sharing → Permissions
• Ensure your user account or “Everyone” group has at least Read access
• Also check the Security tab for matching NTFS permissions

Alternative or Verification Steps

• To verify the fix: Try accessing the shared resource again via \\servername\sharename in File Explorer’s address bar. If successful, the connection should establish without the Error 58 prompt.
• Alternative solution: If the issue persists, try mapping the network drive using the server’s IP address instead of its hostname (\\192.168.x.x\sharename), as this can bypass DNS or NetBIOS resolution issues that sometimes trigger this error.

Troubleshooting Guide: Error 59 – “An Unexpected Network Error Occurred”

Why This Error Happens

Error 59 typically occurs when the SMB (Server Message Block) protocol encounters an interruption while reading or writing data across a network connection, often due to unstable network hardware, corrupted network drivers, or misconfigured network adapter settings. This can also result from conflicts between the Workstation and Server services, or from NIC (Network Interface Card) power-saving features interrupting active connections. Additionally, outdated firmware on routers/switches or a corrupted TCP/IP stack can trigger this error during file transfers or shared resource access.

Step-by-Step Resolution Guide

1. Disable Network Adapter Power Management

• Press Win + X → select Device Manager
• Expand Network adapters, right-click your active adapter → Properties
• Go to the Power Management tab → uncheck “Allow the computer to turn off this device to save power” → click OK

1. Reset TCP/IP Stack and Winsock Catalog

• Open Command Prompt as Administrator (Win + X → Terminal (Admin))
• Run the following commands sequentially:
  
netsh int ip reset
netsh winsock reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

• Restart your PC.

1. Update or Roll Back Network Drivers

• In Device Manager, right-click your network adapter → Update driver
• If the issue started recently, instead choose Properties → Driver tab → Roll Back Driver
• Alternatively, download the latest driver directly from the manufacturer’s website (Intel, Realtek, etc.)

1. Restart Workstation and Server Services

• Press Win + R, type services.msc, press Enter
• Locate Workstation and Server services → right-click each → Restart

1. Check and Repair Corrupted System Files

• Open Command Prompt as Administrator
• Run:
  
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

• Restart your computer once the scans complete.

Alternative or Verification Steps

• Verify the fix: Attempt the same network operation (file transfer, shared drive access, etc.) that previously triggered Error 59. Check Event Viewer (eventvwr.msc) under Windows Logs → System to confirm no new Error 59 entries appear.
• Alternative fix: If the error persists, temporarily disable any third-party antivirus/firewall software to rule out interference, or connect via Ethernet instead of Wi-Fi to isolate whether the issue is wireless-hardware related.

Why This Error Happens

Error 60 (“The remote adapter is not compatible”) typically occurs when the Remote Desktop Protocol (RDP) client attempts to negotiate a connection using a network adapter driver or Winsock configuration that is outdated, corrupted, or mismatched with the security protocols required by the host. This is often triggered by a corrupted network stack, an outdated NIC driver, or conflicting virtual adapters created by VPN software, Hyper-V, or third-party antivirus tools. It can also result from a broken Winsock catalog after a Windows Update or driver rollback.

Step-by-Step Resolution Guide

1. Reset the Winsock catalog and TCP/IP stack
   Open Command Prompt as Administrator and run:

   netsh winsock reset
   netsh int ip reset

Restart your PC after running these commands.

2. Update or reinstall the network adapter driver

• Go to Device Manager > Network Adapters.
• Right-click your primary adapter (Ethernet or Wi-Fi) → Update driver → “Search automatically for drivers.”
• If that fails, right-click → Uninstall device, check “Delete the driver software,” then reboot to let Windows reinstall a clean driver.

2. Disable conflicting virtual adapters

• Open ncpa.cpl (Network Connections).
• Temporarily disable any VPN adapters, Hyper-V Virtual Switches, or VMware/VirtualBox virtual NICs that aren’t in active use.
• Retry the Remote Desktop connection.

2. Check and repair system files
   Run the following in an elevated Command Prompt to fix underlying corruption:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

5. Update Remote Desktop Client settings

• Open Registry Editor (regedit) and navigate to:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp
• Ensure SecurityLayer is set to 1 (Negotiate) rather than 0 or 2, which can cause adapter compatibility mismatches during handshake.

Alternative or Verification Steps

• After applying the fixes, test connectivity by launching mstsc and connecting to the same remote host — the session should establish without triggering Error 60.
• If the issue persists, try connecting from a different network adapter (e.g., switch from Wi-Fi to Ethernet) or a different device entirely to isolate whether the problem is adapter-specific or host-side.

Windows 11 Troubleshooting Guide: Error 61 – Printer Queue Full

Why This Error Happens

Error 61 typically occurs when the Print Spooler service (spoolsv.exe) becomes overloaded or corrupted, causing print jobs to stack up in the queue instead of processing normally. This often happens due to a stalled or corrupted print job at the front of the queue that blocks all subsequent jobs, insufficient permissions on the spooler’s working directory, or a conflict between the printer driver and the spooler service. In some cases, a full or corrupted spool folder (where temporary print files are stored) prevents the system from accepting new jobs, triggering the “queue full” error.

Step-by-Step Resolution Guide

1. Stop the Print Spooler Service

• Press Win + R, type services.msc, and press Enter.
• Locate Print Spooler in the list, right-click it, and select Stop.

1. Clear the Print Spool Folder

• Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS.
• Delete all files in this folder (these are the stuck/corrupted print jobs causing the backlog). You may need administrator permission to do this.

1. Restart the Print Spooler Service

• Go back to services.msc, right-click Print Spooler, and select Start.
• Set the Startup type to Automatic if it isn’t already, to prevent future manual restarts.

1. Check Printer Driver and Permissions

• Open Settings > Bluetooth & devices > Printers & scanners, select your printer, and click Remove device.
• Reinstall the printer using the latest driver from the manufacturer’s website (avoid generic Windows drivers if issues persist).
• Ensure your user account has Full Control permissions on the C:\Windows\System32\spool\PRINTERS folder via right-click > Properties > Security tab.

1. Run the Windows Printer Troubleshooter

• Go to Settings > System > Troubleshoot > Other troubleshooters.
• Click Run next to Printer and follow the prompts to detect and fix spooler-related issues automatically.

Alternative or Verification Steps

• Verify the fix: Send a test print job (Settings > Printers & scanners > select printer > Print a test page). If it completes without errors and the queue shows no stuck jobs, the issue is resolved.
• Alternative fix: If the error persists, try printing directly via USB (bypassing network/Wi-Fi drivers) to isolate whether the issue is spooler-related or connectivity-related.

Troubleshooting Guide: Error 62 – Print Spooler Storage Space Unavailable

Why This Error Happens

Error 62 occurs when the Windows Print Spooler service cannot allocate enough disk space on the drive hosting the spool folder to temporarily store a print job. This is typically caused by a full or near-full system drive (usually C:\), an excessively large spool folder filled with stuck or corrupted print jobs, or insufficient NTFS permissions on the spool directory preventing the spooler from writing new files. In some cases, a misconfigured spool folder path pointing to an inaccessible or disconnected drive can also trigger this error.

Step-by-Step Resolution Guide

1. Check available disk space
   Open File Explorer and check free space on the drive where Windows is installed (typically C:\). Ensure at least 1–2 GB is free. If space is low, delete temporary files using Settings > System > Storage > Temporary files.

2. Clear the print spooler folder

• Press Win + R, type services.msc, and press Enter.
• Locate Print Spooler, right-click it, and select Stop.
• Navigate to C:\Windows\System32\spool\PRINTERS.
• Delete all files inside this folder (these are queued print jobs).
• Go back to services.msc, right-click Print Spooler, and select Start.

1. Verify folder permissions

• Right-click the PRINTERS folder (C:\Windows\System32\spool\PRINTERS) and select Properties > Security.
• Ensure SYSTEM, Administrators, and Print Operators have Full Control.
• Apply changes and restart the Print Spooler service as described above.

1. Change the spool folder location (if disk space is chronically low)

• Open Control Panel > Devices and Printers.
• Right-click any printer and select Printer Properties, or open the Print Server Properties dialog.
• Go to the Advanced tab and click Change Advanced Settings.
• Set a new spool folder path on a drive with more free space (e.g., D:\Spool).
• Restart the Print Spooler service to apply the change.

1. Run Windows Update and Printer Troubleshooter

• Go to Settings > System > Troubleshoot > Other troubleshooters.
• Run the Printer troubleshooter to detect and repair spooler-related issues automatically.

Alternative or Verification Steps

• After completing the steps, send a test print job to confirm it processes without triggering Error 62.
• If the issue persists, check Event Viewer (eventvwr.msc) under Windows Logs > System for related Spooler errors, and consider reinstalling the printer driver or resetting the print system using net stop spooler and net start spooler via Command Prompt (Admin).

Why This Error Happens

Error 63 typically occurs when the Print Spooler service encounters a corrupted spool file or loses communication with the printer driver mid-job, causing Windows to automatically purge the print job from the queue. This can also happen if the spooler folder (C:\Windows\System32\spool\PRINTERS) has insufficient permissions, is full, or contains orphaned .SHD/.SPL files from a previous failed print attempt. Outdated or mismatched printer drivers are another common trigger, especially after a recent Windows 11 update.

Step-by-Step Resolution Guide

1. Stop the Print Spooler service

• Press Win + R, type services.msc, and press Enter.
• Locate Print Spooler, right-click it, and select Stop.

1. Clear the print queue folder manually

• Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS.
• Delete all files inside this folder (these are leftover/corrupted spool files causing Error 63).

1. Restart the Print Spooler service

• Go back to services.msc, right-click Print Spooler, and select Start.
• Set the Startup type to Automatic if it isn’t already.

1. Update or reinstall the printer driver

• Go to Settings > Bluetooth & devices > Printers & scanners.
• Select your printer, click Remove device, then reinstall it by clicking Add device and letting Windows fetch the latest driver.

1. Run the Windows Printer Troubleshooter

• Go to Settings > System > Troubleshoot > Other troubleshooters.
• Click Run next to Printer and follow the on-screen prompts to auto-detect and fix spooler-related issues.

Alternative or Verification Steps

• After completing the steps, send a test print job (e.g., print a simple text document) to confirm it processes without triggering Error 63.
• If the issue persists, check Event Viewer (Windows Logs > System) for related Print Spooler errors, and consider updating your printer’s firmware from the manufacturer’s website.

Troubleshooting Guide: Error 64 – “The Specified Network Name Is No Longer Available” (Windows 11)

Why This Error Happens

Error 64 typically occurs when an active SMB (Server Message Block) connection between two devices is unexpectedly terminated, often due to network instability, timeout settings, or interference from security software. Common root causes include outdated network adapter drivers, misconfigured SMB signing/encryption settings, antivirus or firewall software interrupting the connection, or issues with the network adapter’s power-saving features causing the connection to drop mid-transfer. This is especially common when accessing shared drives, printers, or performing large file transfers over a network in Windows 11.

Step-by-Step Resolution Guide

1. Update Network Adapter Drivers

• Open Device Manager (right-click Start > Device Manager).
• Expand Network Adapters, right-click your active adapter, and select Update driver > Search automatically for drivers.
• Restart your PC after the update completes.

1. Disable Network Adapter Power Management

• Go to Device Manager > Network Adapters > right-click your adapter > Properties.
• Navigate to the Power Management tab and uncheck “Allow the computer to turn off this device to save power.”
• Click OK and restart the system.

1. Adjust SMB Configuration via PowerShell

• Open PowerShell as Administrator.
• Run the following command to disable SMB signing requirements (if causing conflicts):
  
Set-SmbClientConfiguration -RequireSecuritySignature $false -Force

• On the server/host machine, run:
  
Set-SmbServerConfiguration -EncryptData $false -Force


1. Modify Registry for Session Timeout

• Press Win + R, type regedit, and navigate to:
  
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

• Create/modify a DWORD (32-bit) value named KeepAliveTime and set it to 10 (in seconds, hexadecimal or decimal as needed).
• Restart the computer for changes to take effect.

1. Temporarily Disable Firewall/Antivirus

• Go to Windows Security > Firewall & network protection.
• Temporarily disable the firewall for your active network profile (Private/Public) to test if third-party antivirus or Windows Firewall is blocking the SMB connection.
• If this resolves the issue, add an exception for SMB traffic (port 445) instead of leaving the firewall disabled.

Alternative or Verification Steps

• Verify the fix: Attempt to access the network share or perform the previous action (e.g., file transfer, printer access) that triggered Error 64. Monitor for at least 15-20 minutes to ensure the connection remains stable.
• Alternative solution: If the issue persists, try mapping the network drive using the IP address instead of the hostname (\\192.168.x.x\sharename) to rule out DNS resolution problems.

Troubleshooting Guide: Error 65 – Network Access Denied (Windows 11)

Why This Error Happens

Error 65 typically occurs when Windows 11 attempts to establish a connection to a shared network resource (such as a mapped drive, shared folder, or printer) but is blocked by insufficient permissions, disabled network protocols, or restrictive firewall/security policies. This is commonly triggered when the “File and Printer Sharing” service is disabled, the target share’s NTFS/Share permissions don’t include the connecting user account, or SMB (Server Message Block) settings are misconfigured between the client and host. In some cases, outdated or corrupted network credentials cached in Windows Credential Manager also cause this access denial.

Step-by-Step Resolution Guide

1. Verify User Permissions on the Shared Resource

• On the host machine, right-click the shared folder → Properties → Sharing tab → Advanced Sharing → Permissions.
• Ensure the user/group attempting to connect has at least Read access, and check the Security tab for matching NTFS permissions.

1. Enable File and Printer Sharing

• Go to Control Panel → Network and Internet → Network and Sharing Center → Change advanced sharing settings.
• Under your active network profile, enable Turn on file and printer sharing and Turn on network discovery.

1. Clear Cached Credentials

• Open Control Panel → Credential Manager → Windows Credentials.
• Locate any entries related to the network path causing the error, click them, and select Remove.
• Reconnect to the share and enter fresh credentials when prompted.

1. Check SMB Protocol Settings

• Open PowerShell as Administrator and run:
  
Get-SmbServerConfiguration | Select EnableSMB1Protocol, EnableSMB2Protocol

• If SMB1 is required (for legacy devices), enable it via Control Panel → Programs → Turn Windows features on or off → check SMB 1.0/CIFS File Sharing Support.

1. Adjust Firewall/Group Policy Restrictions

• Open Windows Defender Firewall with Advanced Security and ensure File and Printer Sharing (SMB-In) rules are enabled for your network profile.
• If on a domain, check Group Policy (gpedit.msc) under Computer Configuration → Windows Settings → Security Settings → Local Policies → User Rights Assignment for restrictions like “Deny access to this computer from the network.”

Alternative or Verification Steps

• After applying changes, test the connection using net use \\<ServerName>\<ShareName> in Command Prompt — a successful mount confirms the fix.
• If the issue persists, try connecting via IP address instead of hostname, or temporarily disable third-party antivirus/firewall software to rule out interference.

Windows 11 Troubleshooting Guide: Error 2 – “The System Cannot Find the File Specified”

Why This Error Happens

Error 2 occurs when a process, service, or command attempts to access a file, executable, or path that does not exist at the expected location. This is typically caused by a missing or relocated file, an incorrect path referenced in the Windows Registry or a configuration file, or corruption within a service’s installation directory. It can also occur when environment variables (like PATH) point to outdated or invalid directories.

Step-by-Step Resolution Guide

1. Identify the exact file/path causing the error
   Open Event Viewer (Win + R → eventvwr.msc) and navigate to Windows Logs > System or Application. Locate the Error 2 entry and note the specific file path or service name mentioned in the details pane.

2. Verify the file exists
   Use File Explorer or Command Prompt to check if the referenced file is actually present:

   dir "C:\Path\To\File.exe"

If missing, it may have been deleted by an update, antivirus quarantine, or a botched uninstall.

3. Run System File Checker and DISM
   Corrupted system files often trigger this error. Open Command Prompt as Administrator and run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart your PC after completion.

4. Check and repair the associated application/service
   If the error points to a specific program, go to Settings > Apps > Installed Apps, locate the application, and select Modify or Repair. For core Windows services, use:

   sc query <servicename>

to confirm the service’s binary path is correct.

5. Reset environment variables (if PATH-related)
   Go to Settings > System > About > Advanced system settings > Environment Variables. Review the Path variable for broken or outdated directory entries and remove/correct them.

Alternative or Verification Steps

• Verify the fix: Re-run the original action or command that triggered Error 2 and confirm it completes without the file-not-found message; also check Event Viewer to ensure no new Error 2 entries appear.
• Alternative fix: If the issue persists, perform an in-place repair upgrade using Windows 11 installation media (setup.exe from a mounted ISO) to restore missing system files without affecting personal data.

Windows 11 Troubleshooting Guide: Error 3 – “The System Cannot Find the Path Specified”

Why This Error Happens

Error 3 occurs when the Windows OS or an application attempts to access a file path that no longer exists, has been renamed, or is malformed in a script/registry entry. This is commonly caused by broken environment variables, incorrect drive mappings, or leftover references from uninstalled software. It can also happen if a service is configured to launch from a directory that was moved or deleted during an update.

Step-by-Step Resolution Guide

1. Verify the Path Exists
   Open File Explorer and manually navigate to the path referenced in the error. If it’s a system path, check C:\Windows\System32\ or the specific application’s install directory to confirm it hasn’t been moved or deleted.

2. Check Environment Variables

• Press Win + S, type “Edit the system environment variables”, and press Enter.
• Click Environment Variables.
• Under System Variables, review the Path variable and remove any entries pointing to non-existent directories (e.g., old software folders).
• Click OK and restart your PC.

1. Repair Corrupted System Files
   Open Command Prompt as Administrator and run:

   sfc /scannow

Followed by:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be causing incorrect path resolution.

4. Inspect the Windows Registry (Advanced Users)

• Press Win + R, type regedit, and press Enter.
• Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths.
• Look for keys referencing the missing path and correct or delete the invalid entry.
• Backup the registry before making any changes (File > Export).

4. Reinstall or Repair the Affected Application
   If the error is tied to a specific program, go to Settings > Apps > Installed Apps, select the application, and choose Modify/Repair. If unavailable, uninstall and reinstall it.

Alternative or Verification Steps

• Verify the Fix: Restart your PC and re-run the action that triggered Error 3. Check Event Viewer (eventvwr.msc) under Windows Logs > Application to confirm no repeated Error 3 entries appear.
• Alternative Fix: If the issue persists, perform a System Restore to a point before the error started occurring, via Settings > System > Recovery > Advanced startup.

Windows 11 Troubleshooting Guide: Error 20 – “The System Cannot Find the Device Specified”

Why This Error Happens

Error Code 20 typically occurs when the Windows Plug and Play (PnP) manager cannot properly load or communicate with a device driver, often due to a corrupted or incomplete driver installation. This can result from a failed Windows Update, corrupted registry entries related to the device, or conflicts introduced by third-party driver management software. In some cases, it also occurs when the device’s driver files have been deleted or are missing from the system driver store (C:\Windows\System32\drivers).

Step-by-Step Resolution Guide

1. Open Device Manager and identify the affected device:
   Press Win + X and select Device Manager. Locate the device showing a yellow warning triangle and Error 20 in its Properties (right-click the device → Properties → General tab).

2. Uninstall and scan for hardware changes:
   Right-click the problematic device and select Uninstall device. Ensure you check the box for “Attempt to remove the driver for this device” if prompted. Then click the Action menu in Device Manager and select Scan for hardware changes to force Windows to reinstall the driver.

3. Manually update the driver via Windows Update or OEM source:
   Go to Settings > Windows Update > Advanced options > Optional updates > Driver updates to check for a Microsoft-signed driver. If unavailable, download the latest driver directly from the manufacturer’s website (based on the exact hardware model) and install it manually via Update driver > Browse my computer for drivers.

4. Check and repair system files:
   Open Command Prompt as Administrator and run:

   sfc /scannow

Once complete, run:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be interfering with driver registration.

5. Reset the device via Registry (Advanced users only):
   If the error persists, open regedit, navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum, locate the specific device instance ID (matching the Device Manager entry), and delete the problematic key. Back up the registry first, then restart the PC to allow Windows to regenerate the entry.

Alternative or Verification Steps

• Verify the fix: Reopen Device Manager and confirm the yellow warning icon is gone; check Properties > General to see if it states “This device is working properly.”
• Alternative solution: If the error returns after a restart, run the built-in Hardware and Devices Troubleshooter via Settings > System > Troubleshoot > Other troubleshooters, or perform a System Restore to a point before the error first appeared.

Windows 11 Error 21: “The Device Is Not Ready” Troubleshooting Guide

Why This Error Happens

Error 21 typically occurs when Windows attempts to communicate with a storage device (hard drive, USB drive, SD card, or optical drive) that isn’t fully initialized, powered, or properly connected. This is commonly caused by a loose cable connection, a corrupted or outdated device driver, or a drive that hasn’t finished spinning up/mounting before the OS tries to access it. In some cases, it stems from a corrupted file system or a drive letter conflict within Windows Disk Management.

Step-by-Step Resolution Guide

1. Check Physical Connections
   Disconnect and reconnect the affected drive (USB cable, SATA cable, or card reader). If it’s an external drive, try a different USB port or cable to rule out a faulty connection.

2. Update or Reinstall the Device Driver

• Press Win + X and select Device Manager.
• Expand Disk drives, right-click the problematic device, and select Update driver.
• Choose Search automatically for drivers. If that doesn’t resolve it, right-click again and select Uninstall device, then restart your PC to let Windows reinstall it fresh.

1. Run CHKDSK to Repair File System Errors

• Open Command Prompt as Administrator (Win + X → Terminal (Admin)).
• Run: chkdsk X: /f /r (replace X: with the actual drive letter).
• Allow the scan to complete; this may take time depending on drive size.

1. Reassign the Drive Letter

• Press Win + R, type diskmgmt.msc, and hit Enter.
• Right-click the affected drive/partition and select Change Drive Letter and Paths.
• Assign a new, unused drive letter and click OK.

1. Check Power Management Settings for USB Devices

• In Device Manager, expand Universal Serial Bus controllers.
• Right-click each USB Root Hub, go to Properties → Power Management, and uncheck Allow the computer to turn off this device to save power.

Alternative or Verification Steps

• Verify the fix: Open File Explorer and confirm the drive appears and opens without delay or error. Also check Device Manager to ensure no yellow warning icons remain on the device.
• Alternative solution: If the error persists, test the drive on another PC. If the issue follows the drive, it may be failing physically and should be backed up immediately and replaced.

Windows 11 Error 22: Device Does Not Recognize the Command

Why This Error Happens

Error 22 typically occurs when a device driver is corrupted, outdated, or incompatible with the command being sent by the operating system, often after a Windows update or driver installation. This can also result from a damaged registry entry associated with the device, or a conflict caused by third-party software modifying system-level I/O commands. In many cases, the device controller (such as a disk, USB peripheral, or optical drive) is receiving instructions it cannot interpret due to a mismatched or legacy driver version.

Step-by-Step Resolution Guide

1. Update or Reinstall the Device Driver

• Press Win + X and select Device Manager.
• Locate the problematic device (check under Disk drives, DVD/CD-ROM drives, or Universal Serial Bus controllers).
• Right-click the device, select Uninstall device, check “Attempt to remove the driver,” and restart your PC. Windows 11 will reinstall a fresh driver automatically.

1. Check the Registry for Corrupted Upper/Lower Filters

• Press Win + R, type regedit, and press Enter.
• Navigate to:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
• Look for UpperFilters and LowerFilters values. If present and not part of standard antivirus/burning software, back up the key and delete these values, then restart.

1. Run SFC and DISM Scans

• Open Terminal (Admin) via right-click on the Start button.
• Run: sfc /scannow
• Once complete, run: DISM /Online /Cleanup-Image /RestoreHealth
• Restart your computer after both scans finish.

1. Update Windows 11 Fully

• Go to Settings > Windows Update and click Check for updates.
• Install any pending updates, including optional driver updates listed under Advanced options > Optional updates.

1. Check Physical Connections (for external devices)

• Unplug and reconnect the device using a different USB port or cable.
• Test the device on another PC to rule out hardware failure.

Alternative or Verification Steps

• Verify the fix: Reopen Device Manager and confirm the device no longer shows a yellow warning icon; then retry the original command or action that triggered Error 22.
• Alternative solution: If the issue persists, use System Restore (rstrui.exe) to roll back to a point before the error started occurring, especially if it began after a recent driver or Windows update.

Troubleshooting Guide: Error 23 (Data Error – Cyclic Redundancy Check)

Why This Error Happens

Error 23 (Data error: cyclic redundancy check) occurs when Windows detects that data read from a disk sector doesn’t match its stored checksum, indicating physical or logical corruption. This is typically caused by bad sectors on a hard drive/SSD, a failing storage controller, a damaged or scratched optical disc, or corruption in the file system table (MFT). Loose SATA/USB cable connections and outdated storage drivers can also trigger this error intermittently.

Step-by-Step Resolution Guide

1. Check cable and connection integrity (for external/internal drives)
   Power down the PC, reseat the SATA/power cables (internal) or try a different USB port/cable (external drives). Loose connections often mimic CRC errors.

2. Run CHKDSK to scan and repair the file system
   Open Command Prompt as Administrator and run:

   chkdsk X: /f /r /x

Replace X: with the affected drive letter. This scans for bad sectors and attempts to recover readable information. Allow it to complete fully, even if it requires a restart.

3. Use built-in Windows tools to attempt file copy with retry
   For a specific corrupted file, use Robocopy with the /B (backup mode) switch to bypass permission-based read failures:

   robocopy "C:\Source\Folder" "D:\Destination\Folder" /B /R:1 /W:1

4. Check disk health using SMART data
   Run:

   wmic diskdrive get status

Or use Manage > Storage > Optimize Drives in Windows 11, or third-party tools like CrystalDiskInfo, to check for “Caution” or “Bad” health status indicating impending drive failure.

5. Update or reinstall storage controller drivers
   Go to Device Manager > Disk Drives / Storage Controllers, right-click the relevant device, select Update driver, and choose Search automatically for drivers. Reboot afterward.

Alternative or Verification Steps

• Verify the fix: Re-copy or re-open the previously affected file/folder without errors, and re-run chkdsk X: /scan to confirm no new bad sectors are reported.
• Alternative solution: If CRC errors persist after CHKDSK, the drive may be physically failing — back up all data immediately using a tool like EaseUS Data Recovery or Recuva, then replace the drive.

Why This Error Happens

Error 24 (“The program issued a command but the command length is incorrect”) is a low-level I/O error typically logged by the Disk or storage controller driver in Windows. It usually occurs when a storage device (HDD, SSD, USB drive, or SD card) receives a malformed or truncated command due to a corrupted or outdated driver, a faulty cable/connector, or a failing storage medium. It can also appear when firmware on the drive is out of sync with the Windows storage stack, causing communication mismatches during read/write operations.

Step-by-Step Resolution Guide

1. Check Event Viewer for details

• Press Win + X → Event Viewer → expand Windows Logs → System.
• Filter for Event ID 24 and note the Source (usually “Disk” or a specific controller name) and which device/drive letter is affected.

1. Update or reinstall the storage driver

• Open Device Manager (Win + X → Device Manager).
• Expand Disk drives, right-click the affected drive → Update driver → Search automatically for drivers.
• If that doesn’t help, right-click → Uninstall device, restart the PC to let Windows reinstall a fresh driver.

1. Run CHKDSK to check for disk errors

• Open Command Prompt as Administrator.
• Run: chkdsk X: /f /r (replace X: with the affected drive letter).
• Allow it to complete; restart if prompted (especially for the system drive).

1. Inspect physical connections

• For external/USB drives, try a different USB port or cable, preferably a USB 3.0 port directly on the motherboard (not a hub).
• For internal drives, check SATA/power cable seating, or try a different SATA port.

1. Update firmware and chipset drivers

• Visit the drive manufacturer’s website (e.g., Samsung, WD, Seagate) and install the latest firmware update tool.
• Also update the motherboard chipset drivers via the manufacturer’s support page to ensure proper storage controller communication.

Alternative or Verification Steps

• After applying fixes, reopen Event Viewer and confirm Error 24 no longer appears after a few read/write operations or a system restart.
• If the error persists, test the drive in another PC or enclosure — if it still throws Error 24, the drive itself may be failing and should be backed up and replaced.

Windows 11 Error 25: “The Drive Cannot Locate a Specific Area or Track on the Disk”

Why This Error Happens

Error 25 typically occurs when the operating system encounters bad sectors, file system corruption, or a failing physical disk that prevents the read/write head from properly seeking to a requested location. This can also result from outdated or corrupted disk controller drivers that mismanage low-level disk addressing commands. In some cases, a loose or degraded SATA/power cable connection introduces communication errors that manifest as track-location failures.

Step-by-Step Resolution Guide

1. Run CHKDSK to scan and repair the file system:

• Open Command Prompt as Administrator (search “cmd” → Run as administrator).
• Type: chkdsk C: /f /r /x (replace C: with the affected drive letter).
• Press Y if prompted to schedule the scan on next restart, then reboot.

1. Update or reinstall the disk drivers:

• Open Device Manager (Win + X → Device Manager).
• Expand Disk drives, right-click your hard drive/SSD, and select Update driver.
• Choose Search automatically for drivers. If that fails, select Uninstall device and restart Windows to force a clean driver reinstall.

1. Check disk health using PowerShell:

• Open Windows PowerShell as Administrator.
• Run: Get-PhysicalDisk | Select DeviceID, HealthStatus, OperationalStatus.
• If HealthStatus shows “Warning” or “Unhealthy,” the drive may be physically failing and require replacement.

1. Inspect physical connections (for internal desktop drives):

• Power down the PC, open the case, and reseat the SATA and power cables on both the drive and motherboard.
• Try connecting the drive to a different SATA port if available.

1. Update storage controller drivers via manufacturer:

• Visit your motherboard or SSD/HDD manufacturer’s website (e.g., Intel, AMD, Samsung, Western Digital) and download the latest AHCI/RAID/NVMe controller driver.
• Install it manually and restart your system.

Alternative or Verification Steps

• After completing the steps above, re-run chkdsk C: /scan to confirm no further disk errors are reported, and check Event Viewer (Windows Logs > System) for recurring Error 25 entries.
• If the error persists on the same drive, use a manufacturer diagnostic tool (e.g., Seagate SeaTools, WD Dashboard, or Samsung Magician) to run a full surface scan—persistent failures indicate the drive needs to be backed up immediately and replaced.

Troubleshooting Guide: Error 26 – “The Specified Disk or Diskette Cannot Be Accessed” (Windows 11)

Why This Error Happens

Error 26 typically occurs when the Windows I/O subsystem cannot communicate properly with a disk due to corrupted file system structures, a failing or loose disk connection, or outdated/corrupted storage drivers. It can also result from disk read/write permission restrictions imposed by the OS or third-party security software, or from bad sectors preventing the disk controller from completing a read/write operation. In some cases, this error surfaces after an improper shutdown or sudden power loss that left the disk metadata in an inconsistent state.

Step-by-Step Resolution Guide

1. Run CHKDSK to repair file system errors
   Open Command Prompt as Administrator and run:

   chkdsk C: /f /r /x

Replace C: with the affected drive letter. If prompted, type Y and restart your PC to allow the scan to run before Windows loads.

2. Update or reinstall the storage controller driver

• Go to Device Manager → expand Disk drives and Storage controllers.
• Right-click the relevant disk/controller → Update driver → Search automatically for drivers.
• If the issue persists, uninstall the driver (check “Delete the driver software for this device”) and restart to let Windows reinstall a fresh copy.

2. Check physical/cable connections (for external or secondary internal drives)

• Disconnect and reconnect the USB cable or SATA/power connector.
• Try a different USB port (preferably USB 3.0 directly on the motherboard, not a hub) or a different SATA cable.

2. Verify disk permissions and drive letter assignment

• Open Disk Management (diskmgmt.msc).
• Right-click the problematic partition → Properties → Security tab, and ensure your user account/SYSTEM has Full Control.
• If the drive shows as “Unallocated” or without a letter, right-click → Change Drive Letter and Paths and assign one manually.

2. Run SFC and DISM to repair system file corruption
   In an elevated Command Prompt, run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart the PC after completion.

Alternative or Verification Steps

• Verify the fix: Reopen File Explorer and attempt to access the drive/folder that previously triggered Error 26. Also re-run chkdsk C: /scan to confirm no errors remain.
• Alternative fix: If the drive is failing physically (confirmed via wmic diskdrive get status or a tool like CrystalDiskInfo showing “Bad” health), back up your data immediately and replace the disk, as software-level fixes won’t resolve hardware degradation.

Windows 11 Error 27: “The Drive Cannot Find the Sector Requested”

Why This Error Happens

Error 27 typically occurs when the operating system attempts to read or write data to a specific physical location on a disk, but that sector is either physically damaged, has been remapped incorrectly, or is unreadable due to file system corruption. This is often triggered by aging hard drive hardware, abrupt power loss during a write operation, or a failing controller that disrupts the mapping between logical block addresses and physical sectors. In some cases, it stems from a corrupted Master File Table (MFT) or partition table rather than the physical media itself.

Step-by-Step Resolution Guide

1. Run CHKDSK to scan and repair the file system:
   Open Command Prompt as Administrator (right-click Start > Terminal (Admin)) and run:

   chkdsk C: /f /r /x

Replace C: with the affected drive letter. If the drive is your system drive, Windows will prompt you to schedule the scan on next restart—type Y and reboot.

2. Check disk health using WMIC or PowerShell:
   Run PowerShell as Administrator and execute:

   Get-PhysicalDisk | Select FriendlyName, HealthStatus, OperationalStatus

If HealthStatus returns “Unhealthy” or “Warning,” the drive may have hardware-level sector damage rather than a software issue.

3. Update or reinstall the storage controller driver:
   Go to Device Manager > Disk Drives, right-click your drive, select Update Driver. Then expand IDE ATA/ATAPI Controllers, right-click your SATA/NVMe controller, and choose Uninstall device, followed by a system restart to force Windows to reinstall a clean driver.

4. Run SFC to repair corrupted system files:
   In an elevated Command Prompt, run:

   sfc /scannow

This resolves cases where Error 27 is triggered by corrupted system files referencing bad sector locations rather than the disk itself.

5. Check SMART data with a third-party tool (e.g., CrystalDiskInfo):
   If SMART attributes show reallocated sector counts rising or pending sectors, this confirms physical degradation, and the drive should be backed up immediately and replaced.

Alternative or Verification Steps

• After running CHKDSK, re-run chkdsk C: /f (without /r) to confirm no new errors are logged, and check Event Viewer > Windows Logs > System for absence of new Event ID 27 entries.
• If errors persist after these steps, use wbadmin start backup or a cloning tool (e.g., Macrium Reflect) to image the drive immediately and replace the hardware, as repeated Error 27 occurrences strongly indicate irreversible physical sector damage.

Troubleshooting Guide: Printer Error 28 (“Out of Paper”) on Windows 11

Why This Error Happens

Error 28 is typically triggered by the print spooler receiving a status signal from the printer’s sensor indicating that the paper tray is empty or improperly seated. This can occur due to an actual lack of paper, a misaligned paper tray sensor, dust/debris blocking the sensor, or a corrupted print spooler cache retaining an outdated “no paper” status even after paper has been reloaded. In some cases, outdated or corrupted printer drivers on Windows 11 fail to correctly poll the printer’s real-time hardware status, causing the OS to display a stale error.

Step-by-Step Resolution Guide

1. Physically inspect the paper tray
   Remove the paper tray completely, fan the paper stack to release static, and reload it ensuring it sits flush against the tray’s back guide. Reinsert the tray firmly until you hear/feel it click into place.

2. Clean the paper sensor
   Locate the small optical sensor (usually a small plastic tab or lens) inside the paper tray or feed area. Gently wipe it with a dry, lint-free cloth to remove dust or paper residue that may be blocking the sensor.

3. Clear the Print Spooler queue and restart the service

• Press Win + R, type services.msc, and press Enter.
• Locate Print Spooler, right-click and select Stop.
• Navigate to C:\Windows\System32\spool\PRINTERS and delete all files in this folder.
• Go back to Services, right-click Print Spooler, and select Start.

1. Update or reinstall the printer driver

• Go to Settings > Bluetooth & devices > Printers & scanners.
• Select your printer, click Remove device.
• Visit the manufacturer’s website, download the latest Windows 11–compatible driver, and reinstall the printer.

1. Run the Windows Printer Troubleshooter

• Go to Settings > System > Troubleshoot > Other troubleshooters.
• Click Run next to Printer and follow the on-screen prompts to detect and fix status miscommunication issues.

Alternative or Verification Steps

• Verify the fix: Print a test page via Settings > Bluetooth & devices > Printers & scanners > [Your Printer] > Print test page. If it completes without the Error 28 prompt, the issue is resolved.
• Alternative solution: If the error persists, perform a power cycle on the printer itself (unplug for 60 seconds) to reset its internal sensor firmware, then reconnect and retry printing from Windows 11.

Troubleshooting Guide: Error 29 – “The System Cannot Write to the Specified Device” (Windows 11)

Why This Error Happens

Error 29 typically occurs when Windows attempts to write data to a hardware device—such as a printer port, disk drive, or removable media—but the device is unresponsive, disconnected, or lacks the necessary driver configuration. This is commonly triggered by a corrupted or outdated device driver, a port conflict where the assigned port (e.g., LPT1, COM port) is unavailable or in use by another process, or write protection enabled on the target device. In some cases, a failing storage controller or damaged file system on the device can also produce this error.

Step-by-Step Resolution Guide

1. Check Device Connection and Write Protection
   Ensure the device (USB drive, printer, external HDD) is securely connected. If it’s removable media, check for a physical write-protection switch and disable it.

2. Update or Reinstall the Device Driver

• Press Win + X and select Device Manager.
• Locate the device throwing the error (often under Disk drives, Ports (COM & LPT), or Universal Serial Bus controllers).
• Right-click the device → Update driver → Search automatically for drivers.
• If updating doesn’t help, right-click → Uninstall device, then restart your PC to force Windows to reinstall a fresh driver.

1. Verify Port Assignment (for Printers)

• Go to Settings → Bluetooth & devices → Printers & scanners.
• Select the affected printer → Printer properties → Ports tab.
• Confirm the correct port is selected and not conflicting with another device. Reassign to a different port (e.g., USB001) if necessary.

1. Run CHKDSK to Repair File System Errors

• Open Command Prompt as Administrator.
• Type chkdsk X: /f /r (replace X: with the affected drive letter) and press Enter.
• Allow the scan to complete; restart the PC if prompted.

1. Check Registry for Write Restrictions

• Press Win + R, type regedit, and press Enter.
• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorageDevicePolicies.
• If a WriteProtect key exists with a value of 1, change it to 0 and restart your PC.

Alternative or Verification Steps

• Verify the fix: Try writing a test file to the device (e.g., copy a small document) to confirm the error no longer appears.
• Alternative solution: If the issue persists, test the device on another PC or port—if it still fails, the device itself may be faulty and require replacement.

Why This Error Happens

Error 30 with the message “The system cannot read from the specified device” typically occurs when Windows encounters a driver conflict, corrupted registry entries for storage controllers (especially upper/lower filter drivers), or a hardware communication failure with an optical drive, USB device, or external storage. This is commonly triggered after a Windows Update, driver installation, or when third-party disc-burning/virtual drive software leaves orphaned filter drivers in the registry. In some cases, physical connection issues (loose SATA/USB cables) or outdated firmware on the device also cause this error.

Step-by-Step Resolution Guide

1. Check Device Manager for driver errors

• Press Win + X → select Device Manager.
• Expand DVD/CD-ROM drives (or the relevant device category, e.g., Disk drives/Universal Serial Bus controllers).
• Right-click the affected device → Uninstall device → check “Attempt to remove the driver” if prompted → restart your PC. Windows will reinstall the default driver automatically.

1. Remove Upper/Lower Filter Registry Keys (common fix for optical drives)

• Press Win + R, type regedit, and hit Enter.
• Navigate to:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
• Look for the values UpperFilters and LowerFilters in the right pane.
• Right-click each and select Delete (back up the registry first via File > Export).
• Restart your computer.

1. Update or Reinstall Chipset and Storage Drivers

• Go to Settings > Windows Update > Advanced options > Optional Updates > Driver updates.
• Install any pending storage controller or chipset driver updates.
• Alternatively, visit your motherboard/laptop manufacturer’s support page and manually download the latest SATA/USB/chipset drivers.

1. Run Hardware and Devices Troubleshooter

• Open Command Prompt as Administrator.
• Run: msdt.exe -id DeviceDiagnostic
• Follow the on-screen prompts to let Windows detect and fix device-related issues automatically.

1. Check Physical Connections and Firmware

• For internal drives, reseat the SATA and power cables.
• For external/USB devices, try a different USB port or cable.
• Check the manufacturer’s website for firmware updates for the specific drive/device.

Alternative or Verification Steps

• Verify the fix: Open File Explorer and try reading/writing data to the affected device. Also recheck Device Manager to confirm no yellow warning icons remain on the device.
• Alternative fix: If the error persists, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt to repair corrupted system files that may be affecting device communication.

Troubleshooting Guide: Error 31 – “A Device Attached to the System Is Not Functioning”

Why This Error Happens

Error 31 typically occurs when Windows 11 cannot properly communicate with a device due to a corrupted, outdated, or incompatible driver. This can also result from Windows failing to load the correct driver during boot, conflicting legacy drivers left behind after a hardware change, or corrupted entries in the Windows Registry related to the device. In some cases, a firmware mismatch or a faulty USB controller/port can also trigger this error.

Step-by-Step Resolution Guide

1. Check Device Manager for the Faulty Device
   Press Win + X and select Device Manager. Locate the device showing a yellow warning icon (usually under categories like “Other devices,” “Universal Serial Bus controllers,” or the relevant hardware category).

2. Update or Reinstall the Driver
   Right-click the problematic device and select Update driver > Search automatically for drivers. If Windows doesn’t find an update, go to the manufacturer’s website, download the latest driver for Windows 11, and install it manually.

3. Uninstall and Rescan for Hardware Changes
   Right-click the device and select Uninstall device (check the box for “Attempt to remove the driver” if available). Restart your PC, then go to Device Manager > Action > Scan for hardware changes to let Windows reinstall the driver fresh.

4. Clear Corrupted Registry Entries (Advanced)
   Open Registry Editor (regedit) and navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum
   Locate the device’s subkey (identifiable by the hardware ID), back up the key by exporting it, then delete it. Restart your PC to let Windows regenerate clean entries.

5. Check for Firmware/BIOS Updates
   Visit your motherboard or laptop manufacturer’s support page and install the latest BIOS/UEFI firmware update, as outdated firmware can cause communication failures with connected hardware.

Alternative or Verification Steps

• After completing the steps, reopen Device Manager and confirm the yellow warning icon is gone and the device status reads “This device is working properly.”
• If the issue persists, try connecting the device to a different USB port (preferably directly on the motherboard rather than a hub) or test it on another PC to rule out a hardware failure.

Troubleshooting Guide: Error 32 – “The process cannot access the file because it is being used by another process”

Why This Error Happens

Error 32 occurs when Windows 11 attempts to access, move, delete, or modify a file that is currently locked by another running process, service, or application. This file lock is a Windows mechanism designed to prevent data corruption when multiple programs try to write to the same file simultaneously. Common culprits include background services (like Windows Search Indexer or antivirus software), applications left open in the background, or orphaned processes that failed to release the file handle after closing.

Step-by-Step Resolution Guide

1. Identify the Locking Process using Resource Monitor

• Press Win + R, type resmon, and hit Enter.
• Go to the CPU tab, and in the Associated Handles search box at the bottom, type the file name (e.g., report.docx).
• Note the Process ID (PID) and name of the process locking the file.

1. End the Locking Task via Task Manager

• Press Ctrl + Shift + Esc to open Task Manager.
• Locate the process identified in Step 1 (match by PID under the Details tab).
• Right-click the process and select End Task. Retry your original file operation.

1. Restart Windows Explorer

• In Task Manager, find Windows Explorer under the Processes tab.
• Right-click and select Restart. This clears many temporary file locks caused by File Explorer previews or thumbnails without requiring a full reboot.

1. Check for Third-Party Antivirus/Backup Software Interference

• Temporarily disable real-time scanning in your antivirus software (e.g., Windows Defender, McAfee, Norton) via its settings panel.
• Attempt the file operation again. If successful, add an exclusion for the specific file/folder in your antivirus settings to prevent future locks.

1. Use a Dedicated Unlocking Tool (If Steps 1-4 Fail)

• Download and install a trusted utility like LockHunter or Unlocker.
• Right-click the problematic file and select the tool’s “Unlock” option to forcibly release the handle.

Alternative or Verification Steps

• Verify the Fix: After completing the steps, attempt to move, rename, or delete the file again. If successful with no error prompt, the lock has been released.
• Alternative (Boot into Safe Mode): If the error persists due to a stubborn system-level process, restart into Safe Mode (Shift + Restart > Troubleshoot > Advanced Options > Startup Settings > Safe Mode) and perform the file operation there, as this loads minimal background services.

Why This Error Happens

Error 33 occurs when the Windows I/O subsystem attempts to read, write, or delete a file while another process holds an exclusive lock on a byte range within that file. This is typically caused by a background service (like Windows Search Indexer, OneDrive sync, or antivirus real-time scanning) actively holding a handle to the file, or by a previous application crash that failed to release its file lock properly. Network file shares (SMB) using opportunistic locking (oplocks) can also trigger this error when multiple clients access the same file simultaneously.

Step-by-Step Resolution Guide

1. Identify the locking process using Resource Monitor

• Press Win + R, type resmon, and press Enter.
• Go to the CPU tab, expand Associated Handles, and search for the locked file name.
• Note the Process ID (PID) shown in the results.

1. End the locking process safely

• Open Task Manager (Ctrl + Shift + Esc), click the Details tab.
• Locate the PID from Step 1, right-click it, and select End Task.
• If it’s a critical system process, restart the associated service instead via services.msc.

1. Disable Windows Search Indexing temporarily (common culprit for Error 33)

• Open services.msc, find Windows Search.
• Right-click → Stop, then set Startup type to Disabled temporarily.
• Retry the file operation.

1. Exclude the file/folder from antivirus scanning

• Go to Windows Security → Virus & threat protection → Manage settings.
• Under Exclusions, click Add or remove exclusions and add the affected file path (e.g., C:\Users\<YourName>\Documents\filename.ext).

1. Check for SMB/network share locking (if file is on a network drive)

• Open PowerShell as Administrator and run:
  
Get-SmbOpenFile | Where-Object { $_.Path -like "*filename*" }

• Use Close-SmbOpenFile -FileId <ID> to forcibly release the lock.

Alternative or Verification Steps

• After completing the steps, retry the original file operation (copy, delete, or save) — it should complete without the Error 33 prompt.
• If the issue persists, boot into Safe Mode (Settings → Recovery → Advanced Startup) and attempt the file operation there; if it succeeds, a third-party background service or driver is likely the root cause.

Troubleshooting Guide: Error 34 – “The Wrong Diskette Is in the Drive”

Why This Error Happens

Error 34 is a legacy I/O status message (ERROR_WRONG_DISK) generated by the Windows I/O manager when a process expects a specific removable volume—identified by its Volume Serial Number—but detects a different disk, or no disk, in the target drive letter. On modern Windows 11 systems, this typically surfaces not from actual floppy diskettes, but from legacy applications, batch scripts, backup software, or virtual drive mounting utilities that reference a removable/mapped drive letter and validate against a cached Volume Serial Number (VSN) that no longer matches the currently inserted media. It can also occur if the Volume Serial Number changed due to a reformat, or if drive letter mapping got reassigned by Windows.

Step-by-Step Resolution Guide

1. Identify the drive and expected volume
   Note the drive letter (%1), expected volume label (%2), and Volume Serial Number (%3) from the error message.

2. Verify current media in the drive
   Open File Explorer → right-click the drive → Properties. Check the Volume Serial Number in the General tab (or run vol %1: in an elevated Command Prompt) and compare it to the expected value in the error.

3. Insert/Mount the correct media

• For physical removable media (USB, external HDD, optical disc): eject and insert the correct disk/drive that matches the label and serial number.
• For virtual disk images (ISO/VHD): go to File Explorer, locate the correct .iso or .vhd file, right-click → Mount, ensuring it’s assigned to the expected drive letter.

1. Reassign the drive letter if mismatched
   Open Disk Management (diskmgmt.msc) → right-click the correct volume → Change Drive Letter and Paths → set it to match the letter (%1) the application expects.

2. Update or reconfigure the calling application
   If using backup software, imaging tools, or legacy scripts, open its configuration and update the referenced Volume Serial Number/drive mapping to reflect the current media, since VSNs regenerate after reformatting.

Alternative or Verification Steps

• Run chkdsk %1: in an elevated Command Prompt to confirm the drive is healthy and correctly recognized before retrying the operation.
• If the error persists, uninstall and reinsert the device via Device Manager (devmgmt.msc) → Disk drives → right-click → Uninstall device, then reconnect it to force Windows to re-enumerate the volume.

Troubleshooting Guide: Error 36 – “Too Many Files Opened for Sharing” (Windows 11)

Why This Error Happens

Error 36 occurs when the SMB (Server Message Block) file sharing service exceeds the maximum number of concurrently open file handles allowed by the system’s registry configuration. This typically happens on systems with default consumer-grade sharing limits that are set too low for the actual network load, especially when multiple users or applications access shared folders simultaneously. It can also be triggered by a misconfigured MaxWorkItems or MaxMpxCt registry value, or by an unusually high number of small files being accessed at once through a single share.

Step-by-Step Resolution Guide

1. Open the Registry Editor
   Press Win + R, type regedit, and press Enter. Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

2. Increase the MaxMpxCt value
   Look for a DWORD value named MaxMpxCt. If it doesn’t exist, right-click the Parameters folder → New → DWORD (32-bit) Value, name it MaxMpxCt, and set its value (in Decimal) to 500 or higher (default is often 50).

3. Adjust MaxWorkItems (if present)
   In the same key, check for MaxWorkItems. Set this to 65535 (Decimal) to allow more simultaneous work requests to be processed by the server service.

4. Increase the Irpstacksize
   Navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters
   Add or modify a DWORD value named IRPStackSize and set it to 20 (Decimal) — this allocates more memory for I/O request packets, which is often the direct cause of “too many files open” errors.

5. Restart the Server Service
   Open Command Prompt as Administrator and run:

   net stop server
   net start server

Alternatively, restart the machine to ensure the registry changes take full effect.

Alternative or Verification Steps

• Verify the fix: Re-access the shared folder from multiple client machines simultaneously and check Event Viewer (Windows Logs > System) to confirm Error 36 no longer appears under the source Srv.
• Alternative fix: If the error persists, reduce the number of files being shared per folder by splitting large directories into multiple smaller shares, or upgrade to Windows Server for higher built-in SMB connection limits.

Windows 11 Troubleshooting Guide: Error 38 – “Reached the End of the File”

Why This Error Happens

Error 38 occurs when a program attempts to read beyond the actual data stored in a file, typically because the file is truncated, corrupted, or was not closed properly during a previous write operation. This is commonly triggered by abrupt system shutdowns, disk errors, or a mismatch between the expected file size (recorded in file metadata) and the actual bytes present on disk. It can also surface when antivirus software or a failed disk sector interrupts read/write operations mid-process, leaving the file in an inconsistent state.

Step-by-Step Resolution Guide

1. Run CHKDSK to repair file system errors
   Open Command Prompt as Administrator (search “cmd” → Run as administrator) and execute:

   chkdsk C: /f /r

Press Y to schedule the scan on next restart, then reboot your PC. This scans for and repairs corrupted sectors or file table inconsistencies causing the truncation.

2. Check Event Viewer for the specific failing file/application
   Press Win + X → Event Viewer → navigate to Windows Logs > Application (or System). Filter by Event ID 38 and note the exact file path and source application generating the error to isolate whether it’s OS-related or application-specific.

3. Verify system file integrity
   In an elevated Command Prompt, run:

   sfc /scannow

followed by:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted Windows system files that may be causing incomplete reads.

4. Restore or replace the affected file
   If the error points to a specific document, log, or config file (not a system file), restore it from a previous version:

• Right-click the file → Properties → Previous Versions tab → restore an earlier backup.
• Alternatively, retrieve a clean copy from File History or OneDrive backup if enabled.

4. Check disk health status
   Run wmic diskdrive get status in Command Prompt, or use Settings > System > Storage > Disks & volumes to check for “Needs attention” warnings, indicating failing hardware that repeatedly truncates files during writes.

Alternative or Verification Steps

• After completing the steps above, reopen the file or relaunch the application that triggered Error 38 and confirm it loads/reads to completion without interruption.
• If the error persists, use a dedicated file-repair tool appropriate to the file type (e.g., built-in repair for Office documents, or esentutl /p for database-like files) since CHKDSK only fixes disk-level issues, not internal file corruption.

Why This Error Happens

Error 17 (ERROR_NOT_SAME_DEVICE) occurs because Windows 11 handles file “moves” differently depending on whether the source and destination are on the same volume. Moving a file within the same disk is a simple rename operation in the file system table, but moving it to a different drive requires a full copy-then-delete operation. This error typically surfaces when a script, command-line tool (like MoveFile API calls, robocopy, or batch scripts), or an application explicitly calls a “rename” function instead of a “copy” function to relocate a file across drives, and the underlying API refuses because it only supports same-volume renames.

Step-by-Step Resolution Guide

1. Identify the operation type: If you’re using a command line, avoid move in contexts expecting same-volume behavior. Instead, use robocopy for cross-drive transfers:

   robocopy "C:\SourceFolder" "D:\DestinationFolder" filename.ext /MOV

The /MOV flag copies the file to the destination and deletes the original after a successful copy, correctly handling cross-drive moves.

2. Check the application or script causing the error: If a third-party app or custom script triggers Error 17, open the script/config file and locate the function performing the move (e.g., MoveFileEx, os.rename() in Python, or Rename-Item in PowerShell). Replace rename-based logic with copy-then-delete logic:

• PowerShell fix: replace Rename-Item with Copy-Item followed by Remove-Item.

2. Verify drive letters and paths: Confirm the source and destination paths actually point to different physical/logical drives (e.g., C:\ vs D:\). Check via File Explorer > This PC, or run:

   wmic logicaldisk get name

4. Update or repair the application: If a specific program (backup software, file manager, sync tool) throws Error 17, check for updates via Settings > Apps > Installed apps, or reinstall the app, as older versions may lack proper cross-volume move handling.

5. Run System File Checker to rule out corrupted system files affecting file operation APIs:

   sfc /scannow

Restart your PC after the scan completes.

Alternative or Verification Steps

• Verify the fix: Attempt the same move operation again using robocopy /MOV or manually copy the file via File Explorer (drag-and-drop across drives), then confirm the source file is removed and destination file is intact.
• Alternative workaround: If scripting is not required, simply drag and drop the file between drives in File Explorer — this always performs a copy+delete under the hood and will not trigger Error 17.

Windows 11 Error 18 – “There Are No More Files” Troubleshooting Guide

Why This Error Happens

Error 18 (“There are no more files”) is a Windows system error code that typically occurs when an application or process attempts to enumerate files in a directory using an iteration function (like FindNextFile), but the enumeration has reached the end of the available file list prematurely or unexpectedly. This often happens due to a corrupted file index, a damaged Master File Table (MFT) entry, or a third-party application mishandling the end-of-directory signal from the Windows API. It can also surface when backup software, installers, or file-copy utilities encounter an interrupted or incomplete directory listing caused by disk corruption or a faulty storage driver.

Step-by-Step Resolution Guide

1. Run CHKDSK to repair file system errors
   Open Command Prompt as Administrator (search “cmd,” right-click, “Run as administrator”) and run:

   chkdsk C: /f /r

Press Y to schedule the scan on next restart, then reboot your PC to let it complete.

2. Run System File Checker (SFC) and DISM
   In an elevated Command Prompt, run:

   sfc /scannow

Once complete, run:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be interfering with file enumeration processes.

3. Update or reinstall the storage/disk driver
   Go to Device Manager > Disk drives, right-click your primary drive, select Update driver > Search automatically for drivers. If already up to date, try Uninstall device, then restart Windows 11 to let it reinstall the driver fresh.

4. Check the specific application triggering the error
   If Error 18 appears in a specific app (backup tool, FTP client, installer), verify the app is updated to the latest version and check the source/destination folder for it isn’t pointing to a network drive or removable media that disconnected mid-operation.

5. Inspect the affected folder for corruption
   Navigate to the folder path referenced in the error (visible in Event Viewer under Windows Logs > Application). Try copying its contents to a new folder using File Explorer; if copying fails or hangs, the folder structure itself may be corrupted and should be rebuilt.

Alternative or Verification Steps

• Verify the fix: Re-run the operation that originally triggered Error 18 (e.g., backup job, file copy, or installation) and confirm it completes without interruption. Also check Event Viewer (Event ID 18) to confirm no new instances are logged.
• Alternative fix: If the error persists, create a new user profile in Settings > Accounts > Other users, and test the same operation under that profile — this helps isolate whether the issue is profile-specific corruption versus a system-wide disk problem.

Why This Error Happens

Error 19 with the message “The media is write protected” typically occurs when Windows detects a read-only flag on a storage device, such as a USB drive, SD card, or external hard disk. This can be caused by a physical write-protection switch on the device, a software-level attribute set via disk management (like the “Read-only” flag in DiskPart), or a registry key (WriteProtect) that globally restricts write access to removable media. Corrupted file system structures or outdated USB/storage drivers can also trigger this error even when no physical protection is active.

Step-by-Step Resolution Guide

1. Check for a physical write-protection switch
   Many USB flash drives and SD cards have a small physical lock switch on the side. Slide it to the unlocked position, then reconnect the device.

2. Clear the write-protection flag using DiskPart

• Press Win + X, select Terminal (Admin).
• Type diskpart and press Enter.
• Type list disk and identify your device (e.g., Disk 1).
• Type select disk 1 (replace with your disk number).
• Type attributes disk clear readonly.
• Type exit and reconnect the device.

1. Check the Windows Registry for a global write-protect policy

• Press Win + R, type regedit, and press Enter.
• Navigate to:
  HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\StorageDevicePolicies
• If the key WriteProtect exists, ensure its value is set to 0. If the entire StorageDevicePolicies key doesn’t exist, this isn’t the cause—skip to the next step.
• Restart your PC after making changes.

1. Update or reinstall the USB/storage controller drivers

• Open Device Manager (Win + X → Device Manager).
• Expand Universal Serial Bus controllers and Disk drives.
• Right-click your device and select Update driver or Uninstall device, then reconnect to let Windows reinstall it.

1. Run CHKDSK to repair file system errors

• Open Terminal (Admin).
• Type chkdsk X: /f /r (replace X: with your drive letter) and press Enter.
• Allow the scan to complete and repair any detected errors.

Alternative or Verification Steps

• After applying a fix, try creating a new folder or copying a small file to the drive to confirm write access is restored.
• If the issue persists, test the device on another PC—if it’s still read-only, the drive itself may be physically damaged or nearing end-of-life and should be replaced.

Windows 11 Error 15: “The System Cannot Find the Drive Specified”

Why This Error Happens

Error 15 occurs when Windows attempts to access a drive letter, path, or volume that is no longer available, improperly mapped, or not correctly registered in the system. This is commonly caused by disconnected external drives, unmapped network shares, corrupted drive letter assignments in the registry, or a mismatch between a script/application’s hardcoded path and the actual current drive configuration. It can also result from driver issues where the operating system fails to properly enumerate the storage device during boot or reconnection.

Step-by-Step Resolution Guide

1. Verify the drive is physically connected and recognized:
   Open Disk Management (Win + X → Disk Management) and confirm the drive appears in the list. If it shows as “Not Initialized” or “Unallocated,” the drive itself may have an issue rather than a software configuration problem.

2. Reassign the drive letter manually:
   In Disk Management, right-click the drive → Change Drive Letter and Paths → Change. Assign a new, unused letter (e.g., E:) and click OK. This resolves conflicts where Windows reserved the letter for another device or network resource.

3. Re-map network drives if applicable:
   If the missing drive is a network share, open File Explorer → This PC → Map network drive. Re-enter the UNC path (e.g., \\ServerName\ShareName) and check Reconnect at sign-in to prevent the mapping from dropping after reboot.

4. Update or reinstall the storage controller driver:
   Open Device Manager → expand Disk drives and Storage controllers. Right-click the relevant device → Update driver. If no update is found, try Uninstall device, then restart Windows 11 to force a clean driver reinstallation.

5. Check and repair the registry mount points (advanced):
   Press Win + R, type regedit, and navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices
   Look for stale or duplicate entries referencing the missing drive letter and remove only the specific corrupted entry (back up the registry first via File → Export).

Alternative or Verification Steps

• Verify the fix: Reopen the application or script that triggered Error 15 and confirm it can now read/write to the drive without the error reappearing after a restart.
• Alternative solution: If the issue persists, run chkdsk X: /f (replacing X with the drive letter) in an elevated Command Prompt to repair underlying file system corruption that may be preventing Windows from recognizing the volume.

Why This Error Happens

Error 16 (ERROR_CURRENT_DIRECTORY) occurs when Windows attempts to delete a folder that is currently set as the active/working directory for a running process, such as Command Prompt, PowerShell, or an open application. It can also occur if a file handle inside that directory is still locked by File Explorer, an antivirus scanner, or a background service. Because Windows won’t let a process delete the directory it’s actively “standing in” or referencing, the removal request fails until that lock is released.

Step-by-Step Resolution Guide

1. Close all terminals and apps pointing to that folder
   Close every open Command Prompt, PowerShell, or Windows Terminal window, as well as any File Explorer windows currently browsing inside the target directory.

2. Change directory before deleting (if using CLI)
   If you’re deleting via script or terminal, ensure you cd out of the folder first:

   cd C:\
   rmdir /s /q "C:\Path\To\Folder"

Never run a delete command while your shell’s current path is inside the folder you’re removing.

3. Check for locked files using Resource Monitor

• Press Win + R, type resmon, and hit Enter.
• Go to the CPU tab → Associated Handles.
• Search for the folder name and end any process holding a handle to it.

3. Use Process Explorer to find hidden locks
   Download Sysinternals Process Explorer, use Find > Find Handle or DLL, search the folder path, and close the identified process.

4. Force delete via Safe Mode (last resort)
   Restart Windows 11 into Safe Mode (Settings > System > Recovery > Advanced Startup > Restart Now > Troubleshoot > Advanced Options > Startup Settings > Safe Mode), then delete the folder — this ensures no background apps or services are holding a lock.

Alternative or Verification Steps

• After deletion, run dir "C:\Path\To\Folder" in Command Prompt — if it returns “File Not Found,” the removal was successful.
• If the issue persists, try deleting the folder using a bootable Windows PE / recovery USB, which bypasses all Windows-session file locks entirely.

Windows Error 147: “Not Enough Resources Are Available to Process This Command”

Why This Error Happens

Error 147 typically occurs when the Windows system runs out of available memory resources, virtual memory, or when there’s a conflict in the system’s paging file configuration. This is often triggered by insufficient RAM allocation, a corrupted or undersized virtual memory (pagefile.sys) setting, or too many background processes consuming system handles simultaneously. In some cases, outdated drivers or a fragmented system resource pool can also prevent Windows from allocating the necessary resources to execute a command.

Step-by-Step Resolution Guide

1. Increase Virtual Memory (Pagefile Size)

• Press Win + R, type sysdm.cpl, and press Enter.
• Go to the Advanced tab → click Settings under Performance → Advanced tab → click Change under Virtual Memory.
• Uncheck “Automatically manage paging file size for all drives.”
• Select your system drive (usually C:), choose Custom Size, and set Initial Size to 1.5x your RAM (in MB) and Maximum Size to 3x your RAM.
• Click Set, then OK, and restart your PC.

1. Close Unnecessary Background Processes

• Open Task Manager (Ctrl + Shift + Esc).
• Go to the Processes tab and sort by Memory usage.
• End tasks for non-essential applications consuming high resources.

1. Run a System File Checker (SFC) Scan

• Open Command Prompt as Administrator.
• Run: sfc /scannow
• Allow the scan to complete and repair any corrupted system files, then restart.

1. Update or Reinstall Device Drivers

• Press Win + X → select Device Manager.
• Look for devices with a yellow warning icon (especially network or storage drivers).
• Right-click → Update driver → Search automatically for drivers.

1. Check for Windows Updates

• Go to Settings → Windows Update → click Check for updates.
• Install any pending updates and restart your system.

Alternative or Verification Steps

• Verify the fix: Reopen the application or rerun the command that triggered Error 147. Monitor Task Manager’s Performance tab to confirm memory and CPU usage are stable (not maxed out).
• Alternative solution: If the error persists, consider adding physical RAM to your system or running chkdsk /f via Command Prompt (Admin) to rule out disk-related resource allocation issues.

Why This Error Happens

Error 148 (“The path specified cannot be used at this time”) typically occurs when Windows 11 cannot resolve a file or folder path because it points to a disconnected network drive, a removable device that was ejected improperly, or a location protected by NTFS permissions. It can also occur when the path contains invalid characters, exceeds the legacy 260-character limit, or references a drive letter currently locked by another process (such as a pending disk operation or Volume Shadow Copy snapshot). In some cases, a corrupted registry entry for a mapped network drive or a broken symbolic link/reparse point is the underlying cause.

Step-by-Step Resolution Guide

1. Verify the path is accessible
   Open File Explorer and manually navigate to the exact path referenced in the error. If it’s a mapped network drive, confirm the server is online and reachable via \\ServerName\ShareName in the address bar.

2. Re-map or reconnect network drives
   Go to This PC > Map network drive, remove the broken mapping, and recreate it. Ensure “Reconnect at sign-in” is checked, then restart the application.

3. Check and reset folder permissions
   Right-click the target folder → Properties > Security > Advanced. Ensure your user account has at least “Read & Execute” permissions. If ownership is incorrect, click Change next to Owner, enter your username, and apply with “Replace owner on subcontainers and objects.”

4. Enable long path support (if path exceeds 260 characters)
   Open Registry Editor (regedit), navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem
   Set LongPathsEnabled to 1 (DWORD), then restart your PC.

5. Run System File Checker and CHKDSK
   Open Command Prompt (Admin) and run:

   sfc /scannow
   chkdsk C: /f /r

Restart when prompted to repair corrupted file system structures that may be blocking path resolution.

Alternative or Verification Steps

• After applying fixes, try accessing or saving to the same path again in the affected application to confirm the error no longer appears.
• If the issue persists, try copying the target file/folder to a local drive (e.g., C:\Temp) and reopening it from there — if this works, the problem is isolated to the network path or permissions rather than the application itself.

Troubleshooting Guide: Error 149 – Drive Substitution Conflict

Why This Error Happens

Error 149 occurs when the SUBST command attempts to map a drive letter to a directory path that already resides on—or is part of—another substituted (virtual) drive. Windows does not allow nested substitutions because it cannot resolve a chain of virtual drive mappings back to a genuine physical or logical disk path. This typically happens when a script, batch file, or leftover configuration tries to SUBST a drive letter using a path from a previously created virtual drive that was never removed.

Step-by-Step Resolution Guide

1. Identify all active substituted drives
   Open Command Prompt (Win + R → type cmd → Enter) and run:

   subst

This lists all current virtual drive mappings, showing which drive letters point to which paths.

2. Remove the conflicting substituted drive
   If you see a drive (e.g., Z:) mapped to a path that overlaps with the one you’re trying to create, remove it:

   subst Z: /D

Repeat for any other conflicting mappings shown in the list.

3. Verify the target path is on a real, non-substituted drive
   Ensure the folder you want to substitute (e.g., C:\Projects\App) resides on an actual physical drive letter (C:, D:, etc.) and not inside another virtual drive’s folder structure.

4. Re-create the substitution correctly
   Once conflicts are cleared, run the SUBST command again using a path rooted in a real drive:

   subst X: C:\Projects\App

5. Check startup scripts or registry entries for persistent SUBST commands
   If the error recurs after reboot, check:

• Task Scheduler for scripts running SUBST
• HKEY_CURRENT_USER\Network (legacy drive mappings)
• Any .bat or .cmd files in the Startup folder (shell:startup)
  Remove or correct any command that references a nested/virtual path.

Alternative or Verification Steps

• Verify the fix: Run subst again after re-mapping to confirm the new drive letter appears correctly without triggering Error 149.
• Alternative solution: If SUBST continues to fail, use Disk Management (diskmgmt.msc) to assign the folder via “Change Drive Letter and Paths” using an NTFS mount point instead, which avoids nested substitution issues entirely.

Troubleshooting Guide: Error 150 – “System Trace Information Was Not Specified in CONFIG.SYS”

Why This Error Happens

Error 150 is a legacy system error rooted in MS-DOS and early Windows architecture, where system tracing had to be explicitly enabled via a CONFIG.SYS file using the TRACE=ON directive. Since Windows 11 no longer relies on CONFIG.SYS for boot-time configuration (it uses the Registry and UEFI/BIOS-based initialization instead), this error typically surfaces when a legacy application, script, or compatibility layer attempts to invoke DOS-based tracing functions that the modern OS kernel doesn’t support natively. It can also occur when an outdated installer or a virtualized/emulated DOS environment (like DOSBox or NTVDM) fails to locate expected system trace hooks.

Step-by-Step Resolution Guide

1. Identify the Triggering Application
   Check the Event Viewer (Win + X → Event Viewer → Windows Logs → Application) to identify which specific program or process threw Error 150. This is usually a legacy 16-bit or DOS-based application.

2. Enable NTVDM (if running a legacy DOS app)
   Windows 11 requires the NTVDM (NT Virtual DOS Machine) feature for older applications:

• Go to Control Panel → Programs → Turn Windows features on or off.
• Enable “NTVDM” or “Windows Legacy Console” if listed (availability depends on your Windows 11 edition and build).
• Restart your PC.

1. Create a Virtual CONFIG.SYS via Compatibility Settings
   Since Windows 11 doesn’t read a real CONFIG.SYS, simulate legacy support:

• Right-click the application’s .exe file → Properties → Compatibility tab.
• Check “Run this program in compatibility mode for:” and select Windows 95 or Windows 98/ME.
• Click Apply, then OK.

1. Use DOSBox for True Legacy Emulation
   If compatibility mode fails, install DOSBox (a full DOS emulator):

• Download DOSBox from the official site and install it.
• Create a CONFIG.SYS file in your mounted DOSBox directory with the line: TRACE=ON.
• Run the application through DOSBox instead of natively in Windows 11.

1. Check for Corrupted or Missing Legacy DLLs
   Run sfc /scannow in an elevated Command Prompt (Win + X → Terminal (Admin)) to repair any corrupted system files that might interfere with legacy subsystem emulation.

Alternative or Verification Steps

• Verify the fix: Relaunch the application and monitor Event Viewer for recurrence of Error 150. If it no longer appears, tracing emulation was successfully bypassed or resolved.
• Alternative: If the software is business-critical and legacy compatibility keeps failing, consider running it inside a Windows XP/98 virtual machine (via Hyper-V or VirtualBox) where a genuine CONFIG.SYS file can be created and read natively.

Why This Error Happens

Error 151 is a legacy Win32 API error code (ERROR_TOO_MANY_MUXWAITERS) originally tied to the OS/2 subsystem’s DosMuxSemWait function, which Windows retained for backward compatibility. It typically surfaces when a poorly coded legacy application, driver, or script requests a multiplexed semaphore wait with an invalid or excessive number of semaphore handles (the API only supports a limited count, historically capped at 16). On Windows 11, this is most often triggered by outdated third-party software, a corrupted legacy DLL, or a faulty driver still calling deprecated 16-bit/OS/2-compatibility APIs.

Step-by-Step Resolution Guide

1. Identify the offending application
   Open Event Viewer (eventvwr.msc) → Windows Logs > Application, filter for Event ID 151, and note the source application or service that logged the error. This is almost always a legacy program, not a core Windows process.

2. Update or reinstall the legacy application
   Check the vendor’s website for a Windows 11–compatible update. If none exists, reinstall the application and run it in Compatibility Mode:

• Right-click the .exe → Properties → Compatibility tab
• Check Run this program in compatibility mode for, select Windows 8 or Windows 7

1. Run System File Checker and DISM
   Corrupted system files can affect legacy API shims. Open Command Prompt (Admin) and run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart after completion.

4. Disable/Update the conflicting driver
   If the error correlates with a specific driver (check Device Manager for warning icons), update it via Device Manager > right-click device > Update driver, or roll back/uninstall it if recently installed.

5. Check for NTVDM/legacy subsystem components
   Ensure the Windows Subsystem for legacy applications isn’t corrupted:

• Go to Control Panel > Programs > Turn Windows features on or off
• If listed, toggle Legacy Components off, restart, then re-enable it.

Alternative or Verification Steps

• After applying fixes, reproduce the original action that triggered Error 151 and confirm Event Viewer no longer logs a new instance of Event ID 151.
• If the error persists, use Process Monitor (Procmon) from Sysinternals to trace which process calls DosMuxSemWait and isolate it for removal or replacement with a modern equivalent.

Troubleshooting Guide: Error 152 – DosMuxSemWait Did Not Execute

Why This Error Happens

Error 152 is a legacy MS-DOS/Win16 compatibility error indicating that too many semaphores (synchronization locks used to manage shared resource access) were already set when a DosMuxSemWait call was attempted. On Windows 11, this typically surfaces not from actual DOS applications, but from legacy drivers, poorly written third-party services, or corrupted system files that improperly handle resource locking, mimicking this old error code. It can also occur due to resource exhaustion caused by a runaway process holding onto handles or semaphores without releasing them.

Step-by-Step Resolution Guide

1. Identify the Offending Process
   Open Event Viewer (Win + X → Event Viewer) and navigate to Windows Logs > Application. Look for the exact timestamp of the Error 152 event and note which application or service triggered it in the “Source” column.

2. Run System File Checker (SFC) and DISM
   Since this error is often tied to corrupted system components, open Terminal (Admin) and run:

   sfc /scannow

Followed by:

   DISM /Online /Cleanup-Image /RestoreHealth

Restart your PC after both commands complete.

3. Update or Remove Legacy Drivers/Software
   Since this error originates from 16-bit/legacy compatibility layers, check Device Manager (devmgmt.msc) for outdated drivers (yellow warning icons). Additionally, review installed programs in Settings > Apps > Installed Apps for any old software (especially printer utilities, VPN clients, or industrial hardware drivers) that may still rely on legacy Win16 subsystems. Uninstall or update them to their latest Windows 11-compatible versions.

4. Check for Resource Leaks via Task Manager
   Open Task Manager (Ctrl + Shift + Esc) and go to the Details tab. Sort by “Handles” (right-click the column header to enable if hidden) to identify if a specific process is consuming an abnormally high number of handles, which can trigger semaphore limits. End the task if a non-critical process is misbehaving.

5. Adjust NTVDM/WOW Compatibility Settings
   If the error stems from a specific legacy application, right-click the application’s .exe file, select Properties > Compatibility, and check Run this program in compatibility mode for, selecting an earlier Windows version (e.g., Windows 7).

Alternative or Verification Steps

• Verify the Fix: Reboot your system and attempt to reproduce the exact action that caused the error. Monitor the Event Viewer for 24 hours to confirm Error 152 does not reappear.
• Alternative Solution: If the error persists and is tied to a specific piece of hardware/software, perform a Clean Boot (via msconfig) to isolate whether a third-party service is causing the semaphore conflict, then re-enable services one by one to pinpoint the culprit.

Why This Error Happens

Error 153 (“The DosMuxSemWait list is not correct”) originates from the legacy OS/2 and 16-bit subsystem calls that Windows still emulates through NTVDM (NT Virtual DOS Machine) and compatibility layers. It typically surfaces when a legacy application, printer driver, or service tries to use the outdated DosMuxSemWait synchronization function with a malformed or corrupted semaphore list — usually because of damaged system files, an outdated/incompatible driver, or leftover corrupted entries from a failed software installation. On Windows 11, this is most commonly triggered by legacy print drivers, old third-party utilities, or a corrupted Windows component store (WinSxS).

Step-by-Step Resolution Guide

1. Run System File Checker and DISM to repair corrupted OS files that may be causing the malformed semaphore call:

• Open Command Prompt as Administrator.
• Run sfc /scannow
• If issues are found, follow up with:
  DISM /Online /Cleanup-Image /RestoreHealth
• Restart your PC after completion.

1. Update or Remove the Legacy Driver/Application triggering the error:

• Open Device Manager (devmgmt.msc), especially check Print queues and Ports (COM & LPT).
• Right-click the suspect device → Update driver → Search automatically.
• If no update exists, uninstall the driver and reinstall the latest version from the manufacturer’s website (avoid drivers older than Windows 10-era unless verified compatible).

1. Check and Reinstall the Application Causing the Error:

• Go to Settings > Apps > Installed apps.
• Locate the legacy or third-party app associated with the error (often utility software or old print/fax tools).
• Uninstall it, restart your PC, then reinstall the latest compatible version.

1. Clear Corrupted Print Spooler Data (common source of DosMuxSemWait errors):

• Press Win + R, type services.msc, and stop the Print Spooler service.
• Navigate to C:\Windows\System32\spool\PRINTERS and delete all files inside.
• Restart the Print Spooler service and test the print job again.

1. Create a New Local User Profile if the error persists only under one user account, as it may indicate a corrupted profile:

• Go to Settings > Accounts > Other users > Add account.
• Sign in with the new profile and retest the failing application.

Alternative or Verification Steps

• Verify the fix: Reproduce the original action (printing, running the legacy app, etc.) that triggered Error 153 — if no error dialog appears and the Event Viewer (eventvwr.msc) shows no new Error 153 entries under Windows Logs > Application, the issue is resolved.
• Alternative fix: If the error persists, perform an in-place upgrade repair using Windows 11 installation media (setup.exe → Keep personal files and apps) to rebuild core system components without a full reinstall.

Why This Error Happens

This error occurs because different file systems enforce different maximum lengths for volume labels: FAT32 allows only 11 characters, while NTFS and exFAT allow up to 32 characters. Error 154 is triggered when you attempt to assign a label longer than what the target drive’s file system supports, typically via the label command, Command Prompt, or PowerShell. This is not a corruption or permissions issue—it’s a hard-coded restriction based on the file system’s internal metadata structure for storing volume names.

Step-by-Step Resolution Guide

1. Identify the file system of the target drive.

• Open File Explorer > right-click the drive > Properties.
• Check the File system field (it will show FAT32, NTFS, or exFAT).

1. Shorten the volume label to fit the limit.

• If the drive is FAT32, ensure your label is 11 characters or fewer (letters, numbers, and limited symbols only—no periods or certain special characters).
• If the drive is NTFS or exFAT, keep the label under 32 characters.

1. Reapply the label using Command Prompt.

• Press Win + X > select Terminal (Admin).
• Run: label D: NEWLABEL (replace D: with your drive letter and NEWLABEL with a compliant name).
• Press Enter — if no error appears, the label has been applied successfully.

1. Alternatively, rename the drive via File Explorer.

• Right-click the drive in This PC > Rename.
• Type a shorter name and press Enter.

1. If you need a longer label, reformat the drive to NTFS or exFAT.

• Right-click the drive > Format.
• Under File system, select NTFS or exFAT (⚠️ this erases all data—back up first).
• Assign your desired volume label (up to 32 characters) during the format process.

Alternative or Verification Steps

• Verify the fix: Open File Explorer, check that the drive now displays the new label correctly without any error prompts.
• Alternative: If reformatting isn’t an option, use the Command Prompt method (label command) with a truncated name that fits the FAT32 11-character limit instead of relying on the graphical rename interface.

Why This Error Happens

Error 155 (“Cannot create another thread”) occurs when the Windows Kernel is unable to allocate the necessary resources for a new thread, typically due to exhaustion of the non-paged memory pool or the process/system hitting its maximum handle and thread limits. This is most commonly caused by a “resource leak” — a poorly coded application, an outdated driver, or a background process that continuously spawns threads/handles without releasing them. In some cases, an undersized Windows page file (virtual memory) prevents the OS from allocating stack space for new threads, especially under heavy multitasking loads.

Step-by-Step Resolution Guide

1. Identify the Resource Hog via Task Manager

• Press Ctrl + Shift + Esc to open Task Manager.
• Go to the Details tab, right-click the column header, and select Select Columns. Enable Threads and Handles.
• Sort by these columns to identify any single process with abnormally high counts (e.g., thousands of threads/handles). End that task if it’s a non-critical app.

1. Increase the Virtual Memory (Page File) Allocation

• Press Win + R, type sysdm.cpl, and hit Enter.
• Go to Advanced > Performance Settings > Advanced tab > Change (under Virtual Memory).
• Uncheck Automatically manage paging file size for all drives.
• Select your system drive (usually C:), choose Custom Size, and set an Initial size of 1.5x your RAM (in MB) and Maximum size of 3x your RAM.
• Click Set, then OK, and restart your PC.

1. Update or Roll Back Faulty Drivers

• Open Device Manager (Win + X > Device Manager).
• Check for devices with a yellow warning icon, particularly under Network Adapters, Display Adapters, or Storage Controllers.
• Right-click the flagged device, select Update Driver, or if the issue started after a recent update, choose Properties > Driver tab > Roll Back Driver.

1. Run System File and Disk Checks

• Open Command Prompt as Administrator (Win + X > Terminal (Admin)).
• Run the following commands sequentially to repair corrupted system files that may be mismanaging thread pools:
  
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealth

• Restart the PC once completed.

1. Perform a Clean Boot to Isolate Third-Party Conflicts

• Type msconfig in the Run dialog and press Enter.
• Under the Services tab, check Hide all Microsoft services, then click Disable all.
• Go to the Startup tab, open Task Manager, and disable all non-essential startup items.
• Restart the PC and monitor if the error persists.

Alternative or Verification Steps

• Verify the Fix: Reopen the application that previously threw Error 155 and monitor the Threads count for that specific process in Task Manager over 10–15 minutes; a stable or slowly increasing count confirms the leak is resolved.
• Alternative Fix: If the error persists, check for a corrupted user profile by creating a new local Windows user account (Settings > Accounts > Other users > Add account) and testing if the error occurs under the new profile.

Windows Error 156: “The Recipient Process Has Refused the Signal”

Why This Error Happens

Error 156 occurs when a process attempts to send a signal or message to another process via a named pipe or IPC (Inter-Process Communication) channel, but the receiving process is not in a state to accept it. This typically happens because the target service or application has crashed, is hung, or has closed its communication handle while the pipe connection is still considered “open” by the sender. Corrupted service configurations, mismatched process permissions, or a service that was forcibly terminated mid-operation are the most common root causes on Windows 11.

Step-by-Step Resolution Guide

1. Identify the affected process/service
   Open Event Viewer (eventvwr.msc) → navigate to Windows Logs > System and Application, then filter for Event ID 156 to identify which process triggered the error and which service was the intended recipient.

2. Restart the target service cleanly
   Open Services (services.msc), locate the affected service, right-click → Stop, wait 10 seconds, then right-click → Start. This clears any stale named pipe handles causing the refusal.

3. Check and repair service permissions
   Run sc.exe sdshow <ServiceName> in an elevated Command Prompt to view the service’s security descriptor. If permissions are misconfigured, reset them using:

   sc.exe sdset <ServiceName> D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;IU)(A;;CCLCSWLOCRRC;;;SU)

This restores standard SYSTEM/Administrator access to the service’s control pipe.

4. Run System File Checker and DISM
   Corrupted system files can prevent proper IPC handling. Run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart the PC afterward.

5. Update or reinstall the conflicting application
   If the error correlates with a specific third-party app (visible in Event Viewer details), update it to the latest version or perform a clean reinstall to regenerate its communication handles and registry entries.

Alternative or Verification Steps

• Verify the fix: Reproduce the original action that triggered Error 156, then check Event Viewer to confirm no new Event ID 156 entries appear within the same session.
• Alternative fix: If the error persists, create a new local user profile and test the same action — this isolates whether the issue is a corrupted user profile versus a system-wide service fault.

Windows 11 Error 157: “The segment is already discarded and cannot be locked”

Why This Error Happens

Error 157 occurs when an application attempts to access a memory-mapped segment that has already been released by the system, typically due to a race condition between processes or a premature termination of a shared memory handle. This is commonly triggered by corrupted DLL files, outdated device drivers, or applications improperly managing memory allocation during multitasking. In some cases, disk corruption on the volume hosting the application’s cache or virtual memory files can also cause this discrepancy.

Step-by-Step Resolution Guide

1. Run System File Checker to repair corrupted system files:
   Open Command Prompt as Administrator and run:

   sfc /scannow

Allow the scan to complete fully before restarting your PC.

2. Check and repair disk errors:
   Run the Deployment Image Servicing and Management tool followed by CHKDSK:

   DISM /Online /Cleanup-Image /RestoreHealth
   chkdsk C: /f /r

You will be prompted to schedule the CHKDSK scan on next restart—confirm and reboot.

3. Update or roll back the relevant device driver:
   Navigate to Settings > Windows Update > Advanced options > Optional updates > Driver updates. If the error started after a recent driver update, instead go to Device Manager, right-click the affected hardware, select Properties > Driver tab > Roll Back Driver.

4. Increase virtual memory (paging file) allocation:
   Go to Control Panel > System > Advanced system settings > Performance Settings > Advanced tab > Virtual Memory > Change. Uncheck “Automatically manage paging file size,” select your system drive, choose Custom size, and set an initial size of 1.5x your RAM and a maximum of 3x your RAM.

5. Reset or reinstall the affected application:
   If the error is tied to a specific program, go to Settings > Apps > Installed apps, locate the application, click the three-dot menu, and select Advanced options > Reset. If the issue persists, uninstall and reinstall the application using the latest installer from the vendor.

Alternative or Verification Steps

• Verify the fix: Reopen the application or trigger the action that previously caused Error 157, and monitor Event Viewer (eventvwr.msc) under Windows Logs > Application to confirm no new Error 157 entries appear.
• Alternative solution: If the error persists, create a new local user profile (Settings > Accounts > Other users > Add account) and test the application there—this isolates whether the issue is caused by a corrupted user profile rather than a system-wide fault.

Troubleshooting Guide: Error 158 – “The Segment Is Already Unlocked”

Why This Error Happens

Error 158 (ERRORNOTLOCKED) occurs when an application or process attempts to unlock a region of memory or a file segment that is not currently locked, typically due to a mismatched lock/unlock call sequence in the calling software. This often stems from a race condition where two threads or processes try to release the same resource simultaneously, or from a corrupted application state after an improper shutdown. It can also surface when file system filter drivers (such as antivirus software) interfere with standard file locking mechanisms (LockFile/UnlockFile API calls) on Windows 11.

Step-by-Step Resolution Guide

1. Identify the Offending Process: Open Event Viewer (eventvwr.msc), navigate to Windows Logs > Application, and filter for Event ID 158 to identify exactly which application or service triggered the error.
2. Update the Application and Drivers: Since this is usually a software logic bug rather than a core OS issue, check for pending updates for the specific application via Settings > Apps > Installed apps. Additionally, run Windows Update to ensure all storage and filter drivers are current.
3. Check for File System Corruption: Open Command Prompt as Administrator and run chkdsk C: /f /r to scan for and repair underlying disk segment or sector errors that might be causing the invalid lock state. Restart the PC to allow the scan to complete.
4. Isolate Third-Party Interference: Temporarily disable third-party antivirus or backup software (like Acronis or Macrium) that hooks into file I/O operations, as these frequently cause “phantom” lock/unlock mismatches. Test if the error persists with these tools disabled.
5. Repair System Files: Run the System File Checker by typing sfc /scannow in an elevated Command Prompt to fix corrupted system DLLs that might be mishandling the segment locking API calls.

Alternative or Verification Steps

• Verification: After applying the fixes, repeat the exact action that triggered the error (e.g., saving a file or running a specific script) and check the Event Viewer to confirm Error 158 no longer logs.
• Alternative: If the error persists in a specific third-party application, try running that application in Compatibility Mode for an older Windows version (right-click the .exe > Properties > Compatibility) to bypass Windows 11-specific locking behavior changes.

Troubleshooting Guide: Error 159 – “The Address for the Thread ID Is Not Correct” (Windows 11)

Why This Error Happens

Error 159 typically occurs when a thread’s memory address reference becomes invalid due to corrupted system files, a mismatched or outdated device driver, or improper thread synchronization caused by a failing application module. This is often triggered after an incomplete Windows update, driver installation, or memory corruption in the process handling the thread. In some cases, it can also stem from third-party software conflicting with core Windows threading APIs (such as CreateThread or GetThreadContext).

Step-by-Step Resolution Guide

1. Run System File Checker (SFC) and DISM
   Open Command Prompt as Administrator and run:

   sfc /scannow

Once complete, run:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be causing invalid thread address references.

2. Update or Roll Back Device Drivers
   Go to Settings > Windows Update > Advanced Options > Optional Updates > Driver Updates, and install any pending driver updates. If the error started after a recent driver update, open Device Manager, right-click the affected device, select Properties > Driver tab > Roll Back Driver.

3. Check Event Viewer for the Faulting Module
   Open Event Viewer (eventvwr.msc), navigate to Windows Logs > Application or System, and locate the Error 159 entry. Note the faulting module name (e.g., a .dll or .sys file) — this identifies which application or driver is triggering the thread error.

4. Update or Reinstall the Affected Application
   If the error points to a specific application (not a core OS process), uninstall it via Settings > Apps > Installed Apps, download the latest version from the vendor, and reinstall it.

5. Check for Memory Issues
   Run Windows Memory Diagnostic by typing mdsched.exe in the Start menu search, then select Restart now and check for problems. Faulty RAM can cause invalid thread addresses at the hardware level.

Alternative or Verification Steps

• After completing the steps above, reopen the application that triggered Error 159 and monitor Event Viewer for 24–48 hours to confirm the event no longer appears.
• If the error persists, boot into Safe Mode and attempt to reproduce the issue — if it does not occur in Safe Mode, a third-party service or startup program is likely the root cause, and a clean boot troubleshooting process should be performed.

Windows 11 Error 164: No More Threads Can Be Created in the System

Why This Error Happens

Error 164 occurs when the operating system exhausts the available thread pool, typically because system resources are constrained or a process/driver is leaking threads without releasing them. This is commonly caused by insufficient virtual memory, a runaway application spawning excessive threads, outdated or corrupted device drivers, or a system-wide resource limit (such as the kernel paged pool) being reached. In some cases, malware or a misbehaving background service can also rapidly consume thread handles until the system can no longer allocate new ones.

Step-by-Step Resolution Guide

1. Identify the offending process using Resource Monitor:

• Press Ctrl + Shift + Esc to open Task Manager, then click More details > Performance tab > Open Resource Monitor.
• In the Overview tab, sort processes by Threads count to identify any process consuming an abnormally high number of threads (often in the thousands).
• End the offending task via right-click > End Process Tree.

1. Increase virtual memory (paging file) size:

• Go to Settings > System > About > Advanced system settings.
• Under the Advanced tab, click Settings in the Performance section.
• Go to the Advanced tab > Change under Virtual Memory.
• Uncheck Automatically manage paging file size for all drives, select your system drive (usually C:), choose Custom size, and set an initial size of 1.5x your RAM and maximum size of 3x your RAM (in MB).
• Click Set, then OK, and restart your PC.

1. Update or roll back device drivers:

• Open Device Manager (Win + X > Device Manager).
• Check for drivers with warning icons, especially network adapters, storage controllers, and chipset drivers.
• Right-click each and select Update driver > Search automatically for drivers.
• If the issue started after a recent driver update, right-click the driver > Properties > Driver tab > Roll Back Driver.

1. Run System File Checker and DISM to repair corrupted system files:

• Open Command Prompt as Administrator (Win + X > Terminal (Admin)).
• Run: sfc /scannow and wait for it to complete.
• Follow with: DISM /Online /Cleanup-Image /RestoreHealth
• Restart your computer once both commands finish.

1. Check for malware or unauthorized background processes:

• Run a full scan using Windows Security (Settings > Privacy & security > Windows Security > Virus & threat protection > Scan options > Full scan).
• Remove any detected threats and restart the system.

Alternative or Verification Steps

• Verify the fix: Reopen Resource Monitor and monitor the Threads column over 10–15 minutes of normal use to confirm no process is climbing uncontrollably; also check the Event Viewer (eventvwr.msc) under Windows Logs > System to confirm Error 164 no longer appears.
• Alternative fix: If the error persists, perform a Clean Boot (via msconfig > Services tab > disable all non-Microsoft services, then restart) to isolate whether a third-party service or startup program is causing the thread leak.

Windows 11 Error 13 (“The Data Is Invalid”) Troubleshooting Guide

Why This Error Happens

Error 13 typically occurs when Windows encounters corrupted data while reading from disk, the registry, or a specific file, often due to bad sectors, incomplete writes, or file system corruption. This can also happen when a driver or application passes malformed data to a system call, or when antivirus software interferes with file I/O operations. In many cases, it stems from underlying disk integrity issues or corrupted system files that prevent Windows from correctly parsing expected data structures.

Step-by-Step Resolution Guide

1. Run System File Checker (SFC)
   Open Command Prompt as Administrator (right-click Start → Terminal (Admin)) and run:

   sfc /scannow

Let it complete fully and restart your PC afterward.

2. Check Disk for Errors
   In the same elevated Command Prompt, run:

   chkdsk C: /f /r

Type Y if prompted to schedule the scan on next restart, then reboot to let it run.

3. Run DISM to Repair the Windows Image
   If SFC reports errors it can’t fix, run:

   DISM /Online /Cleanup-Image /RestoreHealth

This pulls clean files from Windows Update to replace corrupted system components.

4. Update or Roll Back Drivers
   Open Device Manager (Win + X → Device Manager), locate the device associated with the error (often disk drives or storage controllers), right-click → Update driver. If the error started after a recent update, choose Roll Back Driver instead under the Driver tab.

5. Temporarily Disable Third-Party Antivirus
   Go to Settings → Privacy & Security → Windows Security → Virus & threat protection, and disable real-time protection temporarily to rule out interference, then retry the action that triggered Error 13.

Alternative or Verification Steps

• After completing the steps, reproduce the original action (file copy, app launch, or install) that triggered Error 13 to confirm it no longer appears.
• If the issue persists, check Event Viewer (Win + X → Event Viewer → Windows Logs → System) for the exact Event ID and source tied to Error 13, then create a System Restore Point rollback to a date before the error began occurring.

Why This Error Happens

Error 129 typically occurs when Windows 11 attempts to execute a legacy 16-bit application through the NTVDM (NT Virtual DOS Machine) subsystem, but the compatibility layer is disabled, missing, or corrupted. Since Windows 11 (like all 64-bit Windows versions) does not natively support 16-bit executables, this error also appears when the WOW (Windows on Windows) emulation layer fails to initialize properly. Corrupted system files or an improperly configured application compatibility database can also trigger this message even on modern 32-bit apps.

Step-by-Step Resolution Guide

1. Confirm Architecture Compatibility
   Right-click the application’s .exe file → Properties → Details tab. Check if it lists as a 16-bit application. If so, Windows 11 (64-bit only) cannot run it natively — skip to Alternative Steps below.

2. Run System File Checker and DISM
   Open Command Prompt as Administrator and run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may affect the Win32 subsystem or compatibility shims.

3. Enable/Repair the Application Compatibility Engine
   Go to Control Panel > Programs > Turn Windows features on or off and ensure Legacy Components (if listed) is checked. Also verify that %SystemRoot%\AppPatch\AcLayers.dll exists and is not corrupted — if missing, run sfc /scannow again after a reboot.

4. Check the Registry for IMAGEFILEEXECUTION_OPTIONS Conflicts
   Open regedit and navigate to:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options
   Look for an entry matching your application name and delete any conflicting Debugger or Layers keys that may be forcing incorrect execution mode.

5. Reinstall or Update the Application
   If the app is 32-bit but still throws Error 129, uninstall it completely (including leftover folders in Program Files (x86)), download the latest Windows 11–compatible installer from the vendor, and reinstall.

Alternative or Verification Steps

• After applying fixes, right-click the .exe → Properties > Compatibility tab → set it to run in Windows 8/7 compatibility mode and test launch again.
• If the application is confirmed 16-bit and cannot be updated, use a virtualization tool like DOSBox or a Windows XP mode via Hyper-V/VirtualBox to run it in an emulated legacy environment.

Why This Error Happens

Error 130 (ERROR_DIRECT_ACCESS_HANDLE) occurs when an application opens a physical disk or partition using a raw/direct-access handle (typically via \\.\PhysicalDriveX or \\.\C:) but then attempts a standard file I/O operation instead of sector-aligned raw read/write calls. This is common with disk imaging, cloning, or low-level backup utilities that fail to properly flag the handle for FILE_FLAG_NO_BUFFERING or don’t lock/dismount the volume before performing raw operations. It also occurs when the volume is still mounted and actively used by the OS (page file, indexing service, or antivirus) while a third-party tool tries to access it directly.

Step-by-Step Resolution Guide

1. Run the application as Administrator
   Raw disk access requires elevated privileges. Right-click the application (e.g., disk cloning/imaging tool) → Run as administrator. Without this, Windows may reject the handle request outright, triggering error 130 downstream.

2. Dismount and lock the volume before raw access
   If you’re using a custom script or tool (e.g., via PowerShell or a C++/C# utility calling DeviceIoControl), ensure it issues FSCTL_LOCK_VOLUME and FSCTL_DISMOUNT_VOLUME before performing raw I/O:

   mountvol X: /P   # dismounts the volume assigned to drive letter X

This prevents the OS from holding a buffered handle open on the same partition while your tool tries raw access.

3. Close background services that access the disk
   Open Task Manager → Services tab and temporarily stop:

• Windows Search (WSearch)
• Volume Shadow Copy (VSS)
• Any real-time antivirus disk scanning
  These services often hold buffered file handles to the partition, conflicting with raw disk requests.

3. Update or reinstall the disk utility software
   Older versions of imaging tools (Macrium Reflect, Acronis, Clonezilla for Windows, custom dd-style utilities) sometimes mishandle the CreateFile flags. Check for updates:

• Go to Settings > Apps > Installed apps, locate the tool, and check for a newer build via the vendor’s website.
• If custom-coded, verify CreateFile is called with FILE_FLAG_NO_BUFFERING | FILE_FLAG_WRITE_THROUGH and that all I/O buffers are sector-aligned (512 or 4096 bytes).

3. Verify disk health and partition integrity
   Corrupted partition tables can cause tools to mishandle raw vs. buffered access. Run:

   chkdsk C: /f /r

Reboot if prompted, and retry the operation afterward.

Alternative or Verification Steps

• Verify the fix: Reattempt the raw disk operation (imaging/cloning) immediately after dismounting the volume and running as Administrator. If the operation completes without Error 130, the handle conflict is resolved.
• Alternative: If the issue persists, boot into a Windows PE (WinPE) environment or use a bootable rescue disk from your imaging software vendor — this avoids OS-level locks entirely since the target partition won’t be mounted by a live Windows session.

Windows 11 Error 131: “An Attempt Was Made to Move the File Pointer Before the Beginning of the File”

Why This Error Happens

Error 131 is a low-level I/O error that occurs when a disk read/write operation attempts to seek to a negative offset within a file, which is typically caused by a corrupted file system structure or a failing storage sector. This most commonly appears in Event Viewer logs tied to disk drivers (such as Ntfs, disk, or atapi) and indicates that the file allocation table or Master File Table (MFT) entry for a file has become inconsistent. It can also be triggered by faulty storage drivers, a failing HDD/SSD, or an improperly terminated write operation caused by a sudden power loss or unsafe device removal.

Step-by-Step Resolution Guide

1. Run CHKDSK to repair file system errors
   Open Command Prompt as Administrator and run:

   chkdsk C: /f /r /x

Since the volume is in use, you’ll be prompted to schedule the scan on next restart — type Y and reboot your PC to let it complete.

2. Check disk health with SMART diagnostics
   Run the following to check the physical health of your drive:

   wmic diskdrive get status

If the status returns anything other than “OK,” the physical disk may be failing and should be backed up immediately and replaced.

3. Update or reinstall storage controller drivers
   Go to Device Manager > Disk drives, right-click your drive, select Update driver. Also expand IDE ATA/ATAPI controllers and update the SATA/NVMe controller driver. Restart afterward.

4. Run System File Checker (SFC) and DISM
   In an elevated Command Prompt, run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be triggering faulty I/O calls.

5. Inspect the specific application/log causing the error
   Open Event Viewer > Windows Logs > System, filter for Event ID 131, and note the source application or driver. If it’s tied to a specific third-party app (e.g., backup software, database service), reinstall or update that application, as it may be mishandling file stream offsets.

Alternative or Verification Steps

• After rebooting and letting CHKDSK complete, re-check Event Viewer for any new Error 131 entries over the next 24–48 hours of normal use to confirm the issue is resolved.
• If the error persists despite a clean CHKDSK and driver update, back up your data immediately and run the manufacturer’s dedicated diagnostic tool (e.g., Samsung Magician, WD Dashboard, CrystalDiskInfo) to rule out imminent drive failure.

Troubleshooting Guide: Error 132 — “The file pointer cannot be set on the specified device or file”

Why This Error Happens

Error 132 occurs when the Windows I/O subsystem fails to execute a SetFilePointer operation, usually because the target file or device is corrupted, locked by another process, or residing on a disk with bad sectors or a damaged file system table (MFT/NTFS metadata). It can also arise when a program attempts to seek beyond the file’s actual size or when disk drivers are outdated and mismanage read/write head positioning. In some cases, this is triggered by third-party antivirus software intercepting file handles and disrupting the pointer offset calculation.

Step-by-Step Resolution Guide

1. Run CHKDSK to repair file system errors:
   Open Command Prompt as Administrator (search “cmd,” right-click, “Run as administrator”) and execute:

   chkdsk C: /f /r /x

Confirm the scan on next restart if prompted, then reboot and let it complete.

2. Check and update storage drivers:
   Go to Settings > Windows Update > Advanced options > Optional updates > Driver updates. Install any pending storage controller or disk drivers. Alternatively, open Device Manager > Disk drives, right-click your drive, select Update driver > Search automatically.

3. Run System File Checker (SFC) and DISM:
   In an elevated Command Prompt, run:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may interfere with file handle operations.

4. Identify and close the process locking the file:
   Use Resource Monitor (type resmon in Start menu) → CPU tab → Associated Handles → search for the affected filename. If a process has it locked unexpectedly, end that process via Task Manager, then retry the file operation.

5. Temporarily disable third-party antivirus/backup software:
   Some antivirus or backup tools hook into file I/O calls and cause pointer conflicts. Disable real-time protection temporarily (via the antivirus system tray icon) and test if the error persists.

Alternative or Verification Steps

• Verify the fix: Reopen the file/application that triggered Error 132 and perform the same read/write/seek operation that failed earlier. Check Event Viewer (eventvwr.msc → Windows Logs → System) to confirm no new Error 132 entries appear.
• Alternative fix: If the error persists on an external or USB drive, test the device on another PC or format it (after backing up data) to rule out physical media failure.

Why This Error Happens

Error 133 occurs because the SUBST or JOIN command is being applied to a drive letter that is already part of an existing JOIN or SUBST mapping. Windows does not allow “nested” virtual drives — you cannot substitute or join a drive onto another drive that has already been virtually joined to a directory, as this would create a circular or ambiguous path reference. This is a logical restriction built into the disk management subsystem, not a hardware or permissions fault, and it commonly appears when leftover virtual drive mappings from a previous session were never removed.

Step-by-Step Resolution Guide

1. Open Command Prompt as Administrator
   Press Win + X, select Terminal (Admin) or Command Prompt (Admin).

2. List all current SUBST mappings
   Run:

   subst

This displays all active virtual drive letters and their target paths. Identify any drive letter that overlaps with the one you’re trying to JOIN/SUBST.

3. Remove the conflicting virtual drive
   Delete the existing substitution before creating a new one:

   subst X: /D

Replace X: with the actual conflicting drive letter shown in step 2.

4. Check for orphaned JOIN mappings (legacy systems only)
   Note: The JOIN command was deprecated after Windows 2000/XP and is not available in Windows 11. If your workflow or script still references JOIN, migrate to mklink /J (junction points) or SUBST, which are natively supported in Windows 11’s cmd.exe.

5. Re-run your original SUBST command
   Once the conflicting mapping is cleared, retry:

   subst Y: C:\YourFolder

The drive should now map without triggering Error 133.

Alternative or Verification Steps

• Run subst again with no arguments to confirm the new mapping appears correctly and no duplicate/nested entries exist.
• If SUBST still fails, use mklink /J C:\LinkFolder C:\TargetFolder to create a junction point instead — this achieves a similar folder-redirection effect without the legacy drive-joining conflicts.

Windows 11 Troubleshooting Guide: Error 134 – JOIN/SUBST Drive Conflict

Why This Error Happens

Error 134 occurs when the JOIN or SUBST command attempts to map a drive letter that is already associated with an active joined or substituted path. Windows maintains an internal table of virtual drive mappings, and this table does not allow a drive letter to be re-joined or re-substituted until the previous mapping is explicitly removed. This typically happens when a batch script, legacy application, or manual command line usage tries to reassign a drive without first checking or clearing its existing state.

Step-by-Step Resolution Guide

1. Open Command Prompt as Administrator
   Press Win + X, select Terminal (Admin) or Command Prompt (Admin).

2. Check the current status of joined/substituted drives
   Run the following command to list active SUBST mappings:

   subst

This displays all currently mapped virtual drives (e.g., Z:\ => C:\Data).

3. Remove the existing JOIN or SUBST mapping

• To remove a SUBST mapping:
  
subst Z: /d

• To remove a JOIN mapping (note: JOIN is deprecated since Windows Vista but may still appear in legacy scripts):
  
join Z: /d

  Replace Z: with the actual conflicting drive letter reported in the error.

3. Re-run the original JOIN or SUBST command
   Once the mapping is cleared, retry the original command:

   subst Z: C:\YourFolderPath

5. Update or correct the source script/application
   If the error originates from a batch file or third-party tool, edit the script to include a cleanup step (subst /d) before attempting to remap the drive letter, preventing future conflicts.

Alternative or Verification Steps

• Verify the fix: Run subst again to confirm only the intended mapping exists, and open File Explorer to check that the drive letter points to the correct folder.
• Alternative fix: If the drive letter remains “stuck” even after /d, restart the system to clear any residual virtual drive table entries, then reattempt the mapping.

Windows Error 135: JOIN/SUBST Drive Conflict Troubleshooting Guide

Why This Error Happens

Error 135 occurs when the Windows JOIN or SUBST command is executed against a drive letter that already has an active substitution or join mapping in place. This happens because Windows only allows one virtual drive mapping per drive letter at a time, and the system’s internal drive letter table still references the original substitution. Legacy applications, batch scripts, or leftover mappings from previous sessions (which weren’t properly cleared before a new command was issued) are the most common triggers of this conflict.

Step-by-Step Resolution Guide

1. Open Command Prompt as Administrator
   Press Win + X, select Windows Terminal (Admin) or Command Prompt (Admin).

2. Check Existing SUBST Mappings
   Run the following command to list all active virtual drive substitutions:

   subst

Identify the drive letter (e.g., Z:) that is already mapped and causing the conflict.

3. Remove the Existing Substitution
   Delete the conflicting mapping using the /d switch:

   subst Z: /d

This clears the virtual drive assignment, freeing up the letter for reuse.

4. Check for Active JOIN Commands (Legacy Systems)
   Note: JOIN was deprecated after Windows XP and is not natively supported in Windows 11. If a legacy script is calling JOIN, remove or update the script to use mklink (symbolic links) or subst instead, as these are the modern equivalents.

5. Re-run Your Original Command
   Once the drive letter is freed, retry your original SUBST command:

   subst Z: C:\YourFolderPath

Alternative or Verification Steps

• Verify the fix: Open File Explorer and confirm the drive letter now points to the correct new path, or run subst again to confirm only one mapping exists for that letter.
• Alternative solution: If SUBST continues to fail, use mklink /d Z:\ "C:\YourFolderPath" instead — symbolic links are the modern, more stable replacement and won’t trigger this legacy Error 135.

Troubleshooting Guide: Error 136 – “The System Tried to Delete the JOIN of a Drive That Is Not Joined”

Why This Error Happens

Error 136 (ERROR_NOT_JOINED) occurs when a process or script attempts to remove a drive path association using the legacy JOIN command on a drive letter or path that was never actually joined in the first place. This typically happens when a startup script, batch file, or third-party application tries to “clean up” a virtual drive mapping that doesn’t exist, or when a previous JOIN operation failed silently and left the system state out of sync with what the application expects. Since Windows 11 has deprecated the JOIN command entirely (it was removed after Windows XP), this error is now most commonly triggered by legacy software, old scripts, or compatibility layers still trying to call this obsolete function.

Step-by-Step Resolution Guide

1. Identify the source of the JOIN call
   Open Event Viewer (eventvwr.msc) → navigate to Windows Logs > Application and System, and filter by Event ID 136. Note the source application or process listed in the event details to determine what is issuing the outdated command.

2. Check for legacy scripts or batch files
   Search your system for .bat, .cmd, or .vbs files that reference the JOIN command:

• Open Command Prompt as Administrator and run:
  
findstr /si "JOIN" C:\Scripts\*.bat C:\Users\*\Startup\*.bat

• Remove or comment out any line calling JOIN /D (delete join) on a drive letter.

1. Remove SUBST/JOIN entries from Registry (if present)
   Some old software leaves residual entries. Open regedit and navigate to:

   HKEY_CURRENT_USER\Network
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\DOS Devices

Delete any manually created drive letter keys that reference JOIN or SUBST paths no longer in use. Back up the registry before making changes.

4. Update or replace the legacy application
   Since JOIN was removed from Windows entirely after XP, any application triggering this error is running in a compatibility mode or using an outdated installer script. Check for a newer version of the software, or run it in Windows XP Compatibility Mode via right-click → Properties → Compatibility tab, only as a temporary workaround.

5. Clear temporary drive mappings
   Open Disk Management (diskmgmt.msc) and confirm no phantom or duplicate drive letters exist. Remove any unused virtual drive letters via Change Drive Letter and Paths.

Alternative or Verification Steps

• Verify the fix: Reboot the system and monitor Event Viewer for 24–48 hours to confirm Event ID 136 no longer appears under Application/System logs.
• Alternative fix: If the error persists and stems from a specific legacy application, use SUBST (the modern replacement) correctly configured, or fully uninstall/reinstall the offending software to reset its drive-mapping configuration.

Troubleshooting Guide: Error 137 – “System Tried to Delete the Substitution of a Drive That Is Not Substituted”

Why This Error Happens

Error 137 occurs when the system attempts to remove a virtual drive mapping created by the SUBST command, but no such substitution actually exists for that drive letter. This typically happens due to a corrupted or outdated batch script, logon script, or startup entry that references a stale SUBST mapping which was already removed, never created, or cleared after a reboot (since SUBST mappings are not persistent by default). It can also occur if a third-party application or backup tool improperly tracks virtual drive letters in its configuration and tries to unmap a drive that Windows never registered as substituted.

Step-by-Step Resolution Guide

1. Check Current SUBST Mappings
   Open Command Prompt as Administrator and run:

   subst

This lists all currently active substituted drives. If the drive letter in question isn’t listed, it confirms no active substitution exists.

2. Locate the Source of the SUBST Command
   Search for scripts calling SUBST in common locations:

• C:\Windows\System32\GroupPolicy\Machine\Scripts\Startup
• Task Scheduler (taskschd.msc) — check for tasks running subst or .bat/.cmd files.
• Registry Run keys: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

2. Remove or Correct the Faulty Script/Entry
   If you find a script attempting subst X: /D (delete) without first verifying the drive exists, either:

• Delete the outdated task/script, or
• Edit it to include a conditional check, e.g.:
  batch
subst | find "X:" >nul && subst X: /D


2. Recreate and Properly Remove the Substitution (if needed)
   If you intended to use a substituted drive, create it correctly first:

   subst X: C:\YourFolder

Then remove it safely:

   subst X: /D

5. Clear Related Registry Remnants
   Check HKEY_CURRENT_USER\Network and HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2 for orphaned drive letter entries and remove any invalid ones (back up the registry first).

Alternative or Verification Steps

• Verify the Fix: Restart your PC and check Event Viewer (eventvwr.msc → Windows Logs → System) to confirm Error 137 no longer appears after the next scheduled task or logon script runs.
• Alternative Fix: If the error persists and the source can’t be found, disable third-party backup/sync software temporarily (many virtual drive tools misuse SUBST) and monitor whether the error recurs.

Windows 11 Error 138: System Tried to Join a Drive to a Directory on a Joined Drive

Why This Error Happens

Error 138 occurs when the system attempts to use the SUBST or volume mount point (join) functionality to link a drive letter to a directory that already resides on another joined/mounted volume. Windows does not support nested joins — a directory that is itself part of a mounted drive cannot serve as the target for another join operation. This typically results from leftover or conflicting entries created by scripts, backup software, or manual SUBST/mountvol commands that were not properly cleaned up before a new join was attempted.

Step-by-Step Resolution Guide

1. Identify existing joined drives/mount points
   Open Command Prompt as Administrator and run:

   mountvol

This lists all volume mount points currently active on the system. Note any paths that overlap with the directory you’re trying to join.

2. Check for active SUBST mappings
   Run the following to see if a virtual drive letter is already mapped to the target directory:

   subst

If you see a conflicting entry (e.g., Z:\ => C:\MountedFolder\SubDir), remove it with:

   subst Z: /D

3. Remove the conflicting mount point
   If the target directory is already a mount point for another volume, unmount it first using Disk Management:

• Press Win + X → Disk Management
• Right-click the volume mounted to that folder → Change Drive Letter and Paths → Remove

3. Recreate the join using a clean, non-nested directory
   Choose an empty folder that is not already part of another mounted volume, then reattempt:

   mountvol C:\NewMountFolder \\?\Volume{GUID}\

Ensure the GUID corresponds to the correct volume from mountvol /L.

5. Restart the Volume Shadow Copy and Virtual Disk services
   Sometimes stale service states cause Windows to misreport join status. Restart via:

   net stop vds
   net start vds

Alternative or Verification Steps

• Verify the fix: Re-run mountvol and subst to confirm no duplicate or nested mappings exist, then retry the original join operation — it should complete without Error 138.
• Alternative: If the issue persists, delete and recreate the target directory entirely (ensuring it’s not nested under any existing mount), then reattempt the join operation from scratch.

Why This Error Happens

Error 14 (ERROR_OUTOFMEMORY) occurs when Windows cannot allocate the memory required for a process, even if physical RAM appears available. This is frequently caused by a fragmented or undersized paging file, memory leaks from background applications, corrupted system files, or outdated/faulty drivers that improperly reserve memory. In some cases, third-party antivirus or disk utilities interfere with memory allocation calls at the kernel level.

Step-by-Step Resolution Guide

1. Increase the Virtual Memory (Paging File) Size

• Press Win + R, type sysdm.cpl, and press Enter.
• Go to Advanced tab → click Settings under Performance → Advanced tab → Change under Virtual Memory.
• Uncheck Automatically manage paging file size for all drives.
• Select your system drive (usually C:), choose Custom size, and set Initial size to 1.5x your RAM (in MB) and Maximum size to 3x your RAM.
• Click Set, then OK, and restart your PC.

1. Run System File Checker and DISM

• Open Command Prompt as Administrator.
• Run: sfc /scannow
• Once complete, run: DISM /Online /Cleanup-Image /RestoreHealth
• Restart your computer after both commands finish.

1. Update or Roll Back Drivers

• Open Device Manager (Win + X → Device Manager).
• Check Display adapters, Storage controllers, and Network adapters for warning icons.
• Right-click each device → Update driver. If the issue started after a recent update, use Roll Back Driver instead (under Properties → Driver tab).

1. Check for Memory Leaks via Task Manager

• Open Task Manager (Ctrl + Shift + Esc) → Processes tab.
• Sort by Memory and identify any app consuming abnormally high resources.
• End the process temporarily and check if the error recurs; uninstall or update that application if it’s the culprit.

1. Run Windows Memory Diagnostic

• Press Win + R, type mdsched.exe, and press Enter.
• Choose Restart now and check for problems.
• Windows will scan your RAM on reboot and report any hardware-level errors.

Alternative or Verification Steps

• After applying the fixes, reopen the application that triggered Error 14 and monitor Task Manager’s memory usage to confirm it stabilizes without spikes.
• If the error persists, boot into Safe Mode and attempt the same task—if it works fine there, a third-party startup program or driver is likely the root cause, and a clean boot troubleshooting process should be performed.

Why This Error Happens

Error 139 occurs when the SUBST command is used to point a virtual drive letter to a path that is already located on another substituted (virtual) drive. Windows does not allow nested drive substitutions because the OS cannot reliably resolve a chain of virtual paths back to a physical disk location. This typically happens when a batch script, mapped network drive, or legacy application attempts to create a substituted drive using a path that references another SUBST-created drive letter instead of the original physical directory.

Step-by-Step Resolution Guide

1. Identify all active substituted drives
   Open Command Prompt (cmd.exe) as Administrator and run:

   subst

This lists all current virtual drive mappings (e.g., Z:\ => C:\Projects\Data).

2. Trace the path back to its physical source
   Check if the target directory you’re trying to substitute is itself part of another SUBST entry. For example, if Y: is substituted to Z:\Reports and Z: is already a substituted drive, this will trigger Error 139.

3. Remove the conflicting substitution
   Delete the existing virtual drive that is causing the conflict:

   subst Z: /D

This unmaps the drive letter without deleting any actual files.

4. Re-create the substitution using the true physical path
   Instead of chaining virtual drives, always point directly to the original disk location:

   subst Z: C:\Projects\Data

Avoid using Y:\Reports (a substituted path) as the source.

5. Update scripts or shortcuts referencing the old virtual path
   If a batch file, .bat startup script, or application shortcut created the faulty substitution, edit it to reference the actual folder path (e.g., C:\Projects\Data\Reports) rather than a previously substituted drive letter.

Alternative or Verification Steps

• Run subst again after applying the fix to confirm only single-layer (non-nested) drive mappings exist.
• If the issue persists, consider using Symbolic Links (mklink /D) instead of SUBST, as NTFS symbolic links support nested directory structures without triggering this legacy DOS-era limitation.

Windows 11 Troubleshooting Guide: Error 140 – “The System Tried to Join a Drive to a Directory on a Substituted Drive”

Why This Error Happens

Error 140 (ERRORJOINTO_SUBST) occurs when a legacy disk management command—JOIN—attempts to merge a physical drive into a directory path that already exists on a virtual drive created by SUBST. Windows does not allow you to stack a JOIN operation on top of a SUBST substitution because the underlying volume mapping becomes ambiguous to the file system driver. This typically happens in legacy scripts, batch files, or older installer routines that still reference drive-letter substitution logic inherited from DOS-era disk management, which is largely deprecated in Windows 11.

Step-by-Step Resolution Guide

1. Identify Active Substituted Drives
   Open Command Prompt as Administrator and run:

   subst

This lists all currently active virtual drive mappings (e.g., Z: => C:\Projects).

2. Remove the Conflicting SUBST Mapping
   If the drive letter referenced by the failing JOIN command matches a listed SUBST entry, remove it:

   subst Z: /D

Replace Z: with the actual drive letter causing the conflict.

3. Avoid Using JOIN Entirely
   The JOIN command is deprecated and unsupported in Windows 11. Locate the script, batch file, or legacy application invoking JOIN and replace it with modern alternatives such as:

• Mount Points (via Disk Management or mountvol)

• Symbolic Links using mklink /D

  Example replacement:

   mklink /D "C:\TargetFolder" "D:\SourceFolder"

4. Check Registry for Legacy Mount Persistence
   Open regedit and navigate to:

   HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices

Look for orphaned or conflicting drive letter entries related to the SUBST/JOIN paths. Export the key first as a backup, then delete only the specific conflicting entry if identified.

5. Restart and Re-run the Original Task
   Reboot the system to clear any cached drive mapping states, then re-attempt the operation that triggered Error 140.

Alternative or Verification Steps

• Verify the Fix: Run subst again to confirm no lingering virtual drives exist at the target path, then re-run the original script or installer to confirm Error 140 no longer appears.
• Alternative Fix: If the issue persists, use Disk Management (diskmgmt.msc) to manually reassign or remove drive letter mappings instead of relying on command-line JOIN/SUBST utilities entirely.

Windows 11 Troubleshooting Guide: Error 141 — SUBST to a Joined Drive Directory

Why This Error Happens

Error 141 occurs because the Windows Virtual DOS Machine (VDM) and volume management drivers do not allow the SUBST command to target a directory that resides on a volume created by the JOIN command. This conflict arises from the way Windows maintains its internal drive-letter and volume mapping table — a joined drive is already treated as a merged extension of another volume’s directory tree, so layering a substituted (virtual) drive letter on top of it creates an unsupported nested mapping. Essentially, the system detects two conflicting virtual filesystem redirections trying to occupy the same logical space and blocks the operation to prevent volume table corruption.

Step-by-Step Resolution Guide

1. Identify active JOIN mappings: Open Command Prompt as Administrator and run subst with no parameters to list current virtual drive mappings, then check for any drives connected via JOIN by reviewing your drive management scripts or startup batch files (JOIN is deprecated but may still be scripted in legacy environments).
2. Undo the JOIN operation first: Run JOIN drive: /D (e.g., JOIN D: /D) to disconnect the joined drive from its target directory before attempting any SUBST command on that path.
3. Recreate the mapping using SUBST only: Once the join is removed, use SUBST X: C:\TargetFolder to create your virtual drive mapping directly, avoiding any dependency on a joined path.
4. Avoid mixing JOIN and SUBST permanently: Update any batch files, login scripts, or Task Scheduler jobs in C:\Windows\System32\ or custom script folders that call both JOIN and SUBST on the same directory tree — replace JOIN references entirely, since it is unsupported in modern Windows 11 workflows and mainly retained for legacy compatibility.
5. Restart Explorer and re-test: Open Task Manager (Ctrl+Shift+Esc), restart Windows Explorer process to refresh the drive letter cache, then reissue your SUBST command in an elevated Command Prompt to confirm it completes without Error 141.

Alternative or Verification Steps

• Verify the fix: Run subst alone in Command Prompt — your new virtual drive letter should appear in the output list pointing to the correct path without any error being thrown.
• Alternative approach: If you still need both directories accessible under separate drive letters, skip JOIN entirely and instead use SUBST for each target directory independently, or use NTFS Mount Points (mountvol) for permanent volume-to-folder mapping instead of the legacy JOIN/SUBST commands.

Why This Error Happens

Error 142 occurs when the SUBST or JOIN command attempts to use a drive letter that is already active in a mapped network drive, an existing SUBST/JOIN session, or is otherwise locked by the Windows drive letter table. Windows 11 tracks virtual drive assignments in the registry and will reject any overlapping request to prevent data corruption. This is commonly triggered by leftover SUBST entries from a previous session that were not cleanly removed, or by third-party disk utilities holding a drive letter reservation.

Step-by-Step Resolution Guide

1. Check for existing SUBST mappings
   Open Command Prompt as Administrator and run:

   subst

This lists all currently mapped virtual drives. Note any letter conflicting with the one you’re trying to assign.

2. Remove the conflicting virtual drive
   If the drive letter is already in use, delete it before retrying:

   subst X: /D

Replace X: with the actual conflicting letter.

3. Disconnect any active network drive using the same letter
   Go to File Explorer > This PC, right-click the mapped network drive, and select Disconnect. Alternatively, run:

   net use X: /delete

4. Clear orphaned registry entries (if the error persists)
   Open regedit and navigate to:

   HKEY_CURRENT_USER\Network

Delete any subkey matching the problematic drive letter, then restart the PC to refresh Windows’ drive letter cache.

5. Retry the SUBST or JOIN command
   Once the letter is free, reissue your original command:

   subst X: C:\YourFolderPath

Alternative or Verification Steps

• Run subst again with no parameters — the drive letter should no longer appear unless you’ve successfully remapped it.
• If the issue persists after a reboot, try assigning a completely unused drive letter (e.g., Z:) to confirm whether the original letter has a stuck OS-level reservation.

Windows Error 143 Troubleshooting Guide

Why This Error Happens

Error 143 occurs when the system attempts to use the SUBST or JOIN command to map a drive letter to a directory that resides on the same physical or logical drive. Windows explicitly blocks this operation because creating a virtual drive pointing to itself would cause a circular reference, leading to unpredictable file system behavior. This is a logical/operational restriction built into the command syntax rather than a corruption or permissions issue.

Step-by-Step Resolution Guide

1. Identify the command that triggered the error. Open Command Prompt (search “cmd” in the Windows 11 Start menu) and review the exact SUBST or JOIN syntax you used. For example, running subst X: C:\Folder while your system drive is already C: will fail if X: and the target path resolve to the same volume.

2. Verify the source and target drives are different. Ensure the drive letter you are creating (e.g., X:) is not the same as, or does not point back to, the drive containing the directory you’re substituting. Use wmic logicaldisk get caption to list all active drive letters and confirm no overlap.

3. Choose a directory on a different drive/partition. If you only have one physical drive, create the substitution using a path on a different partition (e.g., D:\Folder instead of C:\Folder), or use a folder that isn’t nested within the same root drive you’re mapping to.

4. Remove any existing conflicting substitutions. Run subst alone (no parameters) to list all active virtual drives. If a stale mapping exists, remove it with subst X: /D before creating a new one.

5. Restart Command Prompt as Administrator and retry. Some legacy SUBST/JOIN operations require elevated privileges on Windows 11. Right-click Command Prompt and select “Run as administrator,” then re-enter the corrected command.

Alternative or Verification Steps

• Verify the fix: After running the corrected SUBST command, type subst again to confirm the new virtual drive appears in the list and points to the intended (different) drive/path.
• Alternative solution: If you don’t strictly need a drive letter, use an NTFS symbolic link instead via mklink /D C:\LinkFolder C:\TargetFolder — this avoids the same-drive restriction entirely since symbolic links don’t require separate drive letters.

Windows 11 Error 144: “The Directory Is Not a Subdirectory of the Root Directory” Troubleshooting Guide

Why This Error Happens

Error 144 typically occurs when an application or command references a file path that is malformed, uses an incorrect relative path, or points to a directory structure that has been altered (e.g., a mapped drive was disconnected, a junction/symbolic link was broken, or a folder was moved/deleted). Windows expects the target path to exist as a valid child of the specified root (such as a drive letter or mounted volume), and when the path resolution fails—often due to corrupted NTFS junction points, invalid drive mappings, or leftover references in the registry—the system throws this error. This is common after restoring backups, migrating drives, or using scripts/batch files with hardcoded absolute paths that no longer match the current folder hierarchy.

Step-by-Step Resolution Guide

1. Verify the Path Manually
   Open File Explorer and navigate to the exact path referenced by the application or script. Confirm the folder structure exists and matches what’s expected (e.g., C:\Users\YourName\Documents\ProjectFolder).

2. Check for Broken Junctions or Symbolic Links
   Open Command Prompt as Administrator and run:

   dir /AL /S C:\

This lists all symbolic links and junctions. Look for any pointing to non-existent directories, then remove broken ones using:

   rmdir "C:\Path\To\BrokenLink"

3. Repair the File System
   Run CHKDSK to fix underlying disk structure issues that may cause path corruption:

   chkdsk C: /f /r

Restart when prompted, as this requires a reboot to complete the scan.

4. Re-map Network or Virtual Drives
   If the error involves a mapped network drive, go to This PC > Map Network Drive and re-establish the connection using the correct UNC path (e.g., \\ServerName\ShareName), ensuring “Reconnect at sign-in” is checked.

5. Update or Reconfigure the Application’s Path Settings
   If a third-party application triggered the error, open its configuration file or settings menu and correct any hardcoded root directory paths to match your current folder structure.

Alternative or Verification Steps

• Verify the fix: Re-run the original action or command that triggered Error 144. If successful, the operation should complete without the path error appearing in Event Viewer (Windows Logs > Application).
• Alternative solution: If the issue persists, create a new folder in a simple root location (e.g., C:\Data) and reconfigure the application to use this fresh, unambiguous path instead of a deeply nested or previously corrupted directory.

Windows 11 Error 145: “The Directory Is Not Empty” — Troubleshooting Guide

Why This Error Happens

Error 145 typically occurs when Windows attempts to delete, rename, or move a folder using RMDIR (or an underlying API call) while it still contains files, subfolders, or hidden system items that aren’t immediately visible in File Explorer. This often happens due to file system corruption, orphaned index entries, or another process (like antivirus software or a background service) holding a lock on a file inside that directory, preventing Windows from confirming it’s truly empty. In some cases, NTFS metadata corruption on the drive causes the system to falsely report contents even when the folder appears empty.

Step-by-Step Resolution Guide

1. Check for Hidden/System Files
   Open File Explorer, go to View > Show > Hidden items. Navigate to the problematic folder and manually delete any hidden .tmp, .ini, or Thumbs.db files that may be lingering.

2. Close Background Processes Locking the Folder
   Open Task Manager (Ctrl+Shift+Esc), and end tasks related to antivirus scanners, sync clients (OneDrive, Dropbox), or File Explorer itself. Restart explorer.exe via Task Manager (File > Run new task > explorer.exe).

3. Run CHKDSK to Fix File System Errors
   Open Command Prompt as Administrator and run:

   chkdsk C: /f /r

Replace C: with the appropriate drive letter. Restart your PC if prompted, as CHKDSK will run on the next boot to repair NTFS inconsistencies.

4. Force Delete via Command Prompt
   Open Command Prompt as Administrator and run:

   rmdir /s /q "C:\Path\To\Folder"

This forces a recursive deletion, bypassing some File Explorer glitches that trigger Error 145.

5. Take Ownership and Reset Permissions
   Right-click the folder > Properties > Security > Advanced. Change the owner to your user account, enable “Replace owner on subcontainers and objects,” then apply full control permissions before retrying the deletion.

Alternative or Verification Steps

• Verify the Fix: After deletion, refresh File Explorer (F5) and confirm the folder no longer appears; also re-run chkdsk C: /f to ensure no residual disk errors remain.
• Alternative Tool: If the issue persists, boot into Safe Mode and attempt the deletion again, or use a third-party tool like IObit Unlocker to force-remove locked files/folders.

Troubleshooting Guide: Error 146 – “The Path Specified Is Being Used in a Substitute”

Why This Error Happens

Error 146 occurs when a drive letter or folder path has been mapped using the SUBST command, and another process (such as a batch script, installer, or system utility) attempts to perform an operation—like deleting, remapping, or substituting—on that same path. Windows blocks this action because the path is already flagged as a virtual drive reference, creating a conflict between the substituted path and the requested operation. This is common after improper shutdowns, leftover SUBST mappings from previous sessions, or scripts that fail to clean up virtual drives before rerunning.

Step-by-Step Resolution Guide

1. Open Command Prompt as Administrator
   Press Win + X and select Terminal (Admin) or Command Prompt (Admin).

2. List all current substituted drives
   Type the following command and press Enter:

   subst

This will display all active virtual drive mappings (e.g., Z:\ => C:\Users\YourName\Documents\Project).

3. Remove the conflicting substituted drive
   Identify the drive letter causing the conflict, then remove it:

   subst Z: /D

Replace Z: with the actual drive letter shown in the previous step.

4. Retry the original operation
   Re-run the installer, script, or task that triggered Error 146. It should now proceed without the path conflict.

5. Check for persistent SUBST entries in startup scripts
   Navigate to C:\Windows\System32 and check for .bat or .cmd files that may recreate the SUBST mapping on boot. Also inspect:

   Task Scheduler > Task Scheduler Library

for any tasks re-establishing the substituted drive automatically.

Alternative or Verification Steps

• Verify the fix: Run subst again in Command Prompt—if the drive letter no longer appears, the substitution has been successfully cleared.
• Alternative fix: If the issue persists after removing the substitution, restart Windows Explorer via Task Manager (explorer.exe process) or reboot the system to fully release the drive letter from memory before retrying the operation.

Windows Update Error 0x80070002 Troubleshooting Guide

Why This Error Happens

Error 0x80070002 typically occurs when Windows Update cannot locate specific files it expects to find, often due to corruption in the Software Distribution folder where update files are temporarily stored. This can result from interrupted downloads, incorrect system date/time settings, or corrupted Windows Update components (BITS, wuauserv). Incomplete or damaged update caches prevent the installer from verifying and applying the update correctly.

Step-by-Step Resolution Guide

1. Check Date and Time Settings
   Go to Settings > Time & Language > Date & Time and ensure “Set time automatically” is enabled. Incorrect system time can cause certificate validation failures during updates.

2. Stop Windows Update Services
   Open Command Prompt as Administrator and run:

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver

3. Rename the SoftwareDistribution and Catroot2 Folders
   In the same elevated Command Prompt, rename the folders to force Windows to rebuild them:

   ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
   ren C:\Windows\System32\catroot2 catroot2.old

4. Restart the Services
   Restart the services you stopped earlier:

   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver

5. Run the Windows Update Troubleshooter
   Navigate to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update, then run the troubleshooter to detect and fix remaining issues automatically.

Alternative or Verification Steps

• After completing the steps above, go to Settings > Update & Security > Windows Update and click Check for updates to confirm the update installs successfully without the 0x80070002 error.
• If the issue persists, run the System File Checker (sfc /scannow) and DISM (DISM /Online /Cleanup-Image /RestoreHealth) commands in an elevated Command Prompt to repair underlying system file corruption before retrying the update.

Windows Update Error 0x80070002 Troubleshooting Guide

Why This Error Happens

Error 0x80070002 typically occurs when Windows Update cannot locate expected files, usually due to corrupted update components in the SoftwareDistribution folder or interrupted download data. This can also result from incorrect system date/time settings, which cause the Windows Update client to reject valid update packages as expired or invalid. In some cases, third-party antivirus software or a stalled Background Intelligent Transfer Service (BITS) prevents proper file retrieval.

Step-by-Step Resolution Guide

1. Check System Date and Time
   Go to Settings > Time & Language > Date & Time and enable “Set time automatically.” Incorrect clock settings are a common trigger for this error.

2. Stop Windows Update Related Services
   Open Command Prompt as Administrator and run:

   net stop wuauserv
   net stop cryptSvc
   net stop bits
   net stop msiserver

3. Rename the SoftwareDistribution and Catroot2 Folders
   In File Explorer, navigate to C:\Windows\SoftwareDistribution and rename it to SoftwareDistribution.old. Then navigate to C:\Windows\System32\catroot2 and rename it to catroot2.old. This forces Windows to rebuild these folders with fresh files.

4. Restart the Services
   In the same Command Prompt window, run:

   net start wuauserv
   net start cryptSvc
   net start bits
   net start msiserver

5. Run the Windows Update Troubleshooter
   Go to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update, then click “Run the troubleshooter” to detect and repair remaining issues automatically.

Alternative or Verification Steps

• After completing the steps above, go to Settings > Update & Security > Windows Update and click Check for updates to confirm the error no longer appears and updates download successfully.
• If the issue persists, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth in an elevated Command Prompt to repair underlying system file corruption that may be causing the missing file error.

Windows 11 Troubleshooting Guide: Error 1 – “Incorrect Function”

Why This Error Happens

Error 1 (“Incorrect Function”) occurs when Windows or an application sends a command that the target device, driver, or file system doesn’t recognize or cannot execute in its current state. This is commonly triggered by outdated or corrupted device drivers, incompatible disk formatting (such as attempting advanced operations on a FAT32 drive), or corrupted system files that interfere with standard I/O operations. It can also arise when a script or batch process calls a function using syntax or parameters unsupported by the current Windows build.

Step-by-Step Resolution Guide

1. Run the System File Checker (SFC) and DISM tools
   Open Command Prompt as Administrator and run:

   sfc /scannow

Once complete, run:

   DISM /Online /Cleanup-Image /RestoreHealth

Restart your PC after both commands finish.

2. Update or Reinstall the Relevant Device Driver

• Press Win + X → select Device Manager.
• Locate the device throwing the error (often disk drives, USB controllers, or printers).
• Right-click → Update driver → Search automatically for drivers.
• If that fails, right-click → Uninstall device, then restart your PC to let Windows reinstall it.

2. Check Disk for File System Errors
   Open Command Prompt as Administrator and run:

   chkdsk C: /f /r

Confirm the scheduled scan on next restart if prompted, then reboot.

4. Verify File System Compatibility
   If the error occurs on an external drive, check its file system via This PC → right-click drive → Properties → General tab. If it’s formatted as FAT32 and you’re performing operations requiring NTFS features (like large file transfers or permissions), reformat it via Disk Management (Win + X → Disk Management) — back up data first.

5. Check for Pending Windows Updates
   Go to Settings → Windows Update → Check for updates and install any pending cumulative or driver updates, as Microsoft frequently patches I/O-related bugs.

Alternative or Verification Steps

• Verify the fix: Reproduce the original action that triggered Error 1 (e.g., the file copy, print job, or script) and confirm it completes without the error message.
• Alternative fix: If the error persists on a specific drive, run chkdsk /b (Windows 11 only) to fully re-evaluate bad sectors, or test the file/device on another PC to isolate whether the issue is hardware-specific.

Windows Update Error 0x80070002 Troubleshooting Guide

Why This Error Happens

Error 0x80070002 typically occurs when Windows Update cannot locate specific files it expects to find, often due to corrupted update components or a damaged Software Distribution folder. This can result from interrupted downloads, incorrect system date/time settings, or corrupted files within the update cache. In some cases, third-party antivirus software or incomplete previous update installations can also trigger this error.

Step-by-Step Resolution Guide

1. Check and correct system date/time: Go to Settings > Time & Language > Date & Time and ensure “Set time automatically” is enabled. Incorrect time settings can cause update verification failures.

2. Run the Windows Update Troubleshooter: Navigate to Settings > Update & Security > Troubleshoot > Additional troubleshooters > Windows Update, then click “Run the troubleshooter” and follow the prompts.

3. Reset the Software Distribution folder:

• Open Command Prompt as Administrator
• Stop the Windows Update service: net stop wuauserv
• Stop the Background Intelligent Transfer Service: net stop bits
• Rename the folder: ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
• Restart the services: net start wuauserv and net start bits

1. Run System File Checker and DISM: In an elevated Command Prompt, run sfc /scannow to repair corrupted system files, followed by DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows image.

2. Manually download and install the update: Visit the Microsoft Update Catalog (catalog.update.microsoft.com), search for the specific KB number of the failed update, and install it directly.

Alternative or Verification Steps

• After completing the steps, go to Settings > Update & Security > Windows Update and click “Check for updates” to confirm the update installs successfully without the error.
• If the issue persists, use the Media Creation Tool to perform an in-place upgrade/repair install, which refreshes system files without deleting personal data.

Troubleshooting Guide: MySQL Error 10061 on Windows 11

Why This Error Happens

Error 10061 indicates that the connection to the MySQL server was actively refused, which almost always means the MySQL service (MySQL80 or similar) is not currently running on the machine. This can happen if the service crashed, was never started after installation, or was stopped manually. Less commonly, this error occurs because a firewall is blocking port 3306, or the Workbench connection is configured to use the wrong port/host.

Step-by-Step Resolution Guide

1. Check if the MySQL Service is Running
   Press Win + R, type services.msc, and hit Enter. Scroll down to find MySQL80 (or MySQL depending on your install). If the status is blank (not “Running”), right-click it and select Start.

2. Verify the Service Starts Successfully
   If the service fails to start, open Event Viewer (Win + R → eventvwr.msc) and check Windows Logs > Application for MySQL-related errors. A common cause here is a corrupted ibdata1 file or an incorrect my.ini configuration.

3. Inspect the Configuration File
   Navigate to C:\ProgramData\MySQL\MySQL Server 8.0\my.ini (note: ProgramData is hidden by default—enable “Hidden items” in File Explorer’s View tab to see it). Confirm the port=3306 setting matches what MySQL Workbench is trying to connect to, and check the datadir path exists and isn’t corrupted.

4. Set the Service to Start Automatically
   Back in services.msc, right-click MySQL80, go to Properties, and set Startup type to Automatic. This prevents the issue from recurring after a system reboot.

5. Check Windows Firewall Rules
   Open Windows Defender Firewall with Advanced Security, go to Inbound Rules, and ensure there’s a rule allowing traffic on TCP port 3306. If missing, create a new inbound rule to allow this port explicitly.

Alternative or Verification Steps

• Verify the fix: Open Command Prompt and run netstat -ano | findstr 3306. If MySQL is listening correctly, you’ll see a LISTENING entry with a matching PID for mysqld.exe in Task Manager.
• Alternative: If the service still won’t start, try running mysqld --console directly from the MySQL bin directory (e.g., C:\Program Files\MySQL\MySQL Server 8.0\bin) to see live error output that pinpoints the exact failure reason.

Troubleshooting Guide: MySQL Error 10061 on Windows 11

Why This Error Happens

Error 10061 means the connection was actively refused, which almost always indicates that the MySQL service (MySQL80 or similar) is not running on your Windows 11 machine. This can happen if the service crashed, was never started, or is misconfigured in my.ini. Less commonly, a firewall rule or antivirus program is blocking port 3306, or another application is already using that port, preventing MySQL from binding to it.

Step-by-Step Resolution Guide

1. Check if the MySQL Service is Running

• Press Win + R, type services.msc, and press Enter.
• Locate MySQL80 (or your version-specific service name) in the list.
• If the status is not “Running,” right-click it and select Start.

1. Verify the Port Configuration

• Navigate to C:\ProgramData\MySQL\MySQL Server 8.0\my.ini (path may vary by version).
• Open it with a text editor (as Administrator) and confirm the line under [mysqld] reads port=3306 (or your intended port).
• Ensure no other service (like XAMPP, IIS, or Skype) is using port 3306. You can check with:
  
netstat -ano | findstr :3306

• If a conflicting process is found, either stop that process or change MySQL’s port in my.ini.

1. Restart the MySQL Service

• Open Command Prompt as Administrator.
• Run:
  
net stop MySQL80
net start MySQL80

• Check the error log at C:\ProgramData\MySQL\MySQL Server 8.0\Data\[YourComputerName].err for startup failures (e.g., corrupted InnoDB files).

1. Check Windows Defender Firewall

• Go to Windows Security > Firewall & network protection > Advanced settings.
• Under Inbound Rules, ensure there is a rule allowing traffic on TCP port 3306. If missing, create a new inbound rule to allow it.

1. Verify Connection Settings in MySQL Workbench

• Open Workbench, right-click your connection, and select Edit Connection.
• Confirm the Hostname is 127.0.0.1 (not localhost, which can sometimes trigger socket/named pipe issues on Windows) and the Port matches your my.ini setting (default 3306).

Alternative or Verification Steps

• Verify the Fix: Open Command Prompt and run mysql -u root -p. If you’re prompted for a password and can log in successfully, the server is running and accessible.
• Alternative Fix: If the service repeatedly fails to start, reinstall the MySQL Server component via the MySQL Installer (found in your Start Menu) and select “Reconfigure” to reset the data directory and configuration files without losing your existing databases.

Windows 11 Error 10: “The Environment Is Incorrect” — Troubleshooting Guide

Why This Error Happens

Error 10 with the message “The environment is incorrect” typically occurs when a device driver fails to load due to corrupted or mismatched environment variables, invalid registry entries, or incompatible driver configurations recognized by the Windows Driver Framework. This is frequently seen in Device Manager when a hardware component’s driver cannot properly initialize because the system’s PATH variable or driver-specific parameters are malformed. It can also result from a botched Windows update or third-party software that improperly modified system environment settings.

Step-by-Step Resolution Guide

1. Check Device Manager for the Affected Device

• Press Win + X and select Device Manager.
• Locate the device showing a yellow warning icon, right-click it, and select Properties. Confirm “Error 10” appears under the Device Status field.

1. Update or Reinstall the Driver

• In the device’s Properties window, go to the Driver tab and click Update Driver.
• Choose Search automatically for drivers. If no update is found, click Uninstall Device, restart your PC, and let Windows reinstall the driver automatically.

1. Verify System Environment Variables

• Press Win + R, type sysdm.cpl, and press Enter.
• Go to the Advanced tab > Environment Variables.
• Under System variables, check the Path variable for duplicate, broken, or invalid entries (e.g., pointing to non-existent folders). Remove any suspicious entries and click OK.

1. Run System File Checker and DISM

• Open Command Prompt as Administrator.
• Run sfc /scannow to repair corrupted system files.
• Follow with DISM /Online /Cleanup-Image /RestoreHealth to fix underlying Windows image issues, then restart your PC.

1. Roll Back Recent Windows Updates (if the issue started recently)

• Go to Settings > Windows Update > Update History > Uninstall Updates.
• Remove the most recent quality update and restart to see if the error resolves.

Alternative or Verification Steps

• Verify the fix: Reopen Device Manager and confirm the device no longer shows a warning icon; check Event Viewer (Windows Logs > System) to ensure Error 10 is no longer logged.
• Alternative fix: If the error persists, perform a System Restore to a point before the issue began, or use Windows Update Troubleshooter (Settings > System > Troubleshoot > Other troubleshooters) to detect deeper system inconsistencies.

Windows 11 Error 100: “Cannot Create Another System Semaphore”

Why This Error Happens

This error occurs when the Windows kernel exhausts its available pool of system semaphore handles, typically due to a resource leak caused by a misbehaving driver, service, or application that creates semaphores without properly releasing them. It can also result from a depleted non-paged memory pool, corrupted system files affecting the Object Manager, or an accumulation of orphaned handles from a process that crashed without cleanup. Over time, as available system resources dwindle, the OS is unable to allocate new synchronization objects, triggering Error 100.

Step-by-Step Resolution Guide

1. Identify the Resource-Hogging Process
   Open Task Manager (Ctrl+Shift+Esc) → Details tab → right-click column headers → Select Columns → enable Handles. Sort by this column to identify any process consuming an abnormally high number of handles (typically in the thousands).

2. Restart the Offending Service or Application
   If a specific service is identified, restart it via Services.msc (Win+R → services.msc) rather than rebooting the entire system. Right-click the service → Restart.

3. Check and Increase System Resource Limits
   Open Registry Editor (regedit) and navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
   Verify the PagedPoolSize and NonPagedPoolSize values are set to 0 (which allows Windows to auto-manage them dynamically). If they are set to a fixed low value, adjust or remove the override.

4. Run System File Checker and DISM
   Open Terminal (Admin) and run:

   sfc /scannow

Followed by:

   DISM /Online /Cleanup-Image /RestoreHealth

This repairs corrupted system files that may be mishandling kernel object creation.

5. Update Drivers via Device Manager
   Outdated or buggy drivers (especially storage, GPU, or network drivers) are common culprits. Open Device Manager, check for warning icons, and update drivers via Windows Update → Optional Updates or directly from the manufacturer’s website.

Alternative or Verification Steps

• Verify the Fix: Use Performance Monitor (perfmon) and add the counter Object: Semaphores under the Objects category to confirm handle counts remain stable over time instead of climbing indefinitely.
• Alternative Fix: If the issue persists, perform a clean boot (via msconfig → Selective Startup) to isolate whether a third-party startup application is causing the semaphore leak, then uninstall the offending software.

Windows 11 Error 101: “The Exclusive Semaphore Is Owned by Another Process” Troubleshooting Guide

Why This Error Happens

This error occurs when a critical system service or application attempts to acquire an exclusive lock (semaphore) on a resource—such as a print spooler, network port, or shared memory object—that is already locked by another process. This typically happens due to a process that crashed without properly releasing its lock, a conflicting background service holding the resource hostage, or corrupted service dependencies that fail to negotiate resource access correctly. In some cases, insufficient permissions on the resource can also prevent the operating system from resolving the lock conflict automatically.

Step-by-Step Resolution Guide

1. Identify the conflicting process using Resource Monitor

• Press Win + R, type resmon, and hit Enter.
• Navigate to the CPU tab and use the Associated Handles search box to search for the specific resource name mentioned in your error log (check Event Viewer for details).
• Note the Process ID (PID) holding the handle.

1. Terminate the conflicting process safely

• Open Task Manager (Ctrl + Shift + Esc).
• Go to the Details tab, locate the PID identified in Step 1.
• Right-click and select End Task. If it’s a system-critical process, restart the associated service instead via services.msc.

1. Restart the affected Windows service

• Press Win + R, type services.msc, and press Enter.
• Locate the service related to your error (commonly Print Spooler, Windows Audio, or a specific application service).
• Right-click → Restart. If greyed out, set Startup Type to Automatic first, then restart the service.

1. Clear stale lock files (if applicable)

• Navigate to the application’s working directory (e.g., C:\ProgramData\[AppName]\Locks or %TEMP%).
• Delete any .lock, .lck, or .pid files associated with the crashed process.
• Restart the application to regenerate clean lock files.

1. Check and repair permissions on the resource

• Right-click the folder/file associated with the semaphore (often found in C:\ProgramData\ or C:\Windows\Temp\).
• Go to Properties → Security → Advanced.
• Ensure SYSTEM and your user account have Full Control, then apply changes recursively.

Alternative or Verification Steps

• Verify the fix: Reopen the application/service that triggered Error 101 and confirm it launches without the semaphore error. Check Event Viewer (eventvwr.msc) under Windows Logs → Application to ensure no new Error 101 entries appear.
• Alternative fix: If the issue persists, perform a clean boot (msconfig → Services tab → disable all non-Microsoft services) to identify third-party software creating the conflict, then reinstall or update the offending application.

Why This Error Happens

Error 102 (ERRORSEMIS_SET) occurs when a process attempts to close a semaphore object that is still actively signaled or held open by another thread or process. This typically happens due to improperly terminated applications, stuck background services (commonly the Print Spooler or a driver-related service), or orphaned handles left behind after a crash. Corrupted service dependencies or conflicting third-party software hooking into system resources can also prevent Windows from releasing the semaphore cleanly.

Step-by-Step Resolution Guide

1. Identify the offending process/service
   Open Task Manager (Ctrl+Shift+Esc) → Details tab. Look for the application or service reporting the error (often spoolsv.exe, a driver service, or a legacy 32-bit app). Note the PID.

2. Restart the associated service

• Press Win + R, type services.msc, press Enter.
• Locate the relevant service (e.g., Print Spooler).
• Right-click → Stop, wait 10 seconds, then Start again.
• If it won’t stop, open Command Prompt (Admin) and run:
  
taskkill /PID <PID> /F
net stop spooler
net start spooler


1. Clear orphaned handles using Process Explorer

• Download Process Explorer from Microsoft Sysinternals.
• Run as Administrator → Find → Find Handle or DLL.
• Search for “Semaphore” and close any handles tied to the crashed process manually.

1. Check and repair system files
   Run the following in an elevated Command Prompt to fix underlying corruption:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart Windows 11 after completion.

5. Update or roll back the driver/software triggering the error
   Go to Settings → Windows Update → Advanced options → Optional updates → Driver updates, or manually update the specific driver (commonly printer or USB drivers) via Device Manager. If the issue started after a recent update, roll back the driver instead.

Alternative or Verification Steps

• After restarting the service, check the Event Viewer (eventvwr.msc) under Windows Logs → System to confirm Error 102 no longer appears.
• If the issue persists, perform a clean boot (via msconfig → Selective startup, disable all non-Microsoft services) to isolate a third-party application causing the semaphore conflict.

Why This Error Happens

Error 103 (ERROR_SEM_IS_SET) occurs when a process attempts to set a semaphore object that is already in a “set” state, meaning another process or thread is still holding a lock on that shared resource. This typically happens when a service, driver, or application does not release its synchronization handle properly due to a crash, an unexpected termination, or corrupted driver code. It’s frequently seen with print spoolers, legacy hardware drivers, or third-party software that manages shared resources through kernel-level synchronization objects.

Step-by-Step Resolution Guide

1. Restart the affected service

• Press Win + R, type services.msc, and press Enter.
• Locate the service tied to the error (commonly Print Spooler or a specific hardware/driver service).
• Right-click it and select Restart. This releases any stuck semaphore handles.

1. Check Event Viewer for the source process

• Open Event Viewer (Win + X → Event Viewer).
• Navigate to Windows Logs > System and Windows Logs > Application.
• Filter by Event ID 103 to identify which driver or application triggered the semaphore conflict.

1. Update or reinstall the responsible driver

• Open Device Manager (Win + X → Device Manager).
• Find the device linked to the failing process (identified in Step 2).
• Right-click → Uninstall device, then restart your PC to let Windows reinstall a clean driver.
• Alternatively, download the latest driver from the manufacturer’s website.

1. Clear stuck spooler/resource files (if print-related)

• Stop the Print Spooler service via services.msc.
• Navigate to C:\Windows\System32\spool\PRINTERS and delete all files inside.
• Restart the Print Spooler service.

1. Run System File Checker to repair corrupted system components

• Open Command Prompt as Administrator.
• Run: sfc /scannow
• Follow with DISM /Online /Cleanup-Image /RestoreHealth if corruption is found.

Alternative or Verification Steps

• Verify the fix: Reopen the application or reconnect the device that previously triggered Error 103, and confirm no error dialog appears. Check Event Viewer to ensure Event ID 103 is no longer being logged.
• Alternative solution: If the issue persists, perform a clean boot (msconfig → Selective startup, disable all non-Microsoft services) to isolate a conflicting background application that may be locking the semaphore.

Troubleshooting Guide: Error 104 – Cannot Request Exclusive Semaphores at Interrupt Time

Why This Error Happens

Error 104 occurs when a kernel-mode driver or process attempts to acquire an exclusive semaphore lock while the system is servicing a hardware or software interrupt, which violates Windows synchronization rules since semaphore waits are not permitted at elevated IRQL (Interrupt Request Level). This is typically caused by an outdated or poorly written driver (often storage, network, or virtualization drivers) that improperly handles thread synchronization primitives. Corrupted system files or conflicts between kernel-mode components can also trigger this behavior, especially after a recent driver update or Windows feature update.

Step-by-Step Resolution Guide

1. Identify the Faulting Driver

• Open Event Viewer (eventvwr.msc) → navigate to Windows Logs > System.
• Locate the Error 104 event, expand details, and note the driver/module name listed in the “Source” or “General” tab (e.g., stornvme.sys, nvlddmkm.sys).

1. Update or Roll Back the Driver

• Press Win + X → select Device Manager.
• Locate the device tied to the faulting driver, right-click → Properties → Driver tab.
• Click Update Driver to fetch the latest version, or Roll Back Driver if the issue started after a recent update.

1. Run System File Checker and DISM

• Open Command Prompt as Administrator and run:
  
sfc /scannow

• If corruption is found, follow up with:
  
DISM /Online /Cleanup-Image /RestoreHealth

• Restart your PC after completion.

1. Check for Windows Updates

• Go to Settings > Windows Update → click Check for updates.
• Install any pending optional driver updates under Advanced Options > Optional Updates, as Microsoft frequently patches known kernel synchronization bugs.

1. Disable Fast Startup and Hybrid Sleep (if virtualization/storage drivers are involved)

• Go to Control Panel > Power Options > Choose what the power buttons do.
• Click Change settings that are currently unavailable, then uncheck Turn on fast startup.
• Save changes and reboot to rule out interrupt conflicts during hybrid resume states.

Alternative or Verification Steps

• Verify the fix: Reopen Event Viewer after a few reboot cycles and confirm no new Error 104 entries appear under System logs.
• Alternative fix: If the error persists, use verifier.exe (Driver Verifier) to stress-test drivers and pinpoint the exact faulty driver, then uninstall or replace it via the manufacturer’s latest signed driver package.

Why This Error Happens

Error 105 occurs when a Windows process or service loses control of a named semaphore—a synchronization object used to manage access to shared resources between multiple threads or processes. This typically happens when the original owning process crashes, is forcibly terminated, or times out before properly releasing the semaphore handle, leaving it in an orphaned state. Corrupted service dependencies, outdated drivers, or conflicts between multiple instances of an application trying to access the same shared resource can also trigger this abandonment.

Step-by-Step Resolution Guide

1. Identify the source process: Open Event Viewer (eventvwr.msc) → navigate to Windows Logs > Application or System, filter by Event ID 105, and check the “Source” field to determine which application or service triggered the error.

2. Restart the affected service cleanly:

• Press Win + R, type services.msc, and press Enter.
• Locate the service tied to the error (e.g., Print Spooler, SQL Server Agent, or a third-party backup/sync tool).
• Right-click → Stop, wait 10 seconds, then right-click → Start.

1. Clear orphaned handles via reboot in Safe Mode:

• Go to Settings > System > Recovery > Advanced startup > Restart now.
• Select Troubleshoot > Advanced options > Startup Settings > Restart, then press 4 for Safe Mode.
• This forces Windows to release all held semaphores and handles cleanly on the next normal boot.

1. Update or reinstall the affected application’s drivers/dependencies:

• Open Device Manager (devmgmt.msc) and update drivers for any hardware tied to the failing service (common with storage or print drivers).
• If it’s a third-party app, uninstall it via Settings > Apps > Installed apps, then reinstall the latest version from the vendor.

1. Run System File Checker and DISM to repair corrupted system components that manage synchronization objects:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Run these in an elevated Command Prompt or PowerShell window, then restart your PC.

Alternative or Verification Steps

• Verify the fix: Reopen Event Viewer after reproducing the original task (e.g., printing, running the backup job) and confirm no new Event ID 105 entries appear.
• Alternative fix: If the error persists and is tied to a specific third-party application, check the vendor’s website for a patch—this error is frequently resolved in updated builds that handle semaphore release more gracefully during unexpected shutdowns.

Troubleshooting Guide: Error 106 – “Insert the diskette for drive %1”

Why This Error Happens

This error occurs when Windows 11 or a legacy application attempts to access a floppy disk drive (typically A: or B:) that either doesn’t physically exist or is disconnected/misconfigured in the system. It’s commonly triggered by outdated software, batch scripts, or system utilities that still reference floppy drive letters from legacy configurations, or by a mapped network drive/mounted image that incorrectly points to a virtual floppy controller. Since modern PCs rarely include physical floppy drives, this is almost always a leftover driver, registry entry, or software dependency issue rather than an actual hardware fault.

Step-by-Step Resolution Guide

1. Check Device Manager for Floppy Drive Entries

• Press Win + X → select Device Manager.
• Expand Floppy disk drives (if visible). If an entry exists but no physical drive is installed, right-click it and select Uninstall device, then check Delete the driver software for this device.

1. Disable the Floppy Controller in BIOS/UEFI

• Restart your PC and enter BIOS/UEFI setup (usually F2, F10, Del, or Esc during boot).
• Navigate to Advanced or Peripherals settings and set Floppy Controller to Disabled.
• Save changes and reboot.

1. Remove Floppy Drive Letter Mappings in Registry

• Press Win + R, type regedit, and press Enter.
• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\flpydisk.
• If this key exists and no floppy hardware is present, right-click and export a backup, then delete the key.
• Also check HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\Scsi for stale floppy entries.

1. Identify and Update the Triggering Application

• Open Event Viewer (Win + X → Event Viewer) and locate the Error 106 event under Windows Logs > System.
• Check the Source field to identify which application or service is generating the request.
• Update or reconfigure that application to remove references to drive A:/B:, or uninstall it if it’s obsolete.

1. Run System File Checker (SFC) and DISM

• Open Command Prompt as Administrator.
• Run sfc /scannow to repair corrupted system files that may be misreporting drive dependencies.
• Follow with DISM /Online /Cleanup-Image /RestoreHealth to repair the Windows image if SFC finds issues.

Alternative or Verification Steps

• Verify the fix: Open File Explorer and confirm no phantom A:/B: drive icons appear under “This PC.” Re-run the application that originally triggered the error and confirm the prompt no longer appears.
• Alternative solution: If the error persists and is tied to a specific legacy program, run that application in Compatibility Mode (right-click the .exe → Properties → Compatibility tab) or contact the software vendor for an updated version that doesn’t reference floppy drives.

Windows 11 Error 107: “Program Stopped Because an Alternate Diskette Was Not Inserted”

Why This Error Happens

Error 107 is a legacy DOS-based interrupt error that occurs when a program expects removable media (a floppy diskette) in a drive but cannot detect one, often because the system is running an older application or utility through DOSBox, NTVDM compatibility layers, or a legacy installer that still references drive A: or B:. On modern Windows 11 systems, this typically surfaces because the physical floppy drive no longer exists, the drive letter mapping is broken, or the program’s configuration file still points to removable media instead of a virtual/emulated drive. Corrupted or misconfigured .ini/.cfg files tied to legacy software are the most common root cause.

Step-by-Step Resolution Guide

1. Identify the Source Program: Check which application is triggering Error 107. Right-click the shortcut or executable, select Properties, and review the Compatibility tab to confirm if it’s running in DOS-emulation or legacy compatibility mode.

2. Remap the Virtual Drive: If the program requires drive A: or B:, mount a virtual floppy disk image (.img or .vfd) using a tool like WinImage or Virtual Floppy Drive (VFD), then assign it to the expected drive letter via Disk Management (diskmgmt.msc → right-click the mounted image → Change Drive Letter and Paths).

3. Edit the Program’s Configuration File: Locate the application’s .ini, .cfg, or .sys file (commonly in C:\Program Files (x86)\[AppName]\) and change any reference from A:\ or B:\ to a valid local path, such as C:\VirtualDrive\.

4. Run in Compatibility Mode: Right-click the executable → Properties → Compatibility tab → check Run this program in compatibility mode for, and select an older Windows version (e.g., Windows 95/98) that matches the software’s original environment.

5. Reinstall Using an Updated Installer: If the program is outdated, check the vendor’s website for a Windows 11–compatible version that doesn’t rely on physical or virtual diskette emulation.

Alternative or Verification Steps

• After remapping, open File Explorer and confirm the virtual drive letter (e.g., A:) appears and is accessible before relaunching the program.
• If the error persists, try running the application inside DOSBox with a properly configured mount command pointing to a folder instead of a physical/virtual diskette.

Troubleshooting Guide: Error 108 – Disk In Use or Locked by Another Process

Why This Error Happens

Error 108 typically occurs when Windows or a disk utility (such as Disk Management, CHKDSK, or a third-party imaging tool) attempts to access a volume that is currently locked by another active process, service, or open file handle. This commonly happens when a background application (like antivirus, backup software, or a file indexer) is scanning or writing to the disk simultaneously, or when the disk has open handles from a previous session that were not released properly. In some cases, this error can also stem from corrupted file system metadata that causes Windows to hold onto exclusive locks even after the original process has closed.

Step-by-Step Resolution Guide

1. Identify and close conflicting processes:
   Open Task Manager (Ctrl + Shift + Esc), go to the Details tab, and look for processes like SearchIndexer.exe, backup software, or antivirus scanners. End tasks that may be actively reading/writing to the affected disk.

2. Check for open handles using Resource Monitor:
   Press Win + R, type resmon, and press Enter. Go to the CPU tab → Associated Handles section. Type the drive letter (e.g., D:) in the search box to find which process is locking the disk, then close that application.

3. Disable Windows Search Indexing temporarily:
   Go to Control Panel > Indexing Options, click Modify, and uncheck the affected drive. Alternatively, run services.msc, locate Windows Search, right-click, and select Stop.

4. Run CHKDSK in Safe Mode:
   Restart into Safe Mode (Settings > System > Recovery > Advanced Startup > Restart Now), then open Command Prompt as Administrator and run:

   chkdsk D: /f /r

Replace D: with your affected drive letter. Running this in Safe Mode reduces the chance of other processes locking the disk.

5. Update or reinstall the disk controller driver:
   Open Device Manager (devmgmt.msc), expand Disk drives, right-click your disk, and select Update driver. If the issue persists, uninstall the driver and restart the PC to let Windows reinstall it automatically.

Alternative or Verification Steps

• After applying the fix, open Disk Management (diskmgmt.msc) and confirm the drive shows as Healthy with no pending operations or warnings.
• If the issue persists, boot into Safe Mode with Networking and attempt the disk operation again — this rules out third-party software conflicts as the root cause.

Troubleshooting Guide: MySQL Error 10061 on Windows 11

Why This Error Happens

Error 10061 (“Can’t connect to MySQL server on ‘localhost'”) means the client tried to reach the MySQL server but the connection was actively refused. This typically happens because the MySQL server service isn’t running, it’s listening on a different port than the client expects (default 3306), or Windows Firewall is blocking the connection. Less commonly, a corrupted configuration file (my.ini) or incorrect hostname/socket settings in Workbench can also trigger this.

Step-by-Step Resolution Guide

1. Verify the MySQL service is running:

• Press Win + R, type services.msc, and hit Enter.
• Locate MySQL80 (or your version-specific service name) in the list.
• If the status isn’t “Running,” right-click it and select Start.

1. Check the service manually via Command Prompt (Admin):

   net start MySQL80

If it fails to start, check the error log at:
C:\ProgramData\MySQL\MySQL Server 8.0\Data\<hostname>.err

3. Confirm the correct port in configuration:

• Open C:\ProgramData\MySQL\MySQL Server 8.0\my.ini
• Under [mysqld], confirm port=3306 (or note the custom port if changed).
• Ensure this matches the port configured in MySQL Workbench under Connection Settings.

3. Check Windows Firewall rules:

• Go to Windows Defender Firewall with Advanced Security.
• Under Inbound Rules, ensure a rule exists allowing TCP traffic on port 3306.
• If missing, create a new inbound rule allowing that port for both Domain and Private networks.

3. Verify Workbench connection settings:

• Open MySQL Workbench → your connection → Edit Connection.
• Confirm Hostname is 127.0.0.1 (instead of localhost, which can sometimes resolve incorrectly) and Port is 3306.

Alternative or Verification Steps

• Test connectivity directly via Command Prompt:

  mysql -u root -p -h 127.0.0.1 -P 3306

If this connects successfully, the issue is isolated to Workbench’s connection settings rather than the server itself.

• If the service repeatedly fails to start, try reinstalling MySQL Server using the MySQL Installer and reconfiguring the instance from scratch, selecting “Reconfigure” instead of a fresh install to preserve existing databases.

Windows 11 Troubleshooting Guide: Error 11 – “An attempt was made to load a program with an incorrect format”

Why This Error Happens

Error 11 typically occurs when the operating system tries to load a driver or executable file that is architecturally incompatible with the system (e.g., a 32-bit driver on a 64-bit system) or when the file itself has become corrupted. This is commonly seen in Device Manager for hardware drivers, where Windows Event Viewer logs it against a specific .sys or .dll file. Additionally, a mismatch between the file extension and the actual binary format, often caused by incomplete downloads or malware tampering, can trigger this specific error code.

Step-by-Step Resolution Guide

1. Identify the Exact File Path:
   Open Event Viewer (search “Event Viewer” in the Start Menu) and navigate to Windows Logs > System. Find the Error 11 event and check the “General” tab to identify the specific file path (e.g., C:\Windows\System32\drivers\filename.sys) causing the conflict.

2. Check File Architecture:
   Right-click the identified file and check its Properties. If it is a driver, verify via Device Manager (right-click the specific hardware > Properties > Driver tab) that the driver matches your system architecture (64-bit).

   • Go to Settings > System > About to confirm your system type is “64-bit operating system, x64-based processor.”

3. Update or Reinstall the Driver:
   If the file belongs to a specific hardware device:

   • Open Device Manager (Right-click Start button > Device Manager).
   • Locate the device throwing the error (often marked with a yellow triangle).
   • Right-click > Uninstall device. Check the box for “Attempt to remove the driver software for this device” if available.
   • Restart your PC to allow Windows to reinstall a compatible generic driver, or manually install the correct 64-bit driver from the manufacturer’s website.

4. Run System File Checker (SFC):
   If the file is a core system file rather than a third-party driver, it may be corrupted. Open Command Prompt as Administrator and run:

   sfc /scannow
   

   Allow the scan to complete; it will automatically repair corrupted system files by replacing them with cached, correct versions.

5. Perform a DISM Scan:
   If SFC does not resolve the issue, the Windows component store itself might be damaged. Run the following commands in an Administrative Command Prompt to repair the underlying Windows image:
   
DISM /Online /Cleanup-Image /RestoreHealth


Alternative or Verification Steps

• Verify the Fix: Reopen Event Viewer and check the System logs for new occurrences of Error 11 after restarting the PC. If the specific hardware device was the cause, check Device Manager to ensure the yellow warning triangle is gone.
• Alternative Solution: If the error persists after driver updates and SFC/DISM scans, the file might be irrecoverably corrupted or malicious. Use Windows Security (Windows Defender) to run a Full System Scan to rule out malware disguising itself as a system file, then consider a System Restore to a point before the error began.

Why This Error Happens

Error 12 corresponds to the Windows system error ERROR_INVALID_ACCESS, which means an application or process attempted to open a file, registry key, or device using an access mode combination that the operating system does not recognize or permit. This typically stems from corrupted file/folder permissions, an outdated or mismatched driver making an invalid API call, or a damaged system file that no longer matches the access control list (ACL) Windows expects. It can also surface when antivirus or third-party security software intercepts and blocks a legitimate access request, causing Windows to report it as invalid.

Step-by-Step Resolution Guide

1. Run System File Checker and DISM to repair corrupted system files that may be causing invalid access requests:

• Open Command Prompt as Administrator.
• Run: sfc /scannow
• Then run: DISM /Online /Cleanup-Image /RestoreHealth
• Restart your PC after completion.

1. Check and reset file/folder permissions on the affected file or application directory:

• Right-click the file or folder → Properties → Security tab.
• Click Advanced → Change owner to your current user account.
• Check Replace all child object permissions and click Apply.

1. Update or reinstall the relevant device driver (if the error is tied to hardware access, e.g., USB, printer, or storage device):

• Open Device Manager (devmgmt.msc).
• Locate the device, right-click → Update driver → Search automatically.
• If that fails, uninstall the device and restart Windows 11 to force a clean reinstall.

1. Temporarily disable third-party antivirus/security software to rule out interference:

• Go to Settings > Privacy & security > Windows Security (or your antivirus app).
• Disable real-time protection temporarily and retry the action that triggered Error 12.

1. Create a new local user profile if the error persists only under one account, which can indicate a corrupted user profile:

• Go to Settings > Accounts > Other users > Add account.
• Sign in with the new profile and test whether the error still occurs.

Alternative or Verification Steps

• After applying fixes, repeat the exact action that triggered Error 12 (e.g., opening the file, running the app, or accessing the device) to confirm the “access code is invalid” message no longer appears.
• If the issue persists, boot into Safe Mode and attempt the same action — if it works there, a startup program or driver conflict is likely the root cause and should be isolated via Clean Boot (msconfig → Selective startup).

Troubleshooting Guide: Error 109 – “The Pipe Has Been Ended”

Why This Error Happens

Error 109 occurs when a named pipe connection between two processes is unexpectedly terminated before all data has been transmitted, often during print spooling or inter-process communication. This is commonly caused by a corrupted print driver, an unstable network connection to a shared printer, or a crashed background service (such as the Print Spooler) that closed the pipe prematurely. Interrupted communication due to antivirus interference or outdated drivers can also trigger this event.

Step-by-Step Resolution Guide

1. Restart the Print Spooler Service (most common trigger):

• Press Win + R, type services.msc, and press Enter.
• Locate Print Spooler, right-click it, and select Restart.
• Set Startup type to Automatic if it isn’t already.

1. Clear the Print Spooler Queue:

• Navigate to C:\Windows\System32\spool\PRINTERS.
• Stop the Print Spooler service first (as above), then delete all files inside this folder.
• Restart the Print Spooler service afterward.

1. Update or Reinstall the Device Driver:

• Go to Settings > Bluetooth & devices > Printers & scanners (or Device Manager for other pipe-related hardware).
• Select the affected device, click Remove device, then reinstall the latest driver from the manufacturer’s website.

1. Check Network/USB Connection Stability:

• For network devices, ensure a stable Ethernet/Wi-Fi connection; avoid using outdated SMB protocol versions.
• For USB-connected devices, try a different USB port or cable to rule out a physical connection issue.

1. Run Windows Update and SFC Scan:

• Open Settings > Windows Update and install any pending updates.
• Open Command Prompt as Administrator and run sfc /scannow to repair corrupted system files that may affect pipe communication.

Alternative or Verification Steps

• Verify the fix: Reproduce the original action (printing, file transfer, etc.) and check the Event Viewer (eventvwr.msc) under Windows Logs > System to confirm Error 109 no longer appears.
• Alternative fix: If the issue persists, create a new local user profile to rule out profile corruption, or use Windows Troubleshooter (Settings > System > Troubleshoot > Other troubleshooters > Printer) for automated diagnostics.

Troubleshooting Guide: Error 110 – “The System Cannot Open the Device or File Specified” (Windows 11)

Why This Error Happens

Error 110 typically occurs when Windows attempts to access a device, port, or file that is either locked by another process, disconnected improperly, or lacks the necessary permissions for the requesting application. This is commonly seen with USB devices, printers, or COM/LPT ports where a driver conflict or stale device handle prevents the OS from establishing a connection. Corrupted or outdated drivers, along with resource conflicts (e.g., two applications trying to access the same port), are the most frequent root causes.

Step-by-Step Resolution Guide

1. Check Device Manager for Conflicts

• Press Win + X → select Device Manager.
• Look for any device with a yellow exclamation mark, especially under Ports (COM & LPT) or Universal Serial Bus controllers.
• Right-click the problematic device → Update driver → Search automatically for drivers.

1. Restart the Device and Clear the Port Handle

• Physically disconnect the device (USB/printer/etc.).
• Open Task Manager (Ctrl + Shift + Esc) and end any background processes that may be holding the file/device open (e.g., PrintIsolationHost.exe for printers).
• Reconnect the device after 10 seconds.

1. Reset Permissions on the File or Device Path

• Navigate to the file/folder location (e.g., C:\Windows\System32\spool\PRINTERS for print jobs).
• Right-click → Properties → Security tab → Advanced.
• Ensure your user account has Full Control, then click Apply.

1. Uninstall and Reinstall the Driver

• In Device Manager, right-click the affected device → Uninstall device.
• Check “Delete the driver software for this device” if prompted.
• Restart your PC to force Windows to reinstall a clean driver.

1. Run the Hardware and Devices Troubleshooter

• Open Settings → System → Troubleshoot → Other troubleshooters.
• Run Hardware and Devices (if not listed, run via CMD: msdt.exe -id DeviceDiagnostic).

Alternative or Verification Steps

• Verify the fix: Reconnect the device or reopen the file/application that previously threw Error 110 — it should now initialize without the “cannot open” message.
• Alternative fix: If the error persists, try accessing the device/file from a different user account or in Safe Mode to rule out third-party software interference.

Windows 11 Troubleshooting: Error 111 – File Name Too Long

Why This Error Happens

Error 111 occurs when a file path exceeds the traditional Windows MAX_PATH limitation of 260 characters, which includes the drive letter, folder names, subfolders, and the file name itself. This commonly happens with deeply nested folder structures, files synced from cloud services with long auto-generated names, or when copying/extracting archives that preserve long original path structures. Older Win32 APIs still enforce this limit by default, causing operations like copy, rename, or delete to fail even though NTFS itself supports paths up to 32,767 characters.

Step-by-Step Resolution Guide

1. Enable Long Path Support via Group Policy

• Press Win + R, type gpedit.msc, and press Enter.
• Navigate to Computer Configuration > Administrative Templates > System > Filesystem.
• Double-click Enable Win32 long paths, select Enabled, click Apply, then OK.
• Restart your computer for the policy to take effect.

1. Enable Long Path Support via Registry (for Home edition without gpedit)

• Press Win + R, type regedit, and press Enter.
• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem.
• Find or create a DWORD (32-bit) value named LongPathsEnabled.
• Set its value to 1, then restart your PC.

1. Shorten the File or Folder Path Manually

• Move the file closer to the root directory (e.g., C:\Temp\ instead of a deeply nested folder).
• Rename parent folders to shorter names to reduce overall path length.

1. Use Command Prompt with Extended-Length Path Prefix

• Open Command Prompt as Administrator.
• Use the \\?\ prefix before the path to bypass the MAX_PATH limit, for example:
  
ren "\\?\C:\Very\Long\Path\To\File\filename.txt" "short.txt"


1. Use a Third-Party Tool for Bulk Operations

• For copying, deleting, or renaming multiple long-path files, use tools like Robocopy (built into Windows) with the /MIR switch, or a dedicated long-path management utility.

Alternative or Verification Steps

• After applying the fix, try copying, renaming, or deleting the previously problematic file again to confirm Error 111 no longer appears.
• If the issue persists in specific apps (e.g., File Explorer), try performing the same action via PowerShell or Command Prompt, as some applications may not yet support the new long path policy even after enabling it system-wide.

Windows Error 112: “There Is Not Enough Space on the Disk” (Windows 11)

Why This Error Happens

Error 112 occurs when the operating system attempts to write data to a disk volume that lacks sufficient free space, but this often happens even when Disk Properties shows available space. This discrepancy is typically caused by disk fragmentation preventing large contiguous write operations, hidden system files (like hibernation files, System Restore points, or Windows Update caches) consuming reserved space, or a failing/corrupted storage drive with bad sectors that the system can no longer write to. In some cases, disk quotas set at the user level or NTFS file system corruption also trigger this error incorrectly.

Step-by-Step Resolution Guide

1. Run Disk Cleanup to Free Hidden Space

• Press Win + R, type cleanmgr, and press Enter.
• Select your system drive (usually C:), click OK.
• Click Clean up system files, check boxes for Windows Update Cleanup, Temporary Files, and Delivery Optimization Files, then click OK.

1. Check and Repair Disk Errors Using CHKDSK

• Open Command Prompt as Administrator (search “cmd”, right-click, Run as administrator).
• Type: chkdsk C: /f /r and press Enter.
• Confirm the scan on next restart if prompted, then restart your PC to allow it to complete.

1. Disable or Resize Hibernation File

• In the elevated Command Prompt, type: powercfg /hibernate off
• This removes the hiberfil.sys file, which can occupy several GBs depending on installed RAM.

1. Repair Corrupted System Files

• In the elevated Command Prompt, run: sfc /scannow
• Follow up with: DISM /Online /Cleanup-Image /RestoreHealth
• Restart your computer once both commands complete successfully.

1. Check for Disk Quotas (If on a Managed/Domain PC)

• Right-click the affected drive in File Explorer → Properties → Quota tab.
• Ensure “Enable quota management” is unchecked, or increase the limit if required by policy.

Alternative or Verification Steps

• Verify the fix: Re-attempt the original file operation that triggered Error 112. Also check available space via Right-click Drive → Properties to confirm free space has increased.
• Alternative solution: If the error persists on an otherwise healthy-looking drive, run Windows Defender’s offline scan to rule out malware consuming disk space silently, or use wmic diskdrive get status in Command Prompt to check for hardware failure indicators.

Why This Error Happens

Error 113 (“No more internal file identifiers available”) occurs when the operating system’s file handle table is exhausted, meaning too many files, pipes, or registry keys are being held open simultaneously by one or more processes. This is often triggered by a runaway application (such as a backup utility, indexing service, or a script with a handle leak) that opens files without properly closing them. It can also occur on systems with a very low PagedPoolSize or handle quota configured in the registry, which artificially caps the number of identifiers available to the OS.

Step-by-Step Resolution Guide

1. Identify the offending process:

• Open Task Manager (Ctrl+Shift+Esc) → Details tab → right-click the column header → Select columns → check Handles.
• Sort by the Handles column to find any process with an abnormally high count (tens of thousands).

1. Terminate or restart the leaking process:

• Right-click the high-handle process and select End Task.
• If it’s a critical service (e.g., svchost.exe hosting a specific service), instead restart the specific service via Services.msc rather than killing the host process.

1. Increase the system-wide handle/paged pool limit (for advanced/server-like workloads):

• Open Registry Editor (regedit).
• Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management.
• Ensure PagedPoolSize is set to 0xFFFFFFFF (let the system manage it dynamically) rather than a fixed low value.
• Reboot the machine for the change to take effect.

1. Check for malware or corrupted drivers holding handles:

• Run Windows Security → Virus & threat protection → Quick scan.
• Use Driver Verifier (verifier.exe) temporarily if you suspect a faulty third-party driver is leaking handles, then review results in Event Viewer under System logs.

1. Apply pending Windows Updates:

• Go to Settings → Windows Update and install all pending updates, as Microsoft has periodically patched handle-leak bugs in core system components (Explorer, print spooler, etc.).

Alternative or Verification Steps

• After applying the fix, reopen the application that originally threw Error 113 and monitor its handle count in Task Manager over 15–20 minutes to confirm it stabilizes instead of climbing indefinitely.
• If the error persists, boot into Safe Mode and reproduce the issue — if it does not occur, a third-party startup application or driver is the root cause, and you should selectively disable startup items via Task Manager → Startup apps until the culprit is isolated.

Troubleshooting Guide: Error 114 – “The Target Internal File Identifier Is Incorrect”

Why This Error Happens

Error 114 typically occurs when the NTFS file system encounters a mismatch between a file’s Master File Table (MFT) record and the internal reference ID the system expects, often due to disk corruption, an improperly terminated write operation, or bad sectors. This can also surface after a failed disk transfer, a sudden power loss, or when using third-party disk-cloning/backup tools that misread file metadata. In some cases, outdated storage drivers or a failing hard drive can trigger this error as well.

Step-by-Step Resolution Guide

1. Run CHKDSK to repair file system errors

• Open Windows Terminal (Admin) and run:
  
chkdsk C: /f /r

• If prompted that the drive is in use, type Y to schedule the scan on next restart, then reboot.

1. Check disk health status

• Open Command Prompt as Administrator and run:
  
wmic diskdrive get status

• If the status doesn’t return “OK,” the physical disk may be failing and should be backed up immediately.

1. Update storage controller drivers

• Go to Device Manager > Disk Drives, right-click your drive, select Update driver.
• Also update drivers under Storage controllers (e.g., AHCI/RAID controller) via Device Manager or the motherboard/OEM manufacturer’s website.

1. Verify system file integrity

• Run the following in an elevated Command Prompt:
  
sfc /scannow

• Follow with:
  
DISM /Online /Cleanup-Image /RestoreHealth


1. Re-copy or re-transfer the affected file

• If the error appeared during a file copy/move operation (e.g., from an external drive or network share), delete the partially transferred file and re-copy it from the original source.

Alternative or Verification Steps

• Verify the fix: After running CHKDSK and rebooting, try accessing or copying the previously affected file again. If no error appears, the file system issue has been resolved.
• Alternative: If the error persists on a specific file, use a third-party tool like TestDisk to attempt file recovery, or restore the file from a previous backup/System Restore point.

Troubleshooting Guide: Error 117 – “The IOCTL Call Made by the Application Program Is Not Correct”

Why This Error Happens

Error 117 occurs when an application sends an I/O Control (IOCTL) request to a device driver, but the driver cannot interpret or execute it correctly. This is typically caused by an outdated, corrupted, or mismatched device driver that does not support the specific IOCTL code being sent, often following a Windows Update, driver rollback, or hardware/firmware mismatch. It can also occur if the application was designed for an older OS version and uses deprecated driver communication methods not fully supported in Windows 11.

Step-by-Step Resolution Guide

1. Identify the Affected Device/Driver
   Open Event Viewer (Win + X → Event Viewer) → Windows Logs → System, and locate the Error 117 entry. Note the associated device or service name (often shown in the source field).

2. Update the Driver

• Press Win + X → Device Manager.
• Locate the affected device (expand categories like Disk Drives, Storage Controllers, or Ports).
• Right-click → Update driver → Search automatically for drivers.
• If unresolved, manually download the latest driver from the manufacturer’s website and install it.

1. Roll Back or Reinstall the Driver
   If the issue started after a recent update:

• Go to Device Manager → right-click the device → Properties → Driver tab → Roll Back Driver (if available).
• If not available, uninstall the driver (Uninstall Device) and restart the PC to force Windows to reinstall a fresh copy.

1. Check for Corrupted System Files
   Run the following commands in an elevated Command Prompt (Win + X → Terminal (Admin)):

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

Restart the system after completion.

5. Verify Application Compatibility
   Right-click the application’s .exe file → Properties → Compatibility tab → enable Run this program in compatibility mode for and select an earlier Windows version if the app is legacy software making direct IOCTL calls.

Alternative or Verification Steps

• Verify the fix: Reopen the application and perform the action that previously triggered Error 117. Check Event Viewer again to confirm no new Error 117 entries appear.
• Alternative solution: If the error persists, contact the application vendor for an updated version compatible with Windows 11, as the IOCTL code they’re using may be deprecated or unsupported by the current driver stack.

Windows 11 Error 118: Verify-On-Write Parameter Error

Why This Error Happens

Error 118 occurs when the FSUTIL or CHKDSK/write-verification switch is passed an invalid or unsupported parameter value, typically due to a malformed command syntax, an outdated system utility, or a registry setting controlling EnableWriteVerify (or similar disk verification flags) that has been corrupted or set to an unexpected value. This is common when scripts or third-party disk-management tools invoke low-level Windows I/O functions with incorrect flag arguments, or when the underlying storage driver does not support the verify-on-write mode being requested. It can also surface if system files related to disk I/O control (ntdll.dll, disk.sys) have been corrupted or partially updated.

Step-by-Step Resolution Guide

1. Verify the exact command syntax. If you triggered this via Command Prompt or PowerShell, re-check the command. For example, with fsutil, the correct verify-on-write syntax is:

   fsutil behavior set DisableWriteVerify 0

or

   fsutil behavior set DisableWriteVerify 1

Any value other than 0 or 1 will trigger a parameter error.

2. Run Command Prompt as Administrator. Right-click Start → Terminal (Admin), then re-run the command. Insufficient privileges can sometimes surface as parameter validation errors rather than access-denied errors.

3. Check and reset the relevant registry key. Navigate to:

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem

Look for DisableWriteVerify (or similar) and confirm its value is a valid DWORD (0 or 1). Delete and let Windows recreate it if the value type or data appears corrupted.

4. Run System File Checker and DISM to repair corrupted system files that manage I/O verification:

   sfc /scannow
   DISM /Online /Cleanup-Image /RestoreHealth

5. Update storage/disk drivers via Device Manager → Disk drives → right-click your drive → Update driver, since outdated drivers can reject verify-on-write flags issued by the OS.

Alternative or Verification Steps

• After applying the fix, re-run fsutil behavior query DisableWriteVerify to confirm it returns a valid state (0 or 1) without throwing Error 118.
• If the error persists, boot into Safe Mode and repeat the registry check/SFC scan, as background processes or third-party disk utilities in normal mode may be interfering with the write-verify setting.