Fix it now
Microsoft documents 30174-4 as antivirus software, a firewall, proxy settings or the connection preventing Office from installing. The suffixed relatives – 30174-4-2, 30174-4-5, 30174-4-32, 30174-123 and 30174-183 – are on a different page with a different cause: corrupted Office files. Read your code to the last digit before you touch anything.
nslookup officecdn.microsoft.com
curl.exe -I https://officecdn.microsoft.com
netsh winhttp show proxy
w32tm /query /status
- If your code is plain 30174-4, work the network: use the offline installer, try a wired connection or a different network, check proxy settings, and test with antivirus temporarily off.
- If your code carries a suffix, restart the machine and reinstall. Microsoft’s remedy for that group is a clean reinstall, not a network change.
- If the reinstall fails too, run Microsoft’s uninstall troubleshooter, restart when it asks, then install again from a fresh download.
The uninstall troubleshooter needs Windows 10 or later, has to run on the affected PC, and Microsoft states it cannot uninstall Office 2024. Uninstall that one from Settings or Control Panel instead.
If Office installs you can stop here. If not, the next section explains the four stages a setup request passes through and how to tell which one you are stuck at.
Why it happens
Office setup makes ordinary HTTPS requests, and every one of them passes four stages. The name has to resolve, a connection has to open on 443, a TLS handshake has to complete, and the far end has to return something the installer understands. A failure at stage one and a failure at stage three look identical from inside the installer, which is why one code covers so much ground.
Microsoft’s page for the bare 30174-4 puts the cause in that territory: anti-virus software, firewall, proxy settings, or the connection prevent you from installing Office. Its remedies are the offline installer, a wired connection, a different network, disabling proxy settings, and temporarily turning off antivirus and the firewall. That is a network-and-security page and its advice is worth following in that order.
The suffixed codes are the trap. 30174-4-2, 30174-4-5, 30174-4-32, 30174-123 and 30174-183 have their own Microsoft page, and it gives a single, different cause: corrupted Office files. The remedy there is restart and reinstall, then uninstall with the troubleshooter and reinstall. Chasing a firewall for one of those is chasing the wrong machine entirely, and it is the mistake this family produces most often.
So the first thing to do is read the code precisely. A dialog that says 30174-4 with nothing after it is one problem. A dialog that says 30174-4-32, or the same number with a parenthesised value after it, is another. Screenshot it rather than working from memory, because the difference decides everything that follows.
Plain 30174-4 on a filtered network
You have this one if The bare code, and the same account installs Office without complaint on a home connection or a phone hotspot.
- Use Microsoft’s offline installer, which is its first recommended remedy for this code.
- If you need the streamed install to work, check the machine-level proxy with
netsh winhttp show proxyand correct it. - Have outbound HTTPS to
officecdn.microsoft.comandofficeclient.microsoft.compermitted from the client subnets, by hostname. - Test with the antivirus product temporarily disabled, then re-enable it and ask for an exclusion if that was the cause.
A suffixed code, which is a corrupted-files problem
You have this one if The code has a trailing number after the 4, or reads 30174-123 or 30174-183.
- Restart the machine and reinstall Office. That is Microsoft’s first remedy for this group.
- If it fails again, run Microsoft’s uninstall troubleshooter, restart when prompted, and reinstall.
- Install from a freshly downloaded source rather than a copy that has been sitting on a share.
Do not raise a firewall change for one of these. Microsoft attributes them to corrupted Office files, and nothing on the network will make a damaged local installation start working.
Name resolution is failing
You have this one if nslookup officecdn.microsoft.com returns nothing, or an address that clearly does not belong to Microsoft.
- Check the configured DNS servers with
ipconfig /alland confirm they are the ones you expect. - Clear the resolver cache with
ipconfig /flushdns, then test again. - Fix a non-forwarding internal resolver or a sinkholing filter at that service, not by hard-coding anything on the client.
The TLS handshake cannot complete
You have this one if The name resolves and the port opens, but curl.exe fails, on a machine that is old or has had a security hardening baseline applied.
- Check the clock first with
w32tm /query /status, thenw32tm /resync. Certificates are validated against local time. - On a hardened machine, review the SCHANNEL protocol settings and confirm current TLS versions have not been disabled for the client role.
- Correct the baseline rather than the single machine, and reboot afterwards; these values are read at start-up.
Microsoft’s page for 30174-4 does not name TLS as a cause. This is a real failure mode you can prove with curl.exe, but treat it as diagnosis rather than as documented.
A VPN, captive portal or split tunnel is breaking the path
You have this one if The machine is on a guest network, a hotel connection or a VPN, and results change with the connection.
- Complete any captive portal sign-in in a browser before starting setup.
- Disconnect the VPN if outbound access does not require it, or confirm the Office endpoints are inside the tunnel if it does.
- Rerun the four checks on the connection you actually intend to install over.
Full reference
Which stage failed, and who owns it
| First failing check | Stage and owner |
|---|---|
nslookup returns nothing |
Name resolution: the client’s DNS servers or a filtering service |
The name resolves, curl.exe never returns |
Connectivity: an outbound firewall rule, or an inspecting device holding the request |
curl.exe fails immediately with a TLS error |
Protocol negotiation or certificate validation, which includes the clock |
netsh winhttp show proxy shows Direct access |
Services are not using the required proxy |
| All four pass and setup still fails | Local state. If the code is suffixed, that was always the answer |
Export any SCHANNEL key before you edit it: reg export "HKLM\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL" schannel.reg from an elevated prompt. Getting these values wrong can leave a machine unable to make any secure connection at all, including to your own management systems, and the export is what lets you recover it.
Reading the code to the last digit
| Code as shown | Microsoft’s published cause | Where to start |
|---|---|---|
30174-4 |
Anti-virus, firewall, proxy settings or the connection | Offline installer, then proxy, then antivirus |
30174-4-2 |
Corrupted Office files | Restart and reinstall |
30174-4-5 |
Corrupted Office files | Restart and reinstall |
30174-4-32 |
Corrupted Office files | Restart and reinstall |
30174-123 |
Corrupted Office files | Restart and reinstall |
30174-183 |
Corrupted Office files | Restart and reinstall |
Installing from a local source instead
- On a machine with working access, build a source with the Office Deployment Tool:
setup.exe /download configuration.xml. - Copy the resulting folder to a share the failing machine can reach, or to the machine itself.
- Install with
setup.exe /configure configuration.xmlfrom an elevated Command Prompt. - Sign in afterwards. Activation still needs the identity and licensing endpoints, so a completely isolated machine will get further and then stop.
When the network is demonstrably fine
- Check free space on the system volume before anything else. Setup needs working room well beyond the finished size.
- Confirm the Microsoft Office Click-to-Run service exists and is not Disabled in
services.msc. A disabled service produces its own documented code, 30068. - Look at whether a management tool is deploying Office at the same time. Two installers competing produce failures that move around between attempts.
- Run the uninstall troubleshooter even if Office does not appear installed. Registration can survive a removal that took the files away.
- Test with a local administrator account on a machine where application control policy might be blocking the installer.
One more thing worth knowing: if a machine gives you a bare 30174-4 on Monday and a suffixed one on Tuesday, that is not the same fault twice. It usually means the first attempt got far enough to leave a partial installation behind, and you are now dealing with the local damage as well as whatever stopped the first run.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
30174-4 |
Anti-virus software, a firewall, proxy settings or the connection are preventing Office from installing | Microsoft Support |
30174-123 |
Grouped by Microsoft with the suffixed 30174 codes and attributed to corrupted Office files | Microsoft Support |
30174-183 |
Same group, same published cause: corrupted Office files | Microsoft Support |
30174-4-2 |
Same group, same published cause: corrupted Office files | Microsoft Support |
30174-4-5 |
Same group, same published cause: corrupted Office files | Microsoft Support |
30174-4-32 |
Same group, same published cause: corrupted Office files | Microsoft Support |
Confirm the fix worked
- The four checks – resolution, request, proxy and clock – all return what you expect.
- Setup completes and Word opens without a setup prompt.
- File, then Account shows the product, version and channel you meant to install.
- Sign in and confirm the account panel reports the subscription, which proves the identity and licensing endpoints are reachable too.
- If you disabled antivirus or the firewall to test, confirm both are back on.
Questions people ask about this
Do I need to buy anything?
No. Every documented cause here is network configuration, security software or damaged local files. Licensing is not reached until Office is installed and someone signs in.
My code has extra numbers after it. Does that matter?
It decides the fix. Microsoft documents the bare 30174-4 as a network and security-software problem and the suffixed variants as corrupted Office files, on separate pages with separate remedies. Screenshot the dialog before you close it.
Which check matters most?
The first one that fails. Fixing a later stage while an earlier one is broken achieves nothing, and the order – resolution, connection, handshake, response – is always the same.
Why would the clock stop an installer?
TLS validates certificates against local time. If the clock is far enough out, every certificate looks either not yet valid or already expired, and no secure connection can be established at all. w32tm /resync is the fix, and note that /force is not a parameter of that command.
Can I install offline instead?
Yes. Build a source with the Office Deployment Tool on a network that works and install from it. Activation still needs the identity and licensing endpoints afterwards, so the network work does not disappear entirely.
