If Windows or your antivirus blocks Effigy
What Windows, your browser or an antivirus program may show when you download, install or start Effigy, and how to continue if you choose to.
If Setup says it couldn't finish (E-1728)
"Effigy Setup couldn't finish. Please try again. (Error E-1728)" means that Setup downloaded the Effigy installer, checked it and saved it, and Windows then did not start it. Trying again gives the same result until the cause is dealt with.
Smart App Control. Smart App Control is a Windows 11 feature that only lets apps run that it already recognises. Effigy is new, so Smart App Control can block Effigy's installer. Setup then shows E-1728, and its log holds the line "An Application Control policy has blocked this file".
- To see whether it is on, open Windows Security, choose App & browser control, then Smart App Control settings. It shows On, Evaluation or Off.
- Smart App Control has no setting for a single app.
- It can be turned off in the same place. While it is off, it does not check apps and does not tell you about apps it does not recognise.
- Whether it can be turned on again depends on your version of Windows. Microsoft's Smart App Control page says that recent Windows updates allow turning it on again without a clean installation; Microsoft's Windows Security page says that some PCs need a reset or a reinstall of Windows for that. Read Microsoft's page about Smart App Control before you decide.
- Whether to turn it off is your choice.
- On a work or school PC, a policy set by its administrator can block the installer in the same way.
Antivirus. If Smart App Control is not On, look in Windows Security under Protection history, and in the quarantine of any other antivirus program, for a block from a moment ago. Allow or restore the file, then run Setup again.
The exact reason is in the file %LOCALAPPDATA%\Effigy\logs\setup.log (paste that into the address bar of File Explorer). You can send us that file on Discord.
When you download or run the installer
Windows and some browsers show a warning for apps they do not recognise. Effigy is new, so you may see one.
- Your browser may hold the download back or say the file is not commonly downloaded. To continue, choose to keep the file.
- When you start the installer, Windows may show "Windows protected your PC" with an unknown publisher. To continue, choose More info, then Run anyway.
- Do this only for the installer you downloaded from the Download page of this site.
The question the installer asks
The installer asks one question: "Allow Windows Security exceptions for the specific Effigy app files installed in Program Files?"
- Yes adds exceptions only for those Effigy files. That is one file, the Effigy program in
C:\Program Files\Effigy. Windows Security keeps scanning everything else on your PC, including your downloads and personal files. - No installs Effigy without them. The exceptions are optional.
- After a Yes, Effigy keeps the exceptions up to date when it updates, and removes the ones it added when you uninstall Effigy.
If you chose No and want the exceptions later
- Press the Windows key + R.
- Paste this line and press Enter:
"C:\Program Files\Effigy\Effigy.exe" fix - Effigy asks "Fix Effigy's app settings?" and says that only the specific Effigy app files in Program Files will receive exceptions. Choose Yes. Windows may ask for administrator permission once.
If you chose Yes and Effigy later says "Some Effigy app settings need attention", choose Fix in that message.
Adding the exception by hand in Windows Security
- Open Windows Security from the Start menu.
- Choose Virus & threat protection, then Manage settings under "Virus & threat protection settings".
- Under Exclusions, choose Add or remove exclusions, then Add an exclusion and File.
- Select
C:\Program Files\Effigy\releases\, the folder with the highest number, thenbin\effigy-port-launcher.exe.
This is the same single file the installer would add. Do not exclude a whole folder or drive; Effigy does not need it. The number in the path changes when Effigy updates, so an exception added by hand has to be added again after an update. The installer's own option does that for you.
Other antivirus programs
Effigy can add exceptions to Windows Security only. In another antivirus program, allow the same file yourself; its settings usually call this an exception, an exclusion or an allowed app. If it moved an Effigy file to quarantine, restore the file there and allow it, then download Effigy from this site and run the installer again.
What you see when Effigy is blocked after installing
- Effigy does not open when you start it.
- E-1753, "This Effigy installation is incomplete or damaged": a program file is missing. Restore or allow it as above, then install Effigy again.
- E-1750, E-1752 or E-1754: Effigy could not download its startup files, they arrived damaged, or starting took too long. Check that your antivirus, firewall or VPN does not block Effigy or change its downloads.
- E-1912, E-1918 or E-1926: the secure sign-in window could not be downloaded or opened. Allow Effigy in your security software, then try again.
Other codes from Effigy Setup
- E-1727 or E-1735: Setup could not prepare its folder or save the installer on this PC. Look for a block in Protection history or your antivirus as described for E-1728, allow it, then run Setup again.
- E-1726: there is not enough free disk space. Free up some space and run Setup again.
- E-1722: Setup could not connect to the internet. Check your connection.
- E-1723 or E-1730: the Effigy download service could not be reached or cannot provide the download at that moment. Try again in a few minutes.
- E-1729: Setup could not open a secure connection. Check your connection; a security program or network filter that inspects secure connections can cause this.
- E-1724 or E-1725: the downloaded files could not be verified, so nothing was installed. Try again later.
- E-1721: an earlier removal of Effigy finishes when Windows restarts. Restart Windows, then run Setup again.
- E-1733 or E-1734: Setup could not start or finish the download for another reason. Try again; if it keeps happening, send us
setup.log.
Questions? Use Report a problem or ask us on Discord, and include the code you see.