You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I realize NanaZip is a UWP app that needs to be installed as such to work correctly, but version 3.X can be extracted and launched as a regular non-UWP app. The only issue is that each time it is launched that way, "Cannot enable security mitigations" error pops up. Some people cut out almost all UWP packages with DISM, making installation of UWP apps impossible afterwards. UWP never became mainstream.
The most important security mitigations, such CFG and Stack protection, are applied even in non-UWP mode.
Can you add an option to disable that error or release non-UWP version? It would need a basic installer to make NanaZip a "Registered Application" with defined Capability Access settings. Is there some way to disable that error in current 3.X release?
The text was updated successfully, but these errors were encountered:
You can close this one. The issue with security mitigations isn't related to NanaZip and version 3.0 does function as a portable non-UWP app, but I can't get classic shell context entries to show on Windows 11.
Excellent work! Thank you!
I realize NanaZip is a UWP app that needs to be installed as such to work correctly, but version 3.X can be extracted and launched as a regular non-UWP app. The only issue is that each time it is launched that way, "Cannot enable security mitigations" error pops up. Some people cut out almost all UWP packages with DISM, making installation of UWP apps impossible afterwards. UWP never became mainstream.
The most important security mitigations, such CFG and Stack protection, are applied even in non-UWP mode.
Can you add an option to disable that error or release non-UWP version? It would need a basic installer to make NanaZip a "Registered Application" with defined Capability Access settings. Is there some way to disable that error in current 3.X release?
The text was updated successfully, but these errors were encountered: