NetSetMan Support

flagrange

Member

From: Lisbon and Brussels

Registered: 2022-05-15

Posts: 3

Cannot open/create script programs if Quick Access is disabled

Hello,

When going to the Scripts & Programs dialog in the profiles. one can:
- Create a new script file by clicking the Create new script filebutton in Script
- Add a Program by clicking + in the Program Section

When Windows Explorer Quick Access is disabled, the suddenly doesn't work any more, showing an error:
NetSetMan: The system cannot find the path specified. shell:::{679f85cb-0220-4080-b29b-5540cc05aab6}.

The problem indeed occures when
Computer\HKEY_CLASSES_ROOT\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder\Attributes
Computer\HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{679f85cb-0220-4080-b29b-5540cc05aab6}\ShellFolder\Attributes
are set to 0xa0600000 in order to disable Windows Explorer's rather useless Quick Access (as documented in several places like here.

This annoying because changing the above requires a log off and on from Windows. It is a bug because NetSetMan should merely open a FileOpen dialog and not care about nor validate unrelated Windows Explorer settings.

Thank you for looking into this.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,833

Re: Cannot open/create script programs if Quick Access is disabled

For security reasons, we are using a custom file dialog instead of the native one. The native dialog does not provide any customization options that we need, like disabling the context menu, which lead to a security issue in version 4.x.

For the custom file dialog we are using components that include native components into the UI. In the end it looks and feels like the native file dialog, but we have much more control over it.

Having said that, our control over the component itself is limited. We can enable or disable the quick access area and we would like to keep it on by default. You error constellation seems rather rare, because there is no native way to disable it.

It might be possible for us to first check for the mentioned registry value and then enable or disable the quick access area. Hopefully the component won't throw this error if this area is disabled. We have to analyze it. If it is possible, we will include a workaround in the next version.

NetSetMan Support

Administrator

Registered: 2005-08-06

Posts: 1,833

Re: Cannot open/create script programs if Quick Access is disabled

We are unable to reproduce this issue with the latest version 5.1.1 in Windows 10.

After changing the registry key as described and rebooting the system, the quick access shortcuts are gone in Windows File Explorer, so the change was done correctly. However, in NetSetMan using the file dialogs we don't see any error message. The file dialog is displayed correctly, although it ignores the registry setting and still displays the quick access item in the tree menu.

If you have done further changes in your system, please describe them as well.