FixerCode — Error Code Reference Updates

Windows 0x80070003 — Path Not Found — a directory referenced by the operation is missing from the disk

Sun, 06 Sep 2026 00:00:00 GMT

0x80070003 is the HRESULT wrapper around Win32 error 3, ERROR_PATH_NOT_FOUND, whose system text reads 'The system cannot find the path specified'. Where error 2 names a missing file, error 3 means the lookup failed earlier — one of the directories on the way to the target does not exist. Windows Upd

Windows 0x8007000E — Out of Memory — an allocation request exceeded what the system could commit

Sun, 06 Sep 2026 00:00:00 GMT

An allocation the memory manager refuses returns 0x8007000E, the HRESULT form of Win32 error 14, ERROR_OUTOFMEMORY — 'Not enough storage is available to complete this operation'. The same value is registered as E_OUTOFMEMORY in Microsoft's common-HRESULT table, so COM callers and interop layers surf

Windows 0x8007001F — Device Failure — the operating system reports an attached device no longer functions

Sun, 06 Sep 2026 00:00:00 GMT

Hardware that stops answering mid-operation surfaces as 0x8007001F, Win32 error 31, ERROR_GEN_FAILURE — 'A device attached to the system is not functioning'. The upgrade resolution documentation carries the code into setup: 8007001F-0x4000D marks a general device failure during the second-boot phase

Windows 0x80070032 — Request Not Supported — the component receiving the call has no implementation for it

Sun, 06 Sep 2026 00:00:00 GMT

A refusal that names the operation rather than any condition is 0x80070032, Win32 error 50, ERROR_NOT_SUPPORTED — 'The request is not supported'. Unlike an invalid parameter, nothing about the request is malformed; the receiver simply has no implementation behind it, which makes the code a statement

Windows 0x8007007E — Module Not Found — a required library file could not be located at load time

Sun, 06 Sep 2026 00:00:00 GMT

When the loader walks an import list and one library never resolves, the failure is 0x8007007E, Win32 error 126, ERROR_MOD_NOT_FOUND — 'The specified module could not be found'. The upgrade documentation also records the code in servicing: WSUS environments that synced upgrade metadata before a requ

Windows 0x80070103 — No More Items — the enumeration reached its end and returned nothing further

Sun, 06 Sep 2026 00:00:00 GMT

Enumerations end quietly — 0x80070103 is the HRESULT for Win32 error 259, ERROR_NO_MORE_ITEMS, whose official text is simply 'No more data is available'. In Windows Update discussions the code is overwhelmingly reported on driver deliveries: the update surface tries to install a driver for a device

Windows 0x8007025D — Bad Compression Buffer — decompressed data failed validation inside an image stream

Sun, 06 Sep 2026 00:00:00 GMT

Data that arrives inside a compressed stream and fails its structure checks stops an image apply with 0x8007025D, Win32 error 605, ERROR_BAD_COMPRESSION_BUFFER — 'The specified buffer contains ill-formed data'. The upgrade resolution tables pair the code with extend code 0x2000C and attribute it to

Windows 0x8007042B — Process Aborted — a worker process terminated before completing its assigned phase

Sun, 06 Sep 2026 00:00:00 GMT

A process that vanishes before finishing its work hands back 0x8007042B — Win32 error 1067, ERROR_PROCESS_ABORTED, whose system text reads 'The process terminated unexpectedly'. The upgrade resolution tables give the code its best-documented surface: 8007042B-0x4000D marks a second-boot failure duri

Windows 0x8007045B — Shutdown In Progress — the system is powering down and refuses new service work

Sun, 06 Sep 2026 00:00:00 GMT

Calls that arrive while Windows is already shutting down are declined with 0x8007045B, Win32 error 1115, ERROR_SHUTDOWN_IN_PROGRESS — 'A system shutdown is in progress'. The code is a boundary report: the caller reached the system, the request was understood, and the shutdown state forbade acting on

Windows 0x80070570 — File Corrupted — the file or directory is damaged and cannot be read

Sun, 06 Sep 2026 00:00:00 GMT

A read that comes back structurally damaged raises 0x80070570, Win32 error 1392, ERROR_FILE_CORRUPT — 'The file or directory is corrupted and unreadable'. Windows Update troubleshooting lists the code under component store corruption, with the documented repair being DISM RestoreHealth followed by S

