title: NSIS Installer on Windows 10 triggers Bitdefender Ransomware detection
body: <p>I am working currently on a software which I am packing into an NSIS installer and distribute the resulting exe file. The installer must run primarily on Windows 10. Since a few days, Bitdefender added protection against ransomware. Since my installer tries to write to the <code>Documents</code> folder for the current logged in user, the installer is being blocked by Bitdefener as potentially malicious. How can I fix this? Should I not write to the <code>Documents</code> folder? Is there another appropriate folder? Can I sign my installer or is there some other method that makes this installer trustworthy for Bitdefender?</p>
  
  <p>The file which I am writing is an <code>.xlsm</code> file. While I agree that this is not the best file format to create in terms of security, this is the file format I am currently having and there is no quick way to change this.</p>