Product: Avast Update Helper — Error 1316. The Specified Account Already Exists.

Some Windows users who have been using Avast Antivirus complain that they frequently notice 1316 Errors when they check their Event Viewer logs (every hour or so). Although the problem doesn’t show up outside of Event Viewer, some afflicted customers worry that they are leaving their system vulnerable to security problems because of this problem.

If you haven’t updated your Avast application in a while, there’s a good possibility the problem stems from a previous flaw that affected both Avast Free and Avast Security. Installing the most recent version of Avast will enable you to benefit from the repair, which was made by the company at the start of 2019.

Product: Avast Update Helper -- Error 1316. The Specified Account Already Exists.

It’s likely that you are dealing with a corruption that can’t be fixed ordinarily if the issue first appeared after a system outage or after a failed programme upgrade. If this situation applies, you can troubleshoot and repair the application using the built-in repair feature.

Two other kinds of programme conflicts, nevertheless, could also result in these kinds of event watchers. The first one entails utilising Avast Security Browser along with the built-in AV programme (Microsoft Defender). When Nvidia ShadowPlay doesn’t release the Registry Keys before quitting, it may result in the second potential issue. You can resolve the problem in both of these scenarios by removing the incompatible application.


Method 1: Install the Most Recent Version of Avast

As it turns out, a quality-of-life upgrade that Avast released in 2018 caused a spike in Avast Helper Error 1316 and increased the memory and CPU use of Avast Free and Avast Security. Many of the impacted users stated that the Event Viewer would become overrun with events indicating the Error 1316 whenever usage increased.

Several afflicted users reported that they were able to fix the problem by making Avast’s installation update to the most recent version.

Here is a brief tutorial for updating Avast (Avast Free or Avast Security) to the most recent build:

  1. To begin, launch the Avast Antivirus programme and select the Menu icon (top-right corner).
  2. Next, select Settings from the context menu that has just displayed.
  3. Once you have successfully accessed the Settings menu item, select the General tab and then the Update subtab.
  4. Click the Check for Updates button located inside the Update sub-tab and wait for the process to be finished. The application will automatically download and install the most recent version.
  5. You will be prompted to restart after the procedure is finished. Accept the prompt when it appears, then hold off until the next startup process is finished.
  6. Press the Windows key and R to reopen Event Viewer. To launch the Event Viewer, enter “eventvwr.msc” into the text box and click Enter.
  7. Check to see whether the 1316 Problem Pointing to Avast Helper error is still occurring.

Method 2: Using the Integrated Repair Feature

It’s likely that you’re getting this error as a result of a partially corrupted application installation if you’ve only recently started to experience this problem after an unplanned system interruption or after a failed application upgrade.

Many impacted users were able to resolve the problem by utilising the built-in repair feature present in all Avast products. It can be launched immediately from the application and is quite successful in resolving the majority of local problems that lead to the Avast Helper Error 1316.

Here is a simple tutorial on how to use the built-in troubleshooter to fix the Avast AV programme:

  1. Click the Action Menu in your Avast installation (top-right hand corner). Next, select Settings from the context menu that has just displayed.
  2. From the list of sub-menu items in the Settings menu, choose the General tab and then click Troubleshooting.
  3. Click Repair app after you’ve entered the Troubleshooting menu and have scrolled down to the Still experiencing issues? section.
  4. After answering “Yes” to the confirmation question, wait for the preliminary scan to be finished.
  5. You will receive a list of the potential problems that were found at the conclusion of this procedure. Click Resolve all correct the problems to address every case that has been found.
  6. Restart your computer after the procedure is finished to see if the problem has been solved.

Method 3: Remove Avast Secure Browser

Keep in mind that Avast Secure Browser is one of the most common offenders that is known to cause the regular Avast Helper Error 1316 entries in Event Viewer if you use it. As it turns out, the problem is most likely a conflict between Avast Secure Browser and Windows Defender, the default security programme for Windows 10, or another third-party antivirus.

The majority of customers reporting this issue claim that removing the Avast Secure browser was all that was necessary to resolve it. Consider Brave browser if you’re seeking for a solid substitute that doesn’t interfere with Windows Defender:

Here is a step-by-step instruction on how to remove Avast Secure Browser:

  1. To bring up the Run dialogue box, press Windows key + R. Enter “appwiz.cpl” into the text field to launch the Programs and Features menu.
  2. Find your Avast Secure Browser installation by scrolling through the list of installed Programs and Files programmes once you’ve entered the Programs and Features menu. After locating it, perform a right-click and select Uninstall from the context menu.
  3. After completing the uninstallation process, restart your computer and check to see if the problem has been fixed when it starts up again.

Method 4: ShadowPlay uninstalling (or similar application)

If you utilise ShadowPlay (or the ShadowPlay features bundled with Nvidia Experience) and an AVAST product, there’s a good probability that the event was brought on by an app (ShadowPlay) that failed to release the Registry Keys before quitting.

This specific problem may occasionally arise when a background-running programme like ShadowPlay doesn’t release its Registry keys after a user logs off. As a result of this behaviour, Windows will be forced to unload the registry.

Other than the rare instances where recent configuration changes won’t be preserved, this issue shouldn’t have any other significant effects on users (but this happens very rarely).

There are no further effects (apart from repeated entries in the Event Viewer), but you can stop fresh events from happening by uninstalling ShadowPlay as usual.

Here is a little explanation on how to accomplish it:

  1. To bring up the Run dialogue box, press Windows key + R. To access the Programs and Features menu, type “appwiz.cpl” and press Enter.
  2. After selecting ShadowPlay with the right click from the list of installed apps in the Programs and Features menu, pick Uninstall from the context menu.
  3. Once the uninstallation is complete, restart your computer by following the on-screen instructions in the uninstallation window.
  4. Check to determine if the problem has been fixed after the subsequent starting sequence is finished.