Windows 0x800705AA — No System Resources — kernel-level pools are too depleted to service the request

Sun, 06 Sep 2026 00:00:00 GMT

Kernel bookkeeping has ceilings of its own, and exhausting them returns 0x800705AA, Win32 error 1450, ERROR_NO_SYSTEM_RESOURCES — 'Insufficient system resources exist to complete the requested service'. The message deliberately avoids the word memory: the shortage sits in fixed-size kernel pools and

Windows 0x800706BA — RPC Server Unavailable — the remote procedure endpoint could not be reached

Sun, 06 Sep 2026 00:00:00 GMT

Remote procedure calls begin with a rendezvous, and 0x800706BA, Win32 error 1722, RPC_S_SERVER_UNAVAILABLE — 'The RPC server is unavailable' — means that rendezvous never happened. Management tooling that leans on DCOM and WMI makes the code a common cross-machine diagnostic: the local caller works,

Windows 0x800706BE — RPC Call Failed — the request reached its server but the server-side execution failed

Sun, 06 Sep 2026 00:00:00 GMT

The code 0x800706BE, Win32 error 1726, RPC_S_CALL_FAILED — 'The remote procedure call failed' — describes a delivered call with a dead execution. The endpoint answered, the method was invoked, and the failure happened inside the server process, which separates it from 1722, where nothing was ever re

Windows 0x80071392 — Object Already Exists — a creation request collided with an object using the same identity

Sun, 06 Sep 2026 00:00:00 GMT

Two objects cannot hold one identity, and a creation that tries anyway fails with 0x80071392, Win32 error 5010, ERROR_OBJECT_ALREADY_EXISTS — 'The object already exists'. The constant originates in the cluster resource API family — its message speaks of resources and groups — and servicing or manage

Windows 0x8007139F — Invalid State — the target is not in the state this operation requires

Sun, 06 Sep 2026 00:00:00 GMT

State machines accept only certain transitions, and a request issued from the wrong state is refused with 0x8007139F, Win32 error 5023, ERROR_INVALID_STATE — the official message reads 'The group or resource is not in the correct state to perform the requested operation'. The refusal is about orderi

Windows 0x80072EFD — Cannot Connect — the TCP connection attempt failed before any server response

Sun, 06 Sep 2026 00:00:00 GMT

A TCP connect that dies before the first response byte — refused, unroutable, or silently filtered — produces 0x80072EFD, the HRESULT form of WinINet error 12029, ERROR_INTERNET_CANNOT_CONNECT: 'The attempt to connect to the server failed'. Windows Update troubleshooting groups the code with 0x80072

Windows 0x80072EE7 — Name Not Resolved — DNS could not translate the target hostname into an address

Sun, 06 Sep 2026 00:00:00 GMT

Before any HTTP exchange, a hostname has to become an address; when that translation fails, WinINet reports 0x80072EE7, error 12007, ERROR_INTERNET_NAME_NOT_RESOLVED — 'The server name could not be resolved'. The failure happens ahead of connecting entirely, so no server ever sees the request and no

Windows 0x80072EFE — Connection Aborted — an established link was terminated while data was still moving

Sun, 06 Sep 2026 00:00:00 GMT

Transfers that die mid-flight — after the handshake, during the payload — end with 0x80072EFE, the HRESULT of WinINet error 12030, ERROR_INTERNET_CONNECTION_ABORTED: 'The connection with the server has been terminated'. Windows Update documentation gives the code a specific owner: BITS, which surfac

Windows 0x800B0109 — Untrusted Root Certificate — the certificate chain ends at a root the trust provider rejects

Sun, 06 Sep 2026 00:00:00 GMT

Certificate chains can verify cleanly and still be refused at the last step: 0x800B0109, CERT_E_UNTRUSTEDROOT, fires when the chain terminates in a root certificate the trust provider does not trust. Microsoft's DirectAccess troubleshooting documents the code for IP-HTTPS connections, and the same f

Windows 0x80244018 — Update Endpoint Forbidden — the update server answered the scan with HTTP status 403

Sun, 06 Sep 2026 00:00:00 GMT

