Why can't the compressed and encrypted attribute be set on NTFS at the same time?

Question

Microsoft

The essence and reason for such restrictions is not entirely clear.
After all, purely theoretically, no one forbids setting the “encrypted” attribute for a ZIP or WinRAR file archive, does it?
In general, I would also like to be able to work with SPARSE encrypted files.
What other filesystems can do this directly?

Answer 1

Compression and encryption in NTFS are mutually exclusive. The reason is because encryption is applied at the expense of another EFS file system, which is, as it were, an add-on to NTFS.
prowiki.isc.upenn.edu/wiki/EFS ,_Encrypting_File_System

Answer 2

I didn't fully understand the description of the problem. I'll try to answer your question in the thread.
The command shell allows you to work with the attributes of files and folders, the attrib snap-in, there is no compression or encryption in the list of attributes. There is A - archived, but it seems not quite what you need.
You need to compress with a separate snap-in compact, and encrypt with cipher
No one bothers to make a batch file and perform the necessary actions on a directory or file. It will be team after team, but not at the same time.

Answer 3

Before encryption, information is usually compressed anyway in order to increase the entropy of the data and thereby complicate cryptanalysis.