McAfee install error 76567: setup will not finish on this Windows PC

Fix it now

Setup gave up and undid what it had done. McAfee publishes no meaning for 76567 or 76582, but the Windows Installer numbers that appear alongside are documented and they point somewhere quite specific. In practice the commonest cause is another security product, live or half-removed.

sfc /scannow
chkdsk C: /scan

1. Uninstall any other antivirus or internet security suite with that vendor’s own removal tool rather than only the entry in Apps and Features, then restart. Bitdefender puts the rule bluntly in its own documentation: never have more than one security solution installed on your computer at the same time.
2. Run McAfee’s own removal tool, MCPR, to clear remnants of any previous McAfee installation, and restart when it asks.
3. Open Windows Security and confirm under Virus & threat protection that no third-party antivirus other than the one you intend to keep is registered.
4. Download a fresh installer from your McAfee account rather than reusing the file that already failed, and run it as an administrator.
5. If the failure names 2203, check that %temp% exists, is writable by your account and has room. If it names 1614, the operation is targeting a product Windows records as uninstalled – clear the leftover entry rather than retrying.

Do not remove Microsoft Defender first, and do not try. Microsoft documents that on a client with a non-Microsoft antivirus registered, Defender moves into disabled mode by itself and re-enables automatically when that product is uninstalled or stops providing real-time protection.

If setup completes and the app opens without a repair prompt, you are done. If it fails at the same point, the next section explains which stage each number belongs to.

Why it happens

Installing a security suite means registering a file system filter driver and usually a network filter as well. Windows will load more than one, but the products themselves are far less tolerant: a suite that detects a competing real-time scanner will often refuse to continue rather than produce an unstable machine. When it refuses, it rolls back, and you get a setup failure with no explanation on screen.

Uninstalling the other product through Apps and Features is frequently not enough. Filter drivers, services and registry entries survive an incomplete removal, and a new installer cannot distinguish those from a live product. That is why every major vendor publishes a dedicated removal utility – Bitdefender even maintains a page that links to the tools of Norton, McAfee, Avast, AVG, Avira, ESET, Kaspersky, Sophos, Trend Micro and the rest – and using the right one is the difference between a five-minute job and an afternoon.

McAfee publishes no meaning for 76567 or 76582, so nothing you read that defines them precisely is working from a source. What is documented is the second set of numbers, which come from Windows Installer and point at the engine rather than at a conflict: a database file that could not be opened, a file the package expected and did not find, or an operation aimed at a product Windows records as uninstalled.

Full reference

Which numbers are documented and which are not

That split is the whole diagnostic. The five-digit numbers tell you the installer gave up; the four-digit ones tell you where. If your failure shows only a five-digit number, work the conflict angle. If it shows one of the Windows Installer codes, work that instead – they are far more specific than anything McAfee has published.

Removing the other product properly

1. Uninstall it normally first, from Apps and Features, and restart.
2. Then run that vendor’s own removal tool. Bitdefender’s index of vendor uninstall tools is a convenient list of where to find them for Windows and macOS.
3. Restart again, even if the tool does not ask.
4. In an elevated Command Prompt, run fltmc filters and look for filter drivers belonging to the removed product. Do not unload anything by hand – use it to decide whether the removal actually finished.
5. Only then run the McAfee installer, as an administrator, from a freshly downloaded file.

What Defender is doing while all this happens

Nothing you need to manage. Microsoft documents that on a Windows client with a non-Microsoft antivirus installed and no Defender for Endpoint onboarding, Microsoft Defender Antivirus goes into disabled mode automatically, and that it is re-enabled automatically if that product expires, is uninstalled or otherwise stops providing real-time protection. So during a failed installation the machine falls back to Defender rather than to nothing, and there is no step here that requires disabling it.

Checks before the next attempt

• Let any pending Windows updates finish and restart. They hold Windows Installer, and a pending operation blocks the next one.
• Confirm %temp% is writable and has space, which is what 2203 is usually about.
• Confirm the system volume is not nearly full.
• Read the MsiInstaller entries in the Application log in Event Viewer around the time of the failure – they usually name the file or component involved.
• On a managed laptop, expect driver installation and administrator rights to be restricted. If the machine belongs to an employer, the installation goes through whoever manages it.

Why this keeps happening on the same machines

Two suites end up on one PC for a reason, and it is usually a licensing one: a subscription lapsed and something else was installed in a hurry, or a preinstalled trial was never cleared out. Nothing in this article prevents the next occurrence. Deciding which product you are keeping, licensing it for every device you own, and removing the rest properly does.

Every code this article covers

Confirm the fix worked

1. Setup completes and the McAfee app opens without a repair prompt.
2. Windows Security under Virus & threat protection shows one antivirus, not two.
3. Real-time scanning reports as on and an update completes.
4. Apps and Features shows no leftover entry from the product you removed.
5. fltmc filters no longer lists filter drivers belonging to the removed suite.

Questions people ask about this