Inside the Windows Update protocol talker, an HTTP 403 from the update source is re-raised as 0x80244018, WU_E_PT_HTTP_STATUS_FORBIDDEN. Microsoft's error reference defines it — 'Same as HTTP status 403 - server understood the request but declined to fulfill it' — and the upgrade documentation pairs

Windows 0x80244019 — Update Content Missing — the requested URI returned HTTP 404 at the update source

Sun, 06 Sep 2026 00:00:00 GMT

An HTTP 404 returned to the Windows Update agent is re-raised as 0x80244019, WU_E_PT_HTTP_STATUS_NOT_FOUND — 'Same as HTTP status 404 - the server can't find the requested URI (Uniform Resource Identifier)'. Microsoft's error reference defines the code in the protocol-talker family, and in managed e

Windows 0x800F0906 — Feature Source Unreachable — servicing could not download the optional feature payload

Sun, 06 Sep 2026 00:00:00 GMT

Optional features such as .NET Framework 3.5 are not stored on disk by default, and when servicing cannot fetch their payload the request fails with 0x800F0906. Microsoft's .NET Framework 3.5 installation guidance records the message — 'The source files could not be downloaded' — and attributes the

Windows 0x800F0954 — Feature Blocked by WSUS — feature installs are routed to a server without the payload

Sun, 06 Sep 2026 00:00:00 GMT

On machines whose feature installs are routed through WSUS, optional-capability requests can reach a server that carries no such payload, and the failure surfaces as 0x800F0954. Microsoft's troubleshooting record for .NET Framework 3.5 states the condition: the error occurs when an alternative insta

Windows 0xC1900200 — Minimum Requirements Block — setup halted because the hardware does not meet the floor

Sun, 06 Sep 2026 00:00:00 GMT

Before writing anything to disk, Windows Setup checks the machine against the hardware floor, and a machine that does not clear that check stops with 0xC1900200, MOSETUP_E_COMPAT_SYSREQ_BLOCK. Microsoft's modern-setup table defines the constant — 'The system does not pass the minimum requirements to

Windows 0xC1900208 — Compatibility Scan Block — setup refused to continue over unresolved software conflicts

Sun, 06 Sep 2026 00:00:00 GMT

The actionable compatibility phase exists to stop upgrades that installed software would break, and blocking findings there produce 0xC1900208, MOSETUP_E_COMPAT_INSTALLREQ_BLOCK — the constant Microsoft's modern-setup table describes as failing 'the compat scan to install the update'. The companion

Windows 0xC1900107 — Cleanup Pending — a prior installation attempt left cleanup work that a restart must finish

Sun, 06 Sep 2026 00:00:00 GMT

Setup Platform refuses to start over an unfinished predecessor: 0xC1900107, MOSETUP_E_CLEANUP_PENDING, means a previous installation attempt left cleanup operations outstanding. Microsoft's table entry for 0xC1900107 reads 'A cleanup operation from a previous installation attempt is still pending. A

Windows 0xC1900109 — Compatibility Termination — the install process was killed during its actionable compatibility phase

Sun, 06 Sep 2026 00:00:00 GMT

Termination during the actionable compatibility phase — as opposed to a blocking verdict or a user cancellation — is what 0xC1900109, MOSETUP_E_COMPAT_TERMINATE, encodes. The modern-setup table entry reads 'The installation process was terminated during the actionable compatibility phase', giving th

Windows 0x80131500 — COR_E_EXCEPTION — the managed runtime's base HRESULT for an unhandled exception

Sun, 06 Sep 2026 00:00:00 GMT

Every managed exception in the CLR carries an HRESULT, and the base value — assigned when nothing more specific applies — is 0x80131500, COR_E_EXCEPTION. Microsoft's Exception class documentation states the pairing directly: the class uses the HRESULT COR_E_EXCEPTION, which has the value 0x80131500,

Git cannot-pull-with-rebase-unstaged-changes — Git refused a pull configured for rebase because tracked files carry uncommitted edits.

Sun, 06 Sep 2026 00:00:00 GMT

When pull.rebase is enabled or --rebase is passed, a pull re-applies your local commits onto the fetched branch instead of merging. That replay requires a clean working tree, so Git screens for uncommitted edits before the rebase step and stops the whole pull when any are found.

Git cannot-rebase-unstaged-changes — Git declined to start a rebase while the working tree holds unstaged modifications.

