Skip to content

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

Your vault is empty.

Free Fix 1316

AVG won’t uninstall: error 1316, 1638 and the endless repair loop explained

10 min read Updated October 5, 2026 Antivirus & Endpoint Security

Fix it now

These are Windows Installer’s own numbers, and they are worth reading literally: 1316 is a network error reading a named file, 1638 is another version already installed, 1605 is an action attempted against a product Windows Installer does not consider installed, and 2755 is a server returning an unexpected error for the package. The way out is to stop asking Windows Installer.

If you need the real failure rather than the wrapper, run the installer with verbose logging

msiexec /i package.msi /L*v %temp%\avg-install.log
  1. Download AVG Clear from AVG’s website and save it locally before you start.
  2. If AVG still opens, turn off its self-protection from its own settings, so the removal is not blocked. The setting is inside the product rather than in Windows.
  3. Restart into Safe Mode: Windows Recovery Environment, Troubleshoot, Advanced options, Startup Settings, Restart, then press 4.
  4. Run AVG Clear. It removes the product, its services and its drivers directly rather than through Windows Installer.
  5. Restart into normal Windows and confirm no AVG entry remains under Settings, then Apps, then Installed apps.
  6. If a dead entry is still listed on Windows 10, run Microsoft’s Program Install and Uninstall troubleshooter, which clears broken installer records.

Microsoft presents that troubleshooter for Windows 10 and points Windows 11 users at the built-in repair and reset options instead. Do not edit installer records by hand until the supported tools are exhausted.

If AVG is gone and a reinstall runs cleanly you can stop here. If the entry keeps coming back, the next section explains why and what is putting it there.

Why it happens

Windows Installer keeps a copy of every package it installs, cached under C:\Windows\Installer with a generated name, and the product’s registry record points at that copy. Uninstalling reads the record, finds the cached package, and uses it to reverse the installation. If the record points at something Windows Installer cannot read, none of that can happen and you get one of these numbers instead.

Read the numbers precisely, because the published text is narrower than the folklore. 1316 is published as “A network error occurred while attempting to read from the file”, followed by the file name – which is why a package on a share, a redirected installer cache or a disconnected drive is worth checking before you conclude the cache is simply missing. 2755 is “Server returned unexpected error attempting to install package”, which points at the source rather than at the local service.

The other two are about state rather than files. 1638 is ERROR_PRODUCT_VERSION: another version of this product is already installed and this one cannot continue. 1605 is ERROR_UNKNOWN_PRODUCT: the action is only valid for products that are currently installed, which is what you get when a record has been half removed and no longer describes anything real.

Security products make all of this worse in one specific way. Their self-protection is designed to prevent unauthorised removal and does not distinguish between a malicious removal and the legitimate one you started yourself. That is why vendor removal tools exist, why they bypass Windows Installer entirely, and why Safe Mode – where most third-party filter drivers do not load – is the state in which they win.

The cached package cannot be read

You have this one if The failure names a file under the Windows Installer cache folder, or the message is the 1316 network-error text.

  1. Check the obvious version of “network error” first: an installer cache redirected to a share, a disconnected mapped drive, or a source path that no longer exists.
  2. Do not try to recreate the cached file. You cannot generate the exact package Windows Installer expects.
  3. Use AVG Clear instead, which removes the product directly rather than through Windows Installer.
  4. Afterwards, clear any orphaned entry with Microsoft’s Program Install and Uninstall troubleshooter on Windows 10.

Self-protection is blocking the removal

You have this one if The removal appears to run and the product is still there afterwards, with no clear error.

  1. Open AVG’s own settings and turn off self-protection. It is a product setting rather than a Windows one.
  2. Restart into Safe Mode.
  3. Run AVG Clear.
  4. Restart into normal Windows and verify the AVG folders and services are gone.

If AVG will not open at all, Safe Mode alone is usually enough, because the self-protection driver does not load there.

A stale product record is left behind

You have this one if AVG is gone from disk, Installed apps still lists it, and a reinstall reports 1638 – another version already installed.

  1. On Windows 10, run Microsoft’s Program Install and Uninstall troubleshooter and choose the uninstall scenario; it removes broken records safely.
  2. On Windows 11, Microsoft points at the built-in repair and reset options instead of that tool.
  3. Only if the supported tools fail, and only after exporting the key, remove the orphaned entry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall.
  4. Restart, then reinstall from the full offline installer.

Editing installer records by hand can make a future upgrade fail in ways that are much harder to diagnose than this. Exhaust the supported tools first.

Two builds from the same vendor family are registered

You have this one if Installed apps shows more than one AVG or Avast entry, or a version you do not recognise.

  1. Run each vendor’s own removal tool in turn, in Safe Mode, restarting between them.
  2. Confirm no service from either product remains in services.msc.
  3. Confirm the vendor folders under Program Files and ProgramData are gone.
  4. Only then install the single product you intend to keep.

