AxCrypt - File Encryption for Windows

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

Thank you so much for investigating and finding the conflict.

This has always been an issue with Shell Extensions - they require that
the Shell (Windows Explorer / Directory Opus etc) work as expected.

The problem is that Microsoft has not really documented this very well, so
it's hard both for a shell implementer and for a shell extension to know.

However, by definition, if it works with Microsoft Windows Explorer but
not with a 3rd party replacement, the 3rd party is 'wrong'...

Notwithstanding this, I'll be happy to work with GP Software to figure out
the issue. Can you possibly report this as an issue with them, giving them
my contact details, and I'll try to fix this if they provide me with
further information about the issue.

Svante

Hello Svante,

Thanks for your questions. I have now discovered that the problem arises
through interaction with GP Software Directory Opus
(http://www.gpsoft.com.au/), which is a File Manager & Explorer
replacement.

If Directory Opus is set up to replace Explorer (see screenshot in
AxCrypt.doc) then the error (see screenshot for error message) arises. If
Directory Opus is set up with "Don't replace Explorer" the error does not
arise. Any of the three "Replace" conditions in Directory Opus enables the
error.

Alternatively, if Directory Opus is set up to replace Explorer, and
AxCrypt right-click integration is not installed, then the error does not
arise. So AxCrypt right-click integration plus Directory Opus replace
Explorer is the condition that creates the error.

I hope that is clear!

AxCrypt is the subject of one message in the Directory Opus user forum, -
it is an enthusiatic recommendation, no mention of this error.

Regards,
peter

Ok.

Is it possible for you to upload a screen shot, not only of the AxCrypt
dialog, but of the Control Panel, so I can see what mode you're displaying
it in.

It's obviously something that varies between installations, as it works
perfectly on various Windows 7 installations that I have access to for
testing purposes, both 32-bit and 64-bit.

Do you have other additions that affect the workings of Windows Explorer
installed, or other software that changes the context (right-click) menu?

Svante

Yes I am running 1.7.1836.0 Beta. Yes the problem goes away if it's
uninstalled and reappears when AxCrypt is reinstalled.

Regards,
Peter

I cannot reproduce this on any version of Windows.

Are you running 1.7.1836 ?

Does the problem go away if you uninstall, and reappear if you re-install?

I can verify this issue on Windows 7 Home Premium 64 bit (Full Retail) . As
soon as I open the control panel the error message always appears.