SECURITY WARNING: Never run commands you don't understand. Always review code before execution. Use at your own risk.
FixMyError.net
Windows New Added 26 October 2026

Windows: The semaphore timeout period has expired (0x80070079)

Despite the wording, this has nothing to do with semaphores in your code: Windows gave up waiting for an I/O operation, and error 121 is what the storage or network stack reports when a device stops answering. Copying to a NAS or mapped drive, it usually points at the network path (flaky Wi-Fi, NIC power saving, an MTU problem over a VPN). With a USB drive it points at the cable, the hub or the disk. It comes and goes with load, which is why large copies fail and small ones succeed.

Quick fix

Read the commands before running them. Anything that restarts a service, deletes data or changes permissions should be tried on a non-production system first.

Quick fix
# Network share: is the link dropping packets under load?
Test-NetConnection nas01 -Port 445
ping -n 50 nas01 | Select-String "Lost|Average"

# Disk or NIC resets around the time of the failure
Get-WinEvent -FilterHashtable @{LogName='System'; Level=2,3; StartTime=(Get-Date).AddHours(-2)} | Select-Object TimeCreated, ProviderName, Message -First 20

# Stop the adapter being powered down mid-copy
Get-NetAdapterPowerManagement | Format-List Name, AllowComputerToTurnOffDevice
Disable-NetAdapterPowerManagement -Name "Ethernet"

# Over a VPN: lower the size until it stops reporting fragmentation
ping -f -l 1400 nas01

# Local or USB disk: check its health
Get-PhysicalDisk | Select-Object FriendlyName, HealthStatus, OperationalStatus
chkdsk E: /scan

# Big copies over a shaky link: use a copy that resumes and retries
robocopy C:\src \\nas01\share\dst /E /Z /R:5 /W:10

How to diagnose Windows errors

Windows errors surface as numeric codes that mean little on their own, but the operating system keeps detailed logs that almost always contain the real cause. Two categories dominate developer machines: missing Visual C++ redistributables (a DLL-not-found error for a runtime the application assumed was present) and architecture or dependency mismatches (the 0xc000007b family, usually a 32-bit/64-bit mix).

If the quick fix above does not resolve it, work through these steps. They apply to this whole class of error, not just to this one message, which is usually what saves the time.

  1. Read Event Viewer under Windows Logs → Application and System, filtered to the time of the failure. The numeric code in the dialog maps to a detailed entry there.
  2. For MSI failures, install with verbose logging: msiexec /i package.msi /l*v install.log, then search the log for "Return value 3". The lines just above name the failing action.
  3. For missing DLLs, install the matching Visual C++ Redistributable and confirm the architecture matches the application (x64 versus x86).
  4. Repair system corruption with sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth, in that order.
  5. For access-denied errors, check both NTFS permissions and whether the process needs elevation; UAC virtualisation can make writes appear to succeed while landing elsewhere.

Tools worth reaching for

  • Event Viewer
  • msiexec /l*v
  • sfc /scannow
  • DISM /RestoreHealth
  • Process Monitor (ProcMon)

Authoritative references

Primary documentation for this error, worth reading before applying any fix in production.

learn.microsoft.com learn.microsoft.com

Related Windows errors

See all 20 Windows errors →

Browse other categories

Something missing or wrong?

This entry is maintained by hand. If the fix is out of date, incomplete, or you have a better one, email a correction and it will be reviewed.