Something is putting it back

You have this one if The product returns after a restart or overnight with nobody reinstalling it.

  1. Open Task Scheduler and look for tasks belonging to the vendor; disable any that run an installer.
  2. Check for a management agent or software deployment tool with the product assigned as a required install.
  3. On a work machine, ask whoever manages it before removing anything, because the reinstall may be deliberate.
  4. Remove the assignment at the management tool before removing the product locally.

Full reference

What each number is published as

Code Constant Published text
1316 – A network error occurred while attempting to read from the file, followed by the file name
1605 ERROR_UNKNOWN_PRODUCT This action is only valid for products that are currently installed
1638 ERROR_PRODUCT_VERSION Another version of this product is already installed. Installation of this version can’t continue
2755 – Server returned unexpected error attempting to install package

Tools and commands

Item What it does
C:\Windows\Installer Where Windows Installer caches package copies used for repair and removal
msiexec /x {product-code} Requests removal of a product by its installer product code
msiexec /i package.msi /L*v log.txt Runs an installer with verbose logging so the real failure becomes visible
Program Install and Uninstall troubleshooter Microsoft’s tool for clearing corrupted registry keys and incomplete uninstall data, published for Windows 10
AVG Clear AVG’s own removal tool, which deletes all files associated with the product, bypassing Windows Installer
services.msc Confirms whether the product’s services are still registered
fltmc filters Lists loaded file system filter drivers, including leftovers

Everything below the supported tools either removes software or touches the registry. Take a restore point first and export any key before you change it. A wrong edit under the installer or services keys is much harder to undo than the problem you started with.

Reading the verbose log

  1. Run the installer with /L*v and a path you know is writeable, such as one under %temp%.
  2. Open the log and search for “Return value 3”, which marks the action that actually failed.
  3. Read the twenty or so lines above it. The real error is usually there in plain text, and the number on screen is a wrapper around it.
  4. If the log itself cannot be created, that is error 1622 and the problem is the path or its permissions rather than the package.
  5. If the log names a file under the installer cache, stop and go to the removal tool. Recreating that file is not possible.

When the entry keeps coming back

A product that reappears after a restart is not a removal failure. Something is reinstalling it, and the candidates are short: a scheduled task belonging to the vendor, a software deployment or management tool with the product assigned as required, or a bundled installer from another application. Task Scheduler and your management console will show you which within a couple of minutes, and removing the local copy without removing the assignment guarantees a repeat visit.

On a work machine, treat the reinstall as deliberate until someone tells you otherwise. Endpoint software is frequently deployed as a required application precisely so that people cannot remove it, and quietly winning that argument on one machine is a good way to create a gap in someone’s compliance reporting.

Every code this article covers

Code What it points at Source
1316 A network error occurred while attempting to read from the named file Microsoft Learn
1638 ERROR_PRODUCT_VERSION: another version of this product is already installed, and this installation cannot continue Microsoft Learn
1605 ERROR_UNKNOWN_PRODUCT: this action is only valid for products that are currently installed Microsoft Learn
2755 Server returned unexpected error attempting to install package Microsoft Learn

Confirm the fix worked

  1. No AVG entry remains under Settings, then Apps, then Installed apps.
  2. No AVG service is listed in services.msc and the program folders are gone.
  3. fltmc filters shows no AVG filter still loaded.
  4. Windows Security shows an active antivirus provider.
  5. If you are reinstalling, the installer runs to completion without reporting an existing version.

Questions people ask about this

Do I need to pay for anything to get AVG off this machine?

No. AVG Clear is free from AVG and Microsoft’s install and uninstall troubleshooter is free from Microsoft. Any site charging for a removal utility for this is selling you something you do not need.

Does 1316 mean the cached installer is missing?

That is the common reading, and it is often what is happening, but the published text is narrower: a network error occurred while attempting to read from the named file. Check the mundane version first – a redirected installer cache, a disconnected drive, a source path that no longer exists.

Will removing AVG leave me unprotected?

Briefly. Microsoft documents that Defender re-enables itself automatically when a third-party product stops providing real-time protection. Check Windows Security afterwards and confirm rather than assuming.

Does this cancel my AVG subscription?

No. The subscription is held against your AVG account or activation code rather than against the installation, and you can reapply it after reinstalling.

Can I skip Safe Mode?

Try the removal tool in normal Windows with self-protection off first. If it fails, or the product survives, Safe Mode is the reliable route, because most third-party filter drivers do not load there.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

Free Fix McAfee will not uninstall: error 1712 and what the MCPR tool really does License Error ESET update failed with error 0x1106: modules and detection engine stall License Error McAfee says your protection has expired even though you paid for a renewal License Error McAfee real-time scanning will not turn on: service errors 1068 and 1069
← Back to Knowledge Base