Nanazip Does Not Handle Permissions Correctly - "Access is denied" Instead of Elevation Prompt

[MNLierman]

Expected Behavior: When attempting to complete an action that required elevated permissions such as creating a zip file from a folder in the root of the C drive, or other areas that require admin rights, I would expect that Nanazip would, 1) Test the permissions through various APIs available to do so, and if Administrative rights are required to save a zip file in that location, 2) Nanazip should inform the user that the directory requires an elevation request, and, 3) In this dialog give the user the option to save somewhere else if they do not wish to elevate permissions or they are unable to do so.

Actual Behavior: The actual behavior is frustrating, Nanazip displays a generic "Access is denied. cannot open file {path}" which looses the configuration the user created for the zip file creation and it also does not offer an alternative save location. I'm actually surprised that when the "Access is denied" message was created, that permissions checks and elevation were not added. At the very least, Nanazip should be offering to save the zip somewhere else if it encounters a permissions issue.

Steps to Reproduce:

1. Select any files or folders in the root of the C drive, right click, Nanazip, and attempt to create a archive.
2. Choose your settings and press OK.
3. An "Access is denied." message is encountered instead of a choice dialog to handle the permissions appropriately.

[300f20t]

the same issue

[MNLierman]

I see active development for Nana Zip and this seems like a pretty straight forward issue to resolve, but I reported this 4 months ago and no devs have commented. I'm sure people run into this every day and just don't say anything about it.

Devs / Contributors: If UWP apps cannot obtain UAC escalation themselves then it can be done through an escalation helper process, which I have seen many store apps do. This may be a required behavior workaround, ie. using a UAC privilege escalation helper process.

I think it would be most beneficial to the user experience to resolve this but sooner than later, as the experience of finding out Nanazip is incapable of handling privileged areas of NTFS, is quite frustrating and time consuming.