FixerCode — Error Code Reference Updates

Linux 2 — Shell Misuse — improper use of shell built-ins or syntax

Sat, 27 Jun 2026 00:00:00 GMT

Exit code 2 is reserved by the shell (like Bash) to indicate that a built-in command was used incorrectly or a syntax error was found in the script file itself.

Linux 127 — Command Not Found — the specified command or file could not be located

Sat, 27 Jun 2026 00:00:00 GMT

Exit code 127 is returned by the shell when it cannot find the executable file in any of the directories listed in the PATH variable or at the absolute path provided.

HTTP 206 — HTTP 206 Partial Content — the server is sending a requested range

Sat, 27 Jun 2026 00:00:00 GMT

HTTP 206 Partial Content is a successful response for a range request. Instead of returning the entire resource like a normal 200 response, the server sends only the byte range or segment that the client requested.

HTTP 406 — Not Acceptable — the server cannot produce a response matching the request headers

Sat, 27 Jun 2026 00:00:00 GMT

A 406 Not Acceptable response appears when the server understands the request but cannot generate a representation that satisfies the client's declared preferences. It is tied to content negotiation, where headers such as Accept or Accept-Language limit which response formats are considered valid. I

HTTP 501 — Not Implemented — the server does not support the HTTP method used in the request

Sat, 27 Jun 2026 00:00:00 GMT

501 indicates a permanent limitation of the server — the feature or method requested is not supported. It differs from 405 which means the method is recognized but not permitted for that specific resource.

Nginx 499 — Client Closed Request — Nginx logged that the client closed the connection first

Sat, 27 Jun 2026 00:00:00 GMT

Nginx 499 is a non-standard log status used when the client closes the connection before Nginx can finish sending the response. It usually appears in Nginx access logs rather than as a response a browser can display directly. The upstream application may still be processing when the disconnect happe

Linux 1 — General Error — a non-specific failure in a command or script

Sun, 19 Jul 2026 14:35:26 GMT

Exit code 1 is a catch-all for many common Linux command failures. It indicates that the process finished with an error, but the specific reason was not mapped to a more descriptive exit code.

Linux 13 — Permission Denied — the process does not have permission to access the resource

Sun, 19 Jul 2026 14:35:26 GMT

Error 13 (EACCES) occurs when the kernel prevents a process from performing a file system operation due to existing permission bits (owner, group, others) or ACLs.

Linux 126 — Command Not Executable — the file was found but is not executable

Sun, 19 Jul 2026 14:35:26 GMT

Exit code 126 occurs when the shell locates the file you specified, but the system refuses to run it as a process. This is distinct from error 127 where the file isn't found at all.

Linux 130 — Terminated by User — the process was interrupted by a SIGINT signal

Sun, 19 Jul 2026 14:35:26 GMT

Exit code 130 is calculated as 128 + 2 (the signal number for SIGINT). it confirms that the process stopped because it received a manual interrupt signal.

Linux 137 — Process Killed — the process was terminated by a SIGKILL signal

Sun, 19 Jul 2026 14:35:26 GMT

Exit code 137 is 128 + 9 (the signal number for SIGKILL). Unlike SIGTERM, SIGKILL cannot be caught or ignored by the process, resulting in an immediate exit.

Linux 3 — Unspecified Error — a general-purpose failure code with no standardized meaning

Sun, 19 Jul 2026 14:35:26 GMT

Exit code 3 is not reserved by the POSIX standard or Bash. Individual programs assign their own meaning to it, making interpretation fully dependent on the specific application that generated the exit.

Linux 11 — SIGSEGV signal 11 — the process attempted invalid memory access

Sun, 19 Jul 2026 14:35:26 GMT

Signal 11 is the numeric Linux signal for SIGSEGV, the segmentation fault event. It describes the signal delivered to the process, while exit code 139 is the shell-facing status produced from the same event by adding 128 to the signal number.

Linux 139 — Exit code 139 — shell status for a SIGSEGV termination

Sun, 19 Jul 2026 14:35:26 GMT

Exit code 139 is the shell-level representation of a SIGSEGV termination. It comes from the Linux convention of reporting signal exits as 128 plus the signal number: 128 + signal 11 = 139.

Linux 5 — Input/output error EIO — a read or write operation could not complete

Sun, 19 Jul 2026 14:35:26 GMT

Errno 5, commonly named EIO, means an input/output operation failed below the application layer. It can surface while reading, writing, opening, or executing through a path whose backing storage or filesystem layer could not complete the requested operation.

Linux 12 — Out of Memory (ENOMEM) — the kernel cannot allocate the requested amount of memory

Sun, 19 Jul 2026 14:35:26 GMT

ENOMEM (errno 12) is returned by malloc, mmap, and other memory allocation calls when the kernel cannot satisfy the request. The Linux OOM Killer may terminate processes to recover memory before this error is returned.

Linux 128 — Invalid Exit Argument — script exited with an out-of-range status or terminated by a signal