Sun, 06 Sep 2026 00:00:00 GMT

A rebase rewrites the checkout by lifting your commits off their base and reapplying them elsewhere. Every step rewrites files, so unstaged edits have nowhere safe to live during the process. Before touching anything, Git runs a cleanliness check and exits with this message when tracked files differ

Git you-need-to-resolve-your-current-index-first — A branch switch or similar operation stopped because the index still holds unmerged entries.

Sun, 06 Sep 2026 00:00:00 GMT

Switching branches requires a consistent index: one recorded version per path. While a merge, cherry-pick, or stash application has unresolved conflicts, affected paths carry multiple competing stages, and Git refuses to build a different branch on top of that ambiguity until the entries collapse ba

Git this-operation-must-be-run-in-a-work-tree — The command ran inside a bare repository or a Git directory, where no checkout exists.

Sun, 06 Sep 2026 00:00:00 GMT

Git splits a repository into two parts: the object database under .git, and the working tree that holds checked-out files. Commands such as status, pull, or commit need files to compare against. When the current directory is a bare clone (or a .git folder itself), that file side is absent, so the co

Git cannot-do-a-partial-commit-during-a-merge — Committing selected paths was refused because a merge must be recorded as one unit.

Sun, 06 Sep 2026 00:00:00 GMT

Passing file paths to git commit records only those paths and leaves the rest of the index for later. During a merge that selectivity would split the merge result into pieces, so Git refuses path-scoped commits outright while MERGE_HEAD exists, regardless of whether the tree is clean or conflicts re

Git stash-pop-conflict — Reapplying a stash hit conflicts, and the stash entry was deliberately kept.

Sun, 06 Sep 2026 00:00:00 GMT

git stash pop is a two-step command: apply the stored snapshot, then drop it on success. When the tree changed since the stash was taken, the apply half behaves like a merge and can conflict. On conflict, Git keeps the entry in the stash list so nothing is lost, and leaves conflict markers in the af

Git not-possible-to-fast-forward — A fast-forward-only integration was refused because local and fetched histories diverged.

Sun, 06 Sep 2026 00:00:00 GMT

The --ff-only option promises Git that the update can be a pure pointer move: no merge commit, no rewriting. When both sides added commits, that promise cannot be kept. Git prints an advice block about diverging branches, then exits with 'Not possible to fast-forward, aborting.' before touching the

Git your-branch-and-origin-have-diverged — Status reports both the local branch and its upstream holding separate new commits.

Sun, 06 Sep 2026 00:00:00 GMT

After a fetch, git status compares your branch against its upstream and can count commits on each side. The diverged line appears when both counts are non-zero, phrased as 'have diverged, and have N and M different commits each, respectively.' It is a report, not a refusal — nothing has failed yet.

Git gh006-protected-branch-update-failed — GitHub refused the push because branch protection rules blocked updating the target ref.

Sun, 06 Sep 2026 00:00:00 GMT

Protected branches carry server-side rules: required pull requests, review approvals, status checks, push restrictions. When a direct push violates one, GitHub rejects the ref update and reports it with the GH006 error code, prefixing the remote's own error line: 'GH006: Protected branch update fail

Git refusing-to-update-checked-out-branch — A push into a non-bare repository's active branch was denied by that repository's settings.

Sun, 06 Sep 2026 00:00:00 GMT

Pushing to a branch that the receiving repository currently has checked out would leave its index and working tree disagreeing with the new HEAD. Git's receive-pack guards this by default and answers with 'refusing to update checked out branch: refs/heads/', followed by an explanation of the r

Git origin-does-not-appear-to-be-git-repository — The remote address answered, but the path behind it holds no Git repository.

Sun, 06 Sep 2026 00:00:00 GMT

This message appears when the configured URL points somewhere Git can reach, yet the target is not a repository: a plain directory over a file or SSH path, a wrong home directory, or a service URL instead of a repo URL. The remote-side probe fails, and the client adds 'Could not read from remote rep

Git terminal-prompts-disabled — Git needed credentials, found prompting disabled, and no helper supplied them.

Sun, 06 Sep 2026 00:00:00 GMT

