Unable to Run from Current Location. Please change portable execution location.

[dalgza]

I'm running Enpass portable on my M1 mac. I keep getting this error when I open the app, "Unable to Run from Current Location. Please change portable execution location."

Haven't been able to figure out if it's a problem with M1 or something I'm doing wrong.

Thanks.

[Abhishek Dewan]

Hi @dalgza

Welcome to the Enpass Forums!

Enpass portable provides the assistance to carry all your passwords in the USB drive along with credit cards, bank accounts, ID cards, and other life-important credentials. Could you please confirm the location where you have set up your Enpass Portable File? I would also recommend checking out our user guide for Enpass portable and making sure that it is set up correctly. If the issue persists, then I will require some additional information. Please share the below details with me and I'll get it investigated for you -

1. The version of the Enpass Portable app and OS you are using.
2. A screenshot of the error occurring would be helpful.
3. Are you facing this issue on any other device as well?

[Dorian]

Hi, I have exactly the same problem.  Unfortunately, abhishek-dewan's answer isn't really helpful.  No matter where I start Enpass Portable (latest version) from, the said message always comes up. If there is already a defined error message like this, the support should know which requirements have to be met regarding the location.  To abhishek-dewan's questions:

1. MacMini with Intel CPU with MacOS 10.15.7

2. Why?  isn't the exact error message sufficient?  

3. No, I only have a Mac.

Best Regards

Dorian

[Abhishek Dewan]

Hi @Dorian

Welcome to the Enpass Community.

I appreciate you sharing the details with me and have forwarded them to our dedicated team for testing purposes. As soon as they update me on this matter, I will be sure to notify you on this forum. Thanks for your patience in the meantime. 

#SI-2918

[Abhishek Dewan]

Hi @Dorian

We were able to replicate this issue on our end. Our dedicated development is now working on fixing the bug and a patch addressing this issue will be released in the future versions of Enpass. We appreciate your patience in the meantime.