Sun, 19 Jul 2026 14:35:26 GMT

In Linux shell conventions, exit code 128 by itself means an invalid argument was passed to the exit built-in. More commonly, exit codes 128+N (e.g., 130 = 128+2 for SIGINT, 137 = 128+9 for SIGKILL) indicate the process was terminated by signal N.

Windows 0x80070005 — Access Denied

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80070005 code is commonly known as an Access Denied error. It indicates the operating system lacks the necessary permissions to execute a required file or registry modification.

Windows 0x80070002 — File Not Found

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80070002 error generally signifies that a deeply integral file required down the processing pipeline is suddenly missing from the system disk.

Windows 0x80240034 — Update Failed

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80240034 error arises specifically when Windows Update heavily struggles to securely fetch or rapidly integrate a cumulative patch from the Microsoft servers.

Windows 0x800F081F — Source Files Not Found

Sun, 19 Jul 2026 14:35:26 GMT

The 0x800F081F error frequently occurs during aggressive installations of heavy fundamental components, heavily like the .NET Framework 3.5.

Windows 0x80004005 — Unspecified Error

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80004005 is a catch-all COM error that heavily acts as an 'Unspecified Error'. It triggers when Windows cannot successfully map a specific failure to a more detailed, aggressive error code.

Windows 0x80070643 — Fatal error during installation

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80070643 code is a generic fatal error encountered during software installation or updating. It is most notorious for appearing during Windows Update cycles when the system fails to apply a critical security patch or .NET Framework improvement.

Windows 0x80070020 — The process cannot access the file because it is being used by another process

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80070020 error indicates a 'sharing violation' at the file system level. It happens when two different processes attempt to access or modify the same file simultaneously using incompatible access modes.