Interactive terminals ask for usernames and passwords when a server demands them. In non-interactive shells — CI jobs, hooks, scheduled tasks — prompting is switched off with GIT_TERMINAL_PROMPT=0 or simply unavailable. Git then dies with 'could not read Username for : terminal prompts disabled

Git http-407-proxy-connect — The corporate proxy answered the tunnel request with HTTP 407, demanding authentication.

Sun, 06 Sep 2026 00:00:00 GMT

Over HTTPS, Git reaches hosting services through a CONNECT tunnel negotiated with the proxy. When the proxy demands its own credentials it returns status 407, and the transfer dies with the library message 'Received HTTP code 407 from proxy after CONNECT'. Git additionally discards any stored proxy

Git fetch-pack-invalid-index-pack-output — The helper unpacking a fetched pack produced output the fetcher could not interpret.

Sun, 06 Sep 2026 00:00:00 GMT

During a fetch or clone, git fetch-pack receives the server's packfile and hands it to index-pack, reading back its structured progress. When that output deviates from the expected dialogue — often after a truncated stream or an out-of-memory death inside the unpacker — the fetch ends with 'fetch-pa

Git protocol-error-bad-pack-header — The stream fetched from the server did not start with a valid packfile header.

Sun, 06 Sep 2026 00:00:00 GMT

Every packfile begins with a signature, a version, and an object count. When the bytes arriving during a fetch fail that check, the unpacker reports 'protocol error: bad pack header' and the transfer dies. The cause is usually upstream: server-side pack corruption, or a middleman rewriting the strea

Git ssl-unable-to-get-local-issuer-certificate — The TLS layer found no trusted issuer to complete the server's certificate chain.

Sun, 06 Sep 2026 00:00:00 GMT

Certificate verification walks from the server's certificate up to a root the client trusts. When an intermediate certificate is missing from what the server sends and the local trust store cannot supply the missing link, the TLS library reports 'unable to get local issuer certificate' and Git wraps

Git ssl-certificate-revoked — The certificate presented by the server was rejected because its issuer revoked it.

Sun, 06 Sep 2026 00:00:00 GMT

Issuers can revoke a certificate before expiry — after key compromise or domain loss. Clients that check revocation (CRL or OCSP, or Windows schannel enforcement) refuse the connection. Git surfaces the library's wording: OpenSSL builds report it as a certificate problem, Windows builds print the sc

Git insufficient-permission-adding-object — Git could not write a new object file because the object database denied the write.

Sun, 06 Sep 2026 00:00:00 GMT

Every commit, blob, and tree lands as a file under .git/objects. When the operating system refuses that write — typical after several user accounts share one repository, or after a sudo-run Git created root-owned directories — the command dies with 'insufficient permission for adding an object to re

Git object-file-is-empty — A loose object file exists on disk but holds zero bytes, breaking reads.

Sun, 06 Sep 2026 00:00:00 GMT

Loose objects are small compressed files whose length and checksum Git validates on every read. A zero-byte file — the classic residue of an interrupted write, a full disk, or a sync tool that created the name without content — fails the read with 'error: object file .git/objects/xx/... is empty'.

Git not-a-git-command — The invoked subcommand is not among the commands this Git installation provides.

Sun, 06 Sep 2026 00:00:00 GMT

Typing git subcommand-name makes Git search its command table; an unmatched name produces 'git: '' is not a git command. See 'git --help'.', often alongside did-you-mean suggestions. The cause is usually a typo — or an alias, external tool, or plugin assumed present that this installation neve

Git lf-will-be-replaced-by-crlf — Git warns that LF line endings will become CRLF on a file next rewrite.

Sun, 06 Sep 2026 00:00:00 GMT

With core.autocrlf enabled on Windows, Git stores LF in the repository and converts to CRLF in the working tree. The warning fires when a working-tree file's endings do not match that policy — modern Git phrased it 'in the working copy of , LF will be replaced by CRLF the next time Git touches

Git unshallow-on-complete-repository — The --unshallow flag was passed to a fetch in a repository that is not shallow.

Sun, 06 Sep 2026 00:00:00 GMT

--unshallow exists to convert a shallow clone, one with truncated history, into a complete copy by fetching the missing depth. Running it in a repository whose history is already complete has no effect to produce, so Git refuses up front: 'fatal: --unshallow on a complete repository does not make se