Forum Replies Created

Viewing 15 posts - 481 through 495 (of 1,759 total)
  • Author
    Posts
  • in reply to: AxCrypt Hangs on Samsung Note 5 Android #8452

    Svante
    Spectator

    Hello Gene,

    We have just released a new beta for the upcoming release. If you are not already a beta tester, sign up here: https://play.google.com/apps/testing/net.axcrypt.axcrypt2x . That will give you access to beta versions through the Play store.

    in reply to: Not able to import AxCrypt ID #8450

    Svante
    Spectator

    Hello Ricky,

    We’ll investigate – but please understand that this is not of the highest priority, because you’re not really supposed to be using that function. We do all that automatically via our server in all normal cases.

    It’s there partly because of historical reasons, and also as a last resort for non-Internet-connected devices. But it’s used very seldom.

    Do you really have a situation where you cannot let AxCrypt do this work for you automatically?

    in reply to: Erreur Descellement #8446

    Svante
    Spectator

    Hello Cedric,

    Happy to hear it! But, in the future don’t forget to keep backups of your important data – encrypted, or not!

    in reply to: Erreur Descellement #8444

    Svante
    Spectator

    Hello Cedric,

    The messsage indicates that the file has been tampered with or improperly saved.

    It’s hard to say, but it sounds like you’re using the old unsupported version 1.x of AxCrypt.

    If that’s the case, you can always try to decrypt the file anyway and ignore the error. It probably won’t work, but you can try. See http://www.axantum.com/AxCrypt/Registry.html for details, it’s the TryBrokenFile setting.

    If you’re using AxCrypt 2, let us know. There’s a setting there too that you can try.

    But, in any case, backups are your protectoin against data loss for all data, encrypted or not. Think if you might not have a copy of the file somewhere.

    in reply to: The Android app does not open any of my files #8442

    Svante
    Spectator

    Hello Anonymous,

    We are looking into this, and will be releasing a new version shortly hopefully.

    in reply to: Original Icon #8435

    Svante
    Spectator

    Hello Anonymous,

    No, not really, because it’s part of what windows does. It is technically possible to use a so-called icon overlay, but it has never worked very well and requires a lot of very specific code for Windows.

    So, sorry, we don’t support that!

    in reply to: The Android app does not open any of my files #8432

    Svante
    Spectator

    Hello xavier,

    Where are they stored on the phone? What version of Android are you running, and what version of the mobile app?

    in reply to: Unexpected Error. "UTF-8" is not a support encoding name. #8430

    Svante
    Spectator

    Thank you Ned!

    Unfortunately there’s not really anything we can do about this as I understand it, since it’s the framework that is crashing on this. Then again, it’s kind of strange that this is not a bigger problem if a major product like Sophos is defective in this way. Perhaps it’s fixed and you have an old version? Or there are other factors involved. If we could control it we could of course be tolerant of this situation, even if it is non-standard. But as I see it we can’t.

    in reply to: Unexpected Error. "UTF-8" is not a support encoding name. #8422

    Svante
    Spectator

    Hello Ian,

    We investigated this error message before, and this is a message about a bad response from a request to a web server. We have checked and it’s not our server which is responding in the wrong way.

    Notice the message is “UTF-8” is not a supported encoding name. Double double quotes. What’s happening seems to be that someone is intercepting and changing the response to send an encoding with the name “UTF-8” instead of UTF-8. The encoding name should be without quotes. The error message displays the encoding name withing it’s own quotes – so there it’s double double quotes. It’s a little meta subtle so to speak, but it’s out of our control as far as we understand the issue!

    The most likely reason for this is that the user is behind some kind of firewall or other hardware or software which actually rewrites the request – and does this incorrectly. Our server is not responding with encoding name within quotes, something else is we think.

    in reply to: Can't open encrypted file with password created #8419

    Svante
    Spectator

    Hello Rosa,

    The file is encrypted using a password. That password is apparently different than the one you are signed in with. It thus does not help to enter it again, it’s already tried. That’s why the message says you’re already signed in with that password.

    I’m wondering – did you encrypt the document, or did someone send it to you?

    If someone sent it to you, they need to use the key sharing feature in order for you to be able to open it. If they do this, the file is updated to include a key for you so you can open it – but they will need to resend the file to you after adding you as a recipient. All this is explained on our web page https://forum.axcrypt.net/ .

    in reply to: Can't open encrypted file with password created #8385

    Svante
    Spectator

    Hello Rosa,

    From our logs, we can see that you downloaded AxCrypt, created an account, and set a password. Then, about 3 hours later, you signed again to the web site and among other things changed the password.

    This means there are two passwords in play. Please sign out and exit from AxCrypt, then ensure you are online, sign in again with the new password and try again. If the file still does not open, please use the original password you set when you created the account.

    in reply to: Unexpected Error! Cannot Start Application #8378

    Svante
    Spectator

    Hello Eric,

    The reason the AxCrypt upgrade had no effect (but it’s good you did anyway since we don’t support version 1 anymore), is that it’s not an AxCrypt problem.

    It’s a problem with the application (Excel) or the file association (.xls). Start by decrypting one of the files (just right-click it, and select AxCrypt decrypt) so you get the original .xls file back.

    Then double-click it to open it without the involvement of AxCrypt. Hopefully that will give you a clearer indication of what the real problem is.


    Svante
    Spectator

    Hello Todd,

    First – Please upgrade! That version is ancient. You should be seeing a red icon warning you of this. Go to https://forum.axcrypt.net/ and get the latest version,

    You should let AxCrypt clean it up with the red broom icon. You won’t confuse AxCrypt if you delete them manually – but you may lose your most recent edits, since if you have any that have not been re-encrypted, if you delete them the changes are lost.


    Svante
    Spectator

    Hello tekin,

    Please read https://forum.axcrypt.net/support/faq/#forgot-password .

    in reply to: "Get Premium!" #8328

    Svante
    Spectator

    Hello Anonymus,

    Nope, that doesn’t seem to make sense! It shouldn’t display that if you have Premium of course. Can you send a screenshot of this?

Viewing 15 posts - 481 through 495 (of 1,759 total)