Skip to content

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

Your vault is empty.

Free Fix 0x4004FC04

Office 0x4004FC04: the Activation Wizard cannot reach Microsoft servers

10 min read Updated October 5, 2026 Office & Microsoft 365 Licensing

Fix it now

Microsoft publishes no description for 0x4004FC04, and its severity bit marks it a success result rather than a failure, so the diagnosable information is in the codes beside it. Both of those are published timeouts: 0x80072EE2 is “the request has timed out” and 0x800705B4 is “this operation returned because the timeout period expired”.

Run these in an elevated Command Prompt, then retry activation

netsh winhttp show proxy
netsh winhttp import proxy source=ie
w32tm /query /status
w32tm /resync
  1. The first command matters more than it looks. Activation uses the Windows HTTP stack, not the browser, and that stack has its own proxy configuration. A browser that works proves nothing.
  2. Only import the proxy settings if your network actually requires a proxy. netsh winhttp reset proxy puts it back to a direct connection.
  3. Check the clock before blaming the firewall. A wrong date breaks the TLS handshake before any request is sent.
  4. Retry activation with cscript ospp.vbs /act from the Office folder, C:\Program Files\Microsoft Office\root\Office16 or the Program Files (x86) equivalent.

A failed attempt does not consume an activation, so you can retry as often as you need while the network problem is being sorted out.

If activation completes you are done. If it still times out, the next section works outward from the machine to find where the connection stops.

Why it happens

Start with the code you were given, because it is the least informative part of the message. 0x4004FC04 has no published description on any Microsoft page, and the HRESULT layout Microsoft documents puts a severity bit at the top which is clear on this value, marking it a success result. Whatever it is reporting, it is not the failure. The two codes that usually accompany it are the ones that carry information, and both are documented.

0x80072EE2 is WinINet error 12002, ERROR_INTERNET_TIMEOUT: “The request has timed out.” 0x800705B4 is Win32 error 1460, ERROR_TIMEOUT: “This operation returned because the timeout period expired.” Two different layers of the stack, one message: something between this machine and Microsoft did not answer in time.

Activation is an HTTPS conversation. The machine builds a request describing the product and the key, sends it on port 443 and waits for a signed response. It uses the Windows HTTP stack rather than the browser, and that single fact explains most of the wasted time on this error: the browser has its own proxy configuration and its own credentials, so a browser that reaches Microsoft tells you nothing about whether activation can.

That call has several distinct ways to fail and they all surface as timeouts. It can be blocked outright at a firewall. It can reach a proxy that demands credentials the calling process cannot supply. It can be intercepted by a TLS inspection appliance whose certificate the machine will not accept for that endpoint. It can fail name resolution. Or it can fail the handshake because the clock is wrong and the server certificate looks invalid. Neither published code distinguishes them, which is why the diagnosis has to work outward from the machine.

Windows services are not using the proxy

You have this one if The browser works, activation does not, and netsh winhttp show proxy reports a direct connection on a network that requires a proxy.

  1. Import the current settings into the system HTTP stack: netsh winhttp import proxy source=ie, which Microsoft documents as importing the proxy settings from Internet Options.
  2. Confirm the result with netsh winhttp show proxy.
  3. Retry activation.
  4. To undo the change later, netsh winhttp reset proxy resets the setting to DIRECT.

This one setting accounts for a large share of activation timeouts in managed environments, because the browser is configured centrally and the system stack is forgotten.

The proxy wants credentials the activation call cannot supply

You have this one if The proxy is configured correctly, browsing works while a user is signed in, and activation still times out, particularly during unattended deployment.

  1. Ask for the Microsoft activation and licensing endpoints to be allowed through the proxy without authentication.
  2. Where a bypass list is used, add those endpoints to it so the call goes direct.
  3. Take the endpoint list from Microsoft’s published Office and Microsoft 365 endpoint documentation rather than from a forum post. The set changes, and a stale list produces this same failure six months later.

TLS inspection is breaking the connection

You have this one if Activation fails only on the corporate network, and the organisation runs an appliance that decrypts and re-signs HTTPS traffic.

  1. Ask for the Microsoft activation and licensing endpoints to be excluded from decryption.
  2. Retest from a network without inspection first, so you are requesting a change you have already proved is needed.
  3. Confirm the appliance’s root certificate is trusted where other traffic depends on it, but do not rely on that alone for these endpoints.

The clock or the time source is wrong

You have this one if The date is visibly wrong, the machine has been switched off for a long period, or several HTTPS operations fail together.

  1. Read the current state: w32tm /query /status.
  2. Resynchronise: w32tm /resync. Its documented parameters are /computer:, /nowait, /rediscover and /soft, and nothing else.
  3. If no source is configured: w32tm /config /manualpeerlist:"time.windows.com" /syncfromflags:manual /update, then restart the Windows Time service.
  4. Check the time zone as well as the clock, then retry.

Outbound 443 is blocked to the activation endpoints

