Fix it now
Microsoft publishes no meaning for 30204-44, but it does publish one for its neighbour 30180-4: you might see this error if your anti-virus software, firewall, proxy settings or connection prevent you from installing Office. Identify which of those intervened before changing anything, because the fix is specific to the product involved.
- Open Windows Security, then Virus and threat protection, then Protection history, and look for a block or quarantine entry at the exact time setup failed. If you run a third-party product, open its own quarantine and blocked-events log for the same moment.
- Right-click the installer, open Properties, and if there is an Unblock checkbox at the bottom of the General tab, tick it and apply. In PowerShell,
Unblock-File -Path <installer>does the same. - If the machine is centrally managed, check whether application control or attack surface reduction rules are blocking the installer before touching antivirus settings.
- If the estate uses FSLogix, run
"C:\Program Files\FSLogix\Apps\frx.exe" list-rules– Microsoft documents FSLogix hiding an Office executable as the cause of 30010-45. - As a test only, on a machine you control and a network you trust, turn real-time protection off for the length of the installation, then turn it straight back on.
Microsoft’s own guidance for this family includes temporarily turning antivirus and the firewall off, and turning the browser proxy off, as diagnostic steps. They are tests, not configurations to leave behind.
If setup completes, you can stop here – after re-enabling anything you disabled. If it still fails, the next section covers each blocker and how to clear it properly.
Why it happens
Setup is a chain of ordinary operations: fetch content, write files, register components, start a service. A security product can interrupt any of them, and from the installer’s point of view it usually does so silently – the file is simply not there, or the write is refused, or the process is terminated. Setup reports the failure it saw rather than the reason behind it, which is why the code names a stage and not a product.
Of the six codes in this record, one carries a published cause that matches the article’s premise exactly. Microsoft’s page for 30180-4 says you might see this error if your anti-virus software, firewall, proxy settings, or connection prevent you from installing Office, and its remedies are the offline installer, a wired connection, trying from a different location, turning the browser proxy off, turning antivirus off, and turning the firewall off. That is the documented backbone here.
Two others are documented with something different, and both are worth knowing. 30010-45 is published, with 30088-26, as FSLogix being set to hide Officeclicktorun.exe or another Office executable – a profile management rule, not a scanner. And 30145 – the page shows 30145-4 – and 30175-11 both have Microsoft pages that give remedies without stating a cause: restart, Online Repair, then uninstall and reinstall for the first, and the uninstall troubleshooter followed by a reinstall for the second.
The remaining two, 30204-44 and 30182-44, have no vendor text at all. There is a tempting rule that suffixes ending in 44 and 45 mean something was blocked rather than something failed. It does not survive contact with the documentation: 30010-45 is FSLogix hiding a file. Use the security product’s own log to confirm interference, not the shape of the number.
Real-time scanning quarantined a setup file
You have this one if Protection history shows an entry at the moment of failure, often naming a file in the temp folder.
- Re-download the installer from Microsoft rather than restoring an item from quarantine, unless you are certain of its origin.
- Add an exclusion for the setup folder and the temp path while you install: in PowerShell,
Add-MpPreference -ExclusionPath "C:\Windows\Temp"and the folder you are installing from. - Run setup, then remove any exclusion you added and confirm protection is fully on:
Get-MpComputerStatus.
An endpoint or attack surface reduction policy is blocking it
You have this one if The machine is centrally managed, the local antivirus log shows nothing, and the failure is consistent across a group of machines.
- List the rules in force:
Get-MpPreference | Select-Object -ExpandProperty AttackSurfaceReductionRules_Ids, with the matching actions. - Check your endpoint management console for block events attributed to the setup process.
- Move the offending rule to audit mode temporarily, or add an exclusion, through the management console rather than locally.
- Restore the rule to block mode once the installation is complete.
Change these centrally, not on the endpoint. A local change is overwritten at the next policy refresh and you will not know why it stopped working.
A profile management rule is hiding an Office executable
You have this one if You have 30010-45, the estate uses FSLogix, and closing the dialog produces a second message ending in 0-2031 (17004).
- Run
"C:\Program Files\FSLogix\Apps\frx.exe" list-rules. - Look for rules ending in
-> [Hide]against Office executables. - Remove those rules, uninstall Office, restart the device, and reinstall Microsoft 365 Apps.
Application control is refusing to run the installer
You have this one if The installer will not start at all, or dies immediately, and a denial appears in the application control event log.
- Open Event Viewer and look under Applications and Services Logs for your application control product’s log.
- Confirm the denial names the Office setup executable.
- Add a publisher rule permitting Microsoft-signed Office setup binaries rather than a path rule, which is easier to abuse later.
A gateway is interfering with the download
You have this one if Several machines behind one gateway fail identically, and a machine on a different network installs cleanly.
- Turn the browser proxy off as a test, which is one of Microsoft’s documented steps for this family, and retry.
- Ask for the Office content and configuration hostnames to be exempted from TLS inspection, download scanning and any file size limit.
- Where the gateway cannot be changed quickly, download the build with the Office Deployment Tool from a network that works and install from that local copy.
Full reference
Documented and undocumented, code by code
| Code | What Microsoft publishes |
|---|---|
30204-44 |
Nothing |
30182-44 |
Nothing |
30145-4 |
A page for error code 30145 showing this variant. No cause given; the remedies are restart, Online Repair, then uninstall and reinstall |
30010-45 |
FSLogix is set to hide Officeclicktorun.exe or another Office executable |
30180-4 |
Anti-virus software, firewall, proxy settings or the connection preventing the install |
30175-11 |
A page for this code. No cause given; the remedy is the uninstall troubleshooter followed by a reinstall |
Where to look for the blocker
| Where | What tells you it is the culprit |
|---|---|
| Windows Security protection history | A quarantine or block entry timed to the failure |
| Third-party antivirus quarantine | The installer or a temp file listed as removed or blocked |
Get-MpPreference attack surface reduction rules |
A rule enabled in block mode covering process creation or script behaviour |
| AppLocker or application control event logs | A denial event for the setup executable |
frx.exe list-rules |
An FSLogix rule hiding an Office executable |
| The web gateway log | A block, a scan timeout, or a size limit on the Office content hosts |
| Another machine on a different network | Success there points at the network rather than the endpoint |
Microsoft’s documented remedies for 30180-4
- Use the Microsoft 365 offline installer, which may bypass potential proxy, firewall, antivirus or internet connection issues.
- Use a wired connection to the internet and try installing again.
- If you are installing at work or school, try from a different location – the network may be limited in a way that will not allow Office to install.
- Turn the proxy settings off in Microsoft Edge before installing.
- Turn antivirus off temporarily, following the manufacturer’s instructions.
- Turn the firewall off temporarily.
Suspending antivirus or the firewall is a diagnostic step, not a fix. Do it only on a machine you control, on a network you trust, only for the length of the installation, and turn it back on immediately afterwards. Never leave a broad permanent exclusion in place because it made one installation work – and if the machine is managed, ask the owner of the policy rather than working around it locally.
Exclusions, and how to remove them again
| Command | What it does |
|---|---|
Add-MpPreference -ExclusionPath "<path>" |
Adds a Defender path exclusion |
Remove-MpPreference -ExclusionPath "<path>" |
Removes it again once the install is done |
Get-MpPreference |
Shows current preferences, including exclusions and attack surface reduction rules |
Get-MpComputerStatus |
Confirms real-time protection is enabled again |
Unblock-File -Path <installer> |
Clears the downloaded-from-the-internet mark on a copied installer |
When the security product is not the answer
If the logs show nothing at the time of the failure, stop assuming a blocker and read the documented remedies for the codes that have them. Two of the six here are answered by a repair or a clean reinstall, one by an FSLogix rule change, and one by the offline installer. Working through those is faster than negotiating an exclusion for a product that was not involved.
If you cannot change the policy
- Take the block event to whoever owns the policy as evidence. A named rule and a timestamp gets a decision; “antivirus might be blocking it” does not.
- Pre-download the build on a permitted machine with the Office Deployment Tool and install from that copy, which removes several of the blocked operations.
- Ask for a publisher-based allow rule for Microsoft-signed Office setup binaries rather than a path exclusion.
- If it is a gateway scanning limit, ask for the Office content hosts to be exempted from the size cap specifically, rather than for inspection to be turned off.
- Record whatever exception is granted, with an expiry, so it is not still there in three years with nobody able to say why.
Every code this article covers
| Code | What it points at | Source |
|---|---|---|
30204-44 |
Seen when an Office install is interrupted. Microsoft publishes no page for this suffix | not published by the vendor |
30182-44 |
Seen during Office setup. Microsoft publishes no page for this suffix | not published by the vendor |
30145-4 |
Microsoft publishes a page for error code 30145 showing this variant. It states no cause; the remedies are restart, Online Repair, then uninstall and reinstall | Microsoft Support |
30010-45 |
FSLogix is set to hide Officeclicktorun.exe or another Office executable | Microsoft Learn |
30180-4 |
Microsoft: you might see this error if your anti-virus software, firewall, proxy settings, or connection prevent you from installing Office | Microsoft Support |
30175-11 |
Microsoft publishes a page for this code. It states no cause; the documented remedy is the uninstall troubleshooter followed by a reinstall | Microsoft Support |
Confirm the fix worked
- Open Word and confirm it starts without a setup or repair prompt.
- Confirm real-time protection is enabled again:
Get-MpComputerStatusin PowerShell. - Confirm any temporary exclusion has been removed: check the exclusion list in
Get-MpPreference. - Confirm the firewall and any browser proxy setting you changed have been put back.
- Run an update check from File, Account, Update Options, to prove the content path still works with protection restored.
Questions people ask about this
Does this mean the installer is infected?
Almost never, if you downloaded it from Microsoft. Security products flag installer behaviour – writing to system folders, registering services, spawning processes – as much as file content. Re-download from Microsoft rather than trusting a copy of unknown origin.
Does the 44 or 45 on the end mean it was blocked?
No. That rule is invented and the documentation contradicts it: 30010-45 is published as FSLogix hiding an Office executable, which is not a security block at all. Confirm interference from the security product’s own log.
Should I leave the exclusions in place afterwards?
No. Remove any temporary exclusion once the install is done. A permanent exclusion on the temp folder is a meaningful weakness and Office does not need it to run.
We use FSLogix. Could that be it?
Yes, and it is worth checking early. Microsoft documents 30010-45 as FSLogix being set to hide an Office executable, with frx.exe list-rules as the diagnostic. That one is a rule change, not an antivirus exclusion.
Is there anything to buy here?
No. This is a security or network configuration issue on the machine or the network. No Office licence or subscription changes it.
