Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 0x800C0006

0x800C0006: .NET Web Installer and ClickOnce Downloads Fail Part-Way

9 min read Updated October 5, 2026 Installers, Runtimes & App Deployment

Fix it now

These are download-layer codes. The setup logic never got as far as installing anything: it asked for a file and did not receive it. Microsoft publishes each of them as a specific transport failure, and one of them – 0x800C0005 – means the server or proxy could not be found rather than the file. An offline installer removes the whole problem.

Run these from an elevated Command Prompt on the machine that is failing

netsh winhttp show proxy
nslookup <the vendor download host>
netsh winhttp import proxy source=ie
  1. Use the offline or full installer instead of the small web bootstrapper if the vendor publishes one. That removes the download step entirely and is the reliable answer in a managed environment.
  2. Compare the machine-level proxy the first command reports with what the browser uses. They are separate settings and a bootstrapper running as SYSTEM cannot read the browser’s.
  3. Check the system clock, including the year. A wrong date breaks certificate validation and produces download failures with no obvious explanation.
  4. If a filtering appliance is in the way, ask for the vendor’s download hosts to be allowed rather than working around it locally.

The third command copies the current user’s proxy settings into the machine-level configuration. Run it only if you have established that the two genuinely should match.

If the download completes you are done. If it does not, the next section explains which layer each code comes from and what that rules out.

Why it happens

Windows has more than one way to fetch a URL and they do not share configuration. One stack reads the per-user internet settings, the same ones a browser uses. The other reads a separate machine-level proxy configuration. A bootstrapper using the first works when you run it interactively and fails when the same package is deployed by an agent running as SYSTEM, because SYSTEM has no user proxy settings to read.

That single fact accounts for a large share of these failures in managed environments, and it also explains why the offline installer is recommended so often. It takes the network out of the question: the payload is already local when setup begins.

The codes themselves are precise, and one of them is routinely described wrongly. Microsoft publishes 0x800C0005 as INET_E_RESOURCE_NOT_FOUND, “The server or proxy was not found” – a name-resolution or proxy-reachability failure, not a missing file. 0x800C0006 is INET_E_OBJECT_NOT_FOUND, “The object was not found”, which is the missing-file case. 0x800C0008 is INET_E_DOWNLOAD_FAILURE, published as the download having failed because the connection was interrupted. 0x800C000B is INET_E_CONNECTION_TIMEOUT.

Knowing which is which saves real time. 0x800C0005 sends you to DNS and the proxy. 0x800C0006 sends you to the URL and whether the vendor has moved the payload. 0x800C0008 and 0x800C000B both describe a connection that started and did not finish, which is where inspection appliances and unstable links live.

A proxy or filtering appliance is intercepting the download

You have this one if Browsing works, the installer fails, and the organisation runs a web filter or inspects TLS.

  1. Compare netsh winhttp show proxy with the browser’s settings and align them if they should match.
  2. Ask for the vendor’s download hosts to be excluded from inspection, or allowed outright.
  3. Where the tool supports it, point the installer at a local copy of the payload.
  4. Use the offline installer, which removes the dependency altogether.

The setup is running in a context with no network identity

You have this one if The installer works when you run it and fails when the same package is deployed by an agent, a startup script or a scheduled task.

  1. Download the payload once and deploy the offline package rather than the web bootstrapper.
  2. Where a proxy requires authentication, remember SYSTEM cannot supply user credentials; either allow the download host unauthenticated or stage the file locally.
  3. Stage installers on an internal distribution point so the deployment never leaves the network.

If the code is 0x800C0009 rather than one of the four here, that is INET_E_AUTHENTICATION_REQUIRED and it says the proxy authentication case outright.

Name resolution or the proxy address is wrong

You have this one if 0x800C0005 specifically, and nslookup on the download host fails or returns something unexpected.

  1. Resolve the vendor’s download host by name from the failing machine and confirm the answer looks sane.
  2. Confirm the proxy named in the machine-level configuration actually exists and is reachable.
  3. Check for a stale proxy entry left behind by a laptop that has moved networks.

TLS negotiation or certificate validation is failing

You have this one if Downloads fail from one machine and succeed from a newer one on the same network, or only older applications are affected.

  1. Confirm the system date, time and time zone are correct.
  2. Let the machine complete Windows Update so it has current root certificates.
  3. Confirm any inspection appliance’s certificate is trusted by the machine, not only by the browser.
  4. For applications built against older defaults, follow the vendor’s guidance on enabling current TLS versions rather than changing framework-wide settings on a guess.

Full reference

The published meaning of every code in this family

