September 18, 2018 at 08:14 #11374
J’ai maintenant cette erreur lorsque j’essaie d’ouvrir un fichier crypté :September 18, 2018 at 08:37 #11376
This is Windows telling you that AxCrypt (acting as ‘you’) does not have permissions to the folder or the file in question. This can be caused by many things, but they are not AxCrypt-related. If you have moved the disk from another Windows-computer or if you have re-installed Windows you may need to “take ownership”. If you have encrypted the files/folder also with Windows EFS (Encrypting File System) *and* moved the files or re-installed Windows, you need to decrypt them in the original Windows or using backed up recovery certificates. Use Google to find out more about the mentioned situations. It is likely you cannot copy and/or delete the file without AxCrypt directly from Windows Explorer either – thus not an AxCrypt-related issue.September 23, 2018 at 09:18 #11386
Bonjour Svante et merci.
Non, il ne s’agit pas d’EFS.
L’emplacement des fichiers cryptés n’a pas changé, il s’agit simplement de les ouvrir sous Windows 7 alors qu’ils ont été créé sous Windows 10 (dual boot).
J’ai pris le contrôle d’un fichier test (take ownership) et le message d’erreur est le même.
Pourrais-tu m’aider encore ?September 23, 2018 at 11:32 #11387
Are you really sure it’s not EFS? Can you send a screen shot of such a file in Windows Explorer? Or check properties and ensure that the “Encrypt Contents to Secure Data” is *not* checked? Note that the way EFS-files are distinguished has changed in Windows 10 – now it’s a little small padlock icon overlay, before the text of the file name was in green text.
The situation with Dual Boot you describe is a typical scenario where this will happen if it’s EFS-encrypted in Windows 10 and you then try to access them in Windows 7.September 25, 2018 at 08:43 #11434
Merci, c’était bien un problème avec EFS. Bien joué !September 25, 2018 at 12:44 #11435
Happy to hear the cause has been determined. Hopefully you have now restored functionality and solved the problem. Good luck!November 23, 2018 at 00:53 #12179
I am getting this error ant the filie is not encrypted again..Windows 10 Pro ver 1809November 23, 2018 at 00:54 #12180
I am getting this error ant the filie is not encrypted again..Windows 10 Pro ver 1809November 23, 2018 at 11:02 #12181
It seems very strange that AxCrypt tries to write files to the root of C:\ . Is the original file located there? If so, you should move it somewhere else, like your documents or desktop. Do not store and work with files in the root folder like C:\ .