It seems as though Visual Studio still thinks that this setting should be flagged, or it is copying a cached version of the file from somewhere which hasn't had the setting removed. Windows 10 comes with Encrypted File System (EFS) which allows users to encrypt their data in a particular folder or drive. The option of encryption will no longer be greyed.

I have tried publishing to another folder, but alas the new file still get created with encrypted contents setting. Go back to the folder which you want to encrypt and click the PropertiesAdvancedAdvance Attribute option.

I have completely re-created each file by pasting the contents in to a new file, but still when they are copied across the flag is reset. All files are deleted prior to commencing the publish. The source files do not have the flag set, only the published files. However, when I re-publish using Visual Studio 2010, the published files have the setting flagged again. Ok, so I right-click -> properties -> Advanced and unchecked the 'encrypt contents to secure data' setting. To encrypt a folder full of files or a single file, use these steps: Launch File Explorer and navigate to the file or folder you want to encrypt. I found the problem to be the 'encrypt contents to secure data' on each of the files.

My website had problems loading an image, css file and a javascript file downloaded as a package from 'Superfish'.

Encrypt contents to secure data