You have this one if A port test to the published endpoints fails while general browsing works through a proxy.

  1. Compare what your organisation permits against Microsoft’s current published endpoint list.
  2. Have the missing entries allowed outbound on TCP 443 from the client subnets.
  3. Retry activation, and test from a client subnet rather than from the server, because a path that works from the data centre proves nothing.

Full reference

Isolating where the connection stops

Test What the result tells you
Browser reaches Microsoft, activation does not The system HTTP stack has a different proxy configuration from the browser
netsh winhttp show proxy shows nothing on a proxied network Windows services are trying to go direct and being dropped
Test-NetConnection <host> -Port 443 fails The path is blocked at a firewall rather than at a proxy
Activation works off the corporate network Interception or filtering on the corporate path
The machine’s date is visibly wrong The TLS handshake is failing before the request is sent
Other Microsoft services fail too A broad endpoint block rather than an activation-specific one

The netsh winhttp commands, as documented

Command What Microsoft says it does
netsh winhttp show proxy Displays the current WinHTTP proxy setting
netsh winhttp import proxy source=ie Imports the proxy settings from Internet Options
netsh winhttp set proxy proxy-server="..." bypass-list="..." Configures the WinHTTP proxy setting directly
netsh winhttp reset proxy Resets the WinHTTP proxy setting to DIRECT

import proxy source=ie takes a snapshot. If the browser configuration changes later, the system stack keeps the old values until somebody imports again, which is a common way this problem reappears after a network change.

Subscription installations are a different problem

Microsoft states that the ospp.vbs script does not work for Microsoft 365 Apps or for subscription versions of Project and Visio. If the applications are the subscription build, activation is a sign-in operation against identity endpoints rather than an activation call against licensing endpoints, and the failure looks similar from the outside while needing a different set of allowances. Establish which build you have from File, Account, About before you raise a firewall request.

How much time you have

State What Microsoft publishes
A KMS-activated volume installation Licensed for 180 days, renewing every seven by default
After 180 days without activation Office enters the out-of-tolerance state for 30 days
An unlicensed installation Unlicensed Product appears in the title bar and most features are disabled

So an installation that activated recently has months of margin while the network is sorted out, and a new deployment has considerably less. That is the argument to make when a firewall change is being scheduled: this is not urgent today, and it becomes urgent for a whole estate on the same week.

When you cannot get outbound access at all

  • For volume deployments, use a KMS host or Active Directory-based activation internally. Neither needs the client to reach Microsoft.
  • For a KMS host itself, phone activation is documented: run slui.exe 4 on the host and follow the prompts.
  • Microsoft’s Support and Recovery Assistant runs a scripted set of Office activation checks and reports what it finds. It is a way to produce evidence for a network team rather than a fix in itself.
  • Do not disable TLS inspection wholesale to make an activation work. Exclude the specific endpoints and leave the rest of the policy alone.

Every code this article covers

Code What it points at Source
0x4004FC04 Reported by the Activation Wizard. No published description; its severity bit marks it a success result rather than a failure not published by the vendor
0x80072EE2 WinINet error 12002, ERROR_INTERNET_TIMEOUT: the request has timed out Microsoft Learn
0x800705B4 Win32 error 1460, ERROR_TIMEOUT: this operation returned because the timeout period expired Microsoft Learn

Confirm the fix worked

  1. cscript ospp.vbs /dstatus reports a licensed status.
  2. netsh winhttp show proxy shows the setting your network actually requires.
  3. w32tm /query /status shows a recent successful sync and a small offset.
  4. File, Account in an Office application reports the product as activated.
  5. A second machine on the same network activates too, which is what tells you the fix was environmental rather than local.

Questions people ask about this

My browser works, so why does activation fail?

Activation does not use the browser. It uses the Windows HTTP stack, which has its own proxy configuration and cannot supply a user’s credentials. Check it with netsh winhttp show proxy before assuming the network is fine.

What does 0x4004FC04 actually mean?

Microsoft does not publish a description for it. What can be said is that its severity bit is clear, which the documented HRESULT layout defines as a success result, so the failure detail is in the companion codes. Both of those are published timeouts.

Do I need to buy anything to fix this?

No. This is a connectivity fault. Your licence is untouched, and a failed attempt does not consume an activation, so retrying while the network is fixed costs nothing.

How long can Office run while I sort this out?

A KMS-activated installation is licensed for 180 days and renews every seven, then has a 30-day out-of-tolerance state. A newly deployed installation has much less margin. You have room, but not indefinitely.

Can I activate a machine that will never have internet access?

For volume deployments, yes: use a KMS host or Active Directory-based activation internally, neither of which needs the client to reach Microsoft. The host itself can be activated by phone with slui.exe 4.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix Office 30183-39: Office setup fails without a published cause License Error 0xC004F017 in Office activation: “the license is not installed” explained License Error Office 0xC004F038: your KMS count is below the minimum of five clients Free Fix Office 0xC004F001: the licensing service hits an internal error
โ† Back to Knowledge Base