Windows 0x80244017 — WU_E_PT_HTTP_STATUS_DENIED

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80244017 error occurs when the Windows Update agent attempts to connect to a server (either Microsoft's or an internal WSUS) but is actively denied access by an intermediary network device.

Windows 0x80070422 — The service cannot be started, either because it is disabled or has no enabled devices

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80070422 error is a direct signal from the Service Control Manager. It means a process tried to start a service that is currently flagged as disabled, preventing it from ever entering a running state.

Windows 0x80040154 — Class not registered

Sun, 19 Jul 2026 14:35:26 GMT

The 0x80040154 code is a classic COM (Component Object Model) error. It means an application tried to create an instance of a software component that is not correctly listed in the system registry.

Windows 0x80073712 — Component Store Corrupted — a required Windows Update component is damaged

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80073712 indicates that Windows Update cannot proceed because internal servicing files are inconsistent or missing. The component store maintains all update manifests and payloads, and any corruption blocks future installations.

Windows 0x800F0922 — Update Installation Failed — update service connection or reserved partition issue

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x800F0922 has two common root causes: a network connectivity failure to the Windows Update servers, or insufficient space on the System Reserved Partition. These are functionally different problems that share the same error code.

Windows 0x80070057 — Invalid Parameter — the system received an argument it cannot process

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80070057 (E_INVALIDARG) is one of the most generic Windows error codes. It appears across many subsystems including Windows Update, disk management, backup, and application installations whenever an internal function receives data it cannot accept.

Windows 0x8007045d — I/O Device Error — Windows cannot perform an input/output operation on the specified device

Sun, 19 Jul 2026 14:35:26 GMT

0x8007045D is the Windows HRESULT encoding of the Win32 error ERROR_IO_DEVICE (1117). It surfaces in disk operations, file copies, and system imaging tools when the storage device fails to complete an I/O request.

Windows 0x80070424 — Required Service Missing — Windows cannot find a service needed for the operation

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80070424 appears when Windows tries to use a service that is missing from the current system configuration. In update-related cases, the request reaches the service layer, but the expected service entry is absent or broken. That makes this code closer to service registration than to network

Windows 0xc000021a — Fatal System Error — a critical Windows subsystem process terminated, causing the system to halt

Sun, 19 Jul 2026 14:35:26 GMT

0xC000021A is a stop code that results in a Blue Screen of Death. It indicates that a critical user-mode subsystem — typically Winlogon or CSRSS — has crashed and Windows cannot continue running.

Windows 0x80072EE2 — Operation Timed Out — Windows Update waited too long for a response

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80072EE2 appears when Windows Update waits for a network response longer than its transport window allows. The request was sent, but the reply never arrived in time. That makes this code more about delay or reachability than about damaged servicing files on disk.

Windows 0x80070070 — Not Enough Disk Space — the target volume has insufficient free space for the operation

Sun, 19 Jul 2026 14:35:26 GMT

0x80070070 maps to the Win32 error ERROR_DISK_FULL. It commonly occurs during Windows Updates, application installations, or file copy operations when the target volume runs out of free space.

Windows 0x8007000D — Invalid Data — Windows received update data it could not parse

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x8007000D appears when Windows reads data that does not match the structure or integrity it expects. In update scenarios, that often means package metadata, cache contents, or manifest information is present but unusable. The failure sits closer to data quality than to access denial or servic

Windows 0x80244022 — Service Unavailable — the update endpoint returned a temporary server-side failure

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80244022 means the Windows Update client reached an update service path, but the service side returned a temporary availability failure. The request did not fail because of local parsing or permissions. It failed because the service layer on the other side did not successfully complete the e

Windows 0x8024402C — Name Resolution Failure — Windows Update could not resolve the required server name

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x8024402C appears when Windows Update cannot resolve the host name it needs to contact. The failure occurs before a normal service exchange can begin. In practice, this often points to proxy configuration, DNS resolution, or WinHTTP settings that differ from the user's browser path.

Windows 0x800705B4 — Operation Timeout — a required Windows task did not finish in time

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x800705B4 is a broad Windows timeout signal. It appears when a protected task does not complete within the wait period expected by the calling subsystem. In update-related cases, that can mean the operation started correctly but stalled before reaching a usable result.

Windows 0x80073701 — Assembly Missing — servicing stack could not find a required component package

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80073701 points to a missing assembly or package reference inside the Windows servicing stack. The update process is not failing because of a network timeout or disabled service. It is failing because a required servicing component cannot be found where Windows expects it to exist.

Windows 0x8024200D — Update Content Incomplete — the downloaded update package could not be used

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x8024200D appears when Windows Update has package content on disk, but that content is incomplete or inconsistent enough that the update handler cannot continue. The failure is not purely about service reachability. It is about a package state that is present but not trustworthy enough to use

Windows 0x80070490 — Element Not Found — Windows could not locate a required servicing component

Sun, 19 Jul 2026 14:35:26 GMT

Error 0x80070490 means Windows looked for a specific servicing element and did not find it where expected. In update and repair scenarios, that often points to missing package metadata, broken component references, or a store state that no longer maps correctly to the requested operation.

Windows 0xC1900101 — Driver Compatibility Failure — Windows upgrade rolled back after a driver-related crash

Sun, 19 Jul 2026 14:35:26 GMT

Error 0xC1900101 is a Windows upgrade rollback family code commonly associated with driver incompatibility during a feature upgrade. It is not the same kind of signal as a normal monthly update download failure. The setup process advanced far enough to hit a compatibility or crash problem and then r

Git merge-conflict — Git paused the merge because it cannot automatically resolve overlapping changes.

Sun, 19 Jul 2026 14:35:26 GMT

When combining branches, Git usually merges changes automatically. However, if changes directly contradict each other, Git stops, leaves the affected files in an 'unmerged' state, inserts conflict markers (<<<<<<<, =======, >>>>>>>) directly into the code, and waits for a human to resolve the differ

Git unmerged-paths — You have unresolved file conflicts preventing Git from completing the current operation.

Sun, 19 Jul 2026 14:35:26 GMT

Git maintains an internal 'index' (staging area). When a conflict occurs, Git marks the affected files as 'unmerged' in this index. Operations like `git commit` or `git checkout` are blocked until these files are explicitly marked as resolved using `git add`.

Git local-changes-overwritten-by-merge — Git aborted the merge to protect uncommitted changes in your working directory.

Sun, 19 Jul 2026 14:35:26 GMT

Unlike a standard merge conflict (which happens between two committed histories), this error occurs when your current working directory contains unsaved work. Git refuses to overwrite your unsaved edits because doing so would result in permanent data loss.

Git local-changes-overwritten-by-checkout — Git prevented a branch switch because it would overwrite unsaved changes in your working directory.

Sun, 19 Jul 2026 14:35:26 GMT

When you switch branches, Git updates your working directory to match the target branch. If you have uncommitted changes in a file, and the target branch has a different committed version of that same file, a checkout would overwrite your unsaved work. Git blocks the operation to prevent data loss.

Git untracked-files-overwritten-by-merge — Git aborted the merge because it would overwrite untracked files in your working directory.

Sun, 19 Jul 2026 14:35:26 GMT

Untracked files are files that exist on your disk but have not been added to Git. If a merge brings in a tracked file with the same name, Git stops the operation to prevent destroying your local untracked file.

Git failed-to-push-some-refs — Git rejected your push because the remote repository contains commits missing from your local branch

Sun, 19 Jul 2026 14:35:26 GMT

This is a wrapper error that Git throws whenever an upload (push) is blocked. The most common reason is that the remote history has moved forward, and pushing your local history directly would orphan the new remote commits.

Git non-fast-forward — Git rejected your push because your branch is behind the remote, preventing a linear update.

Sun, 19 Jul 2026 14:35:26 GMT

A 'fast-forward' update happens when Git can simply move the branch pointer forward in a straight line. If the remote branch has commits that aren't in your local branch, a linear update is impossible, resulting in a 'non-fast-forward' rejection.