Code Name Published meaning
0x800C0002 INET_E_INVALID_URL The URL could not be parsed.
0x800C0004 INET_E_CANNOT_CONNECT The attempt to connect to the Internet has failed.
0x800C0005 INET_E_RESOURCE_NOT_FOUND The server or proxy was not found.
0x800C0006 INET_E_OBJECT_NOT_FOUND The object was not found.
0x800C0008 INET_E_DOWNLOAD_FAILURE The download has failed (the connection was interrupted).
0x800C0009 INET_E_AUTHENTICATION_REQUIRED Authentication is needed to access the object.
0x800C000B INET_E_CONNECTION_TIMEOUT The Internet connection has timed out.
0x800C000E INET_E_SECURITY_PROBLEM A security problem was encountered.

0x800C0009 is worth watching for on a corporate network. If a bootstrapper reports it, the proxy is asking for credentials the installer has no way to supply, and no amount of certificate or TLS work will change that. Either the host is allowed without authentication or the payload is staged locally.

ClickOnce has its own failure modes

A ClickOnce application is described by a manifest, downloaded on demand and cached per user. It fails for all the ordinary network reasons, and also when the manifest cannot be verified, when the signing certificate has expired, or when the cached copy on the machine is stale or damaged.

  1. Confirm the deployment URL still resolves and returns the manifest rather than an error page or a login form.
  2. Remove the deployed application through Settings, Apps, Installed apps, then launch it again from its deployment URL. That forces a clean download.
  3. Ask the publisher whether the signing certificate is still valid; an expired one blocks installation and update.
  4. Try from a second user profile on the same machine. The cache is per user, so a fault that follows the profile is a cache problem and a fault that does not is a network one.
  5. If the deployment is hosted internally, check that the web server still serves the manifest’s content type correctly after any change to it.

Why the offline installer is not a workaround

It is easy to treat the offline package as an admission of defeat. It is not. For managed and disconnected environments it is the supported deployment route: the bytes are fixed, the deployment is repeatable, and nothing about the outcome depends on what a proxy did that afternoon. If you are deploying to more than a handful of machines, stage the payload internally and stop asking each device to fetch it.

Diagnostics worth running before you escalate

Command What it tells you
netsh winhttp show proxy The machine-level proxy configuration, which is what a SYSTEM-context installer uses
nslookup <host> Whether the download host resolves at all from this machine
certutil -hashfile <file> SHA256 Whether a payload that did arrive matches what the vendor published
System clock and time zone Whether certificate validation can succeed

Every code this article covers

Code What it points at Source
0x800C0006 INET_E_OBJECT_NOT_FOUND: the object was not found Microsoft Learn
0x800C0005 INET_E_RESOURCE_NOT_FOUND: the server or proxy was not found – a name-resolution or proxy problem, not a missing file Microsoft Learn
0x800C0008 INET_E_DOWNLOAD_FAILURE: the download failed because the connection was interrupted Microsoft Learn
0x800C000B INET_E_CONNECTION_TIMEOUT: the connection timed out Microsoft Learn

Confirm the fix worked

  1. Rerun the installer and confirm the download stage completes rather than failing part-way.
  2. Run netsh winhttp show proxy and confirm the machine-level setting matches your environment.
  3. Launch the installed application, or the ClickOnce deployment, and confirm it starts.
  4. For a managed deployment, rerun it from the management tool and confirm it records success rather than a download failure.
  5. If you staged the payload internally, verify its hash on the distribution point so the next machine gets the same bytes.

Questions people ask about this

Will buying a licence make this work?

No. These are network transport errors and they occur whether the software is licensed, trial or free. A key changes nothing about whether a file downloads.

What is the difference between 0x800C0005 and 0x800C0006?

0x800C0005 is published as the server or proxy not being found, so it points at name resolution and proxy reachability. 0x800C0006 is the object not being found, which points at the URL and the payload. They lead in opposite directions and are frequently confused.

Is it safe to keep using the offline installer permanently?

Yes, provided you take it from the vendor and verify it. Offline packages are the supported route for managed and disconnected environments and make deployments predictable.

Should I turn off TLS inspection to fix this?

That is a decision for whoever owns the security policy, not something to do locally. The usual answer is an exclusion for a small set of known download hosts, which leaves inspection in place everywhere else.

Why does the same installer work at home but not at work?

Because the home network has no proxy, no inspection and no filtering in the way. That difference alone accounts for most of these reports and points straight at the network path rather than the machine.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix MSI 1633: This Installation Package Is Not Supported on This Platform Free Fix MSI 1612 and 1706: Installation Source Missing When You Repair or Remove Apps Free Fix Runtime Error R6034: An Application Made an Invalid Attempt to Load the CRT Free Fix MSI 1335: The Cabinet File Required for This Installation Is Corrupt
โ† Back to Knowledge Base