-
-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Not implemented" error message when trying to open .zip files in explorer #160
Comments
Searching the internet this issue seems to arise with Microsoft Office as well, so it is more or less general file association problem. I've found couple of instances from NanaZip source code where I think something like "Not implemented" error would pop up, but would there be NanaZip process running if it originated from NanaZip? Because when I get this error I don't see NanaZip process running. I've however found a workaround. I can create a new file type in admin cmd.exe with "ftype Zip=nanazip.exe %1" and then associate it with .zip file with "assoc .zip=Zip". Now I have new option in context menu of .zip files in "Open with" menu called "NanaZip Graphical User Interface" and I can select it as default from "Open With"->"Choose another app"->"Always use this app to open .zip files". "NanaZip Graphical User Interface" option is also available under "NanaZip" in "Settings"->"Default apps"->"Set defaults by app" but not in "Choose default apps by file type". So now I have to do this for all NanaZip filetypes and I get expected behavior with the double click in Explorer. btw. I installed NanaZip from winget using package ID M2Team.NanaZip and I'm using Windows 10 Pro 21H2 19044.1706. |
I have archive files associated to NanaZip, but when I try to open any archive file from Windows explorer by double clicking or selecting "Open" from context menu I get error message with the file name and message "Not implemented".
"Open archive" works in NanaZip context as well as all the other options there. This is per machine problem as I don't have the same problem on my other machine.
Any idea how to fix this?
The text was updated successfully, but these errors were encountered: