Announcement

Collapse
No announcement yet.

Warning 7250: Warning: Failed to write permissions manifest to setup w/ Avast AV.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Warning 7250: Warning: Failed to write permissions manifest to setup w/ Avast AV.

    When I have Avast Anti-Virus running, almost every project I write will give me the this warning: Warning 7250: Warning: Failed to write permissions manifest to setup.

    If I disable Avast for 10 minutes or longer, I no longer receive this error. My project is using the Require Administrator (default) setting. This only started happening in the last 4 or 5 months, so I believe an Avast updated caused this.

    Does anyone know if I need to add an exception into Avast so I don't have to turn it off every time I want to Build my projects.

    And I guess I don't know too much about what the "write manifest to setup" function really does for me.

    Thx, MikeT

  • #2
    In Avast General Settings dialog, locate the Exclusions section. Expand it, and add the output folder - the folder where you are creating / saving the setup. Click the Add button.

    Click image for larger version

Name:	SCRN-2015-04-09-01.png
Views:	1
Size:	28.1 KB
ID:	284294

    You may also add the folder used for the temporary build files to this exclusion list, which should prevent compression errors during the build process. You can find the location of these files in Setup Factory > Edit > Preferences > Environment > Folders > Temporary build files.

    Click image for larger version

Name:	SCRN-2015-04-09-03.png
Views:	1
Size:	17.2 KB
ID:	284296

    Just copy the contents of this field and add it to the exclusions:

    Click image for larger version

Name:	SCRN-2015-04-09-04.png
Views:	1
Size:	30.6 KB
ID:	284297

    Now, assuming that you have DeepScreen enabled, add the SUFDesign.exe of your Setup Factory installation to the exclusions. Use the Browse button, locate your file, then click Add.

    Click image for larger version

Name:	SCRN-2015-04-09-02.png
Views:	1
Size:	28.2 KB
ID:	284295

    Repeat this for Hardened Mode, if you have this option enabled in your settings.

    Finally, try to build the setup again. With these exclusions in place, Avast stopped interfering with the build process in my test environment (a VM with Windows 7 and evaluation versions for both Setup Factory and Avast Internet Security 2015). The same method explained here should help with other releases and anti-virus products from different vendors as well.

    Ulrich
    Last edited by Ulrich; 04-08-2015, 11:23 PM.

    Comment

    Working...
    X