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 secures itself via AppX/UWP container, but it uses a bunch of other security enhancements that are of great benefit when running NanaZip as a legacy app. The issue is that the latest versions of NanaZip can't and don't run as legacy apps at all. Can legacy support be re-introduced? There are many applicatons that use 7-Zip libraries and they can be rebuilt using NanaZip libraries, but onyl if legacy is supported.
If DISM is used to remove packages, such as Client License Service (ClipSVC) and Windows License Manager service, then NanaZip can't work at all due to the type of license it uses.
The text was updated successfully, but these errors were encountered:
I realize NanaZip secures itself via AppX/UWP container, but it uses a bunch of other security enhancements that are of great benefit when running NanaZip as a legacy app. The issue is that the latest versions of NanaZip can't and don't run as legacy apps at all. Can legacy support be re-introduced? There are many applicatons that use 7-Zip libraries and they can be rebuilt using NanaZip libraries, but onyl if legacy is supported.
If DISM is used to remove packages, such as Client License Service (ClipSVC) and Windows License Manager service, then NanaZip can't work at all due to the type of license it uses.
The text was updated successfully, but these errors were encountered: