NanaZIP’s preview of version 6 lands as a clear evolution of the 7‑Zip fork: deeper Windows 11 integration, a host of interface rewrites using XAML, a controversial new extract‑on‑open workflow, and security‑minded codec changes that move the project further from its 7‑Zip lineage while tightening compatibility requirements. (neowin.net) (github.com)
NanaZIP began as a modern, Microsoft Store–friendly fork of 7‑Zip, with the stated aim of bringing the raw power of the 7‑Zip engine to a Windows 11‑style user experience. The project has been available via GitHub, SourceForge, and the Microsoft Store, and has long emphasized Fluent/XAML styling, automatic updates through the Store, and tighter integration with Explorer context menus. (github.com)
The 6.0 Preview continues that trajectory: more UI elements have been ported to XAML to feel native on modern Windows builds; several dialogs and the progress UI have been rewritten; and under the hood NanaZIP swaps some codec implementations and drops legacy 32‑bit support. Those are the headlines users will notice right away, and they also indicate priorities—polish, security, and a narrower OS support window. (neowin.net, github.com)
From an engineering standpoint, XAML adoption reduces the amount of bespoke UI glue the maintainers must support across OS updates. That can improve stability in the long run and make it easier to adopt new Windows features like Mica and dark mode correctly. However, porting UI surfaces is not risk‑free: previews often reveal edge cases where older automation, scripts, or custom themes behave differently. Users who rely on automation that interacts with NanaZIP’s windows should validate workflows against the preview. (github.com)
This is material. Compression codecs have been the root cause of several archive‑parsing vulnerabilities over the years; replacing or changing codec implementations is a legitimate hardening step. But it also means regression testing is essential: codecs touch many codepaths and interact with container formats in subtle ways. Users who rely on edge‑case archives—multi‑layer nested formats, obscure flags, or self‑extracting executables—should verify that the new decode paths handle their data identically to prior versions. GitHub release notes show these changes were deliberate and part of a wider synchronization to modern 7‑Zip code, but they also underscore the need for continuous validation. (github.com)
The practical effect: enterprises with legacy 32‑bit fleets, or users on older Windows 10 service updates, may need to remain on NanaZIP 5.x or consider alternate builds. The Store still hosts stable and preview channels; administrators should plan compatibility and rollout testing accordingly. (github.com)
Format support remains broad: because NanaZIP is a 7‑Zip derivative, it inherits robust support for ZIP, 7z, TAR, gzip, bzip2, ISO, and can extract RAR archives using compatible libraries, even if it cannot produce proprietary RAR archives. The inability to create RAR remains a legal/technical limitation shared across open‑source 7‑Zip forks. (github.com)
As with any preview software, automatic updates and Store semantics can change the behavior of installed packages. Administrators and power users should test preview builds in isolated environments before broad rollouts. The project’s GitHub also lists known issues and behavior differences introduced by MSIX packaging and Desktop Bridge constraints that can affect edge cases. (github.com)
This preview is not just cosmetic refreshment—it's a deliberate reprioritization that trades broader legacy compatibility for tighter integration, modern UI, and a lower security profile surface. That trade is defensible for many users, but it should be approached with verification: test critical workflows, confirm that the zstd and other codec behaviors match your archived data, and treat extract‑on‑open as a helpful convenience that must be managed carefully in security‑conscious environments. (github.com, neowin.net)
NanaZIP 6 Preview can be acquired through the Microsoft Store’s Preview channel or by downloading the preview MSIX packages from the project’s GitHub releases. Users who want the safest route should wait for the stable rollout; those who want to influence testing and file early bug reports will find the preview an appropriate testing ground. (github.com)
(Notes: feature details and exact system requirements are taken from NanaZIP’s preview release notes and contemporary coverage; readers should consult the project’s release page and test environments for the most up‑to‑date specifics and to verify behavior in their unique contexts.) (github.com, neowin.net)
Source: Neowin NanaZIP 6 is out in preview with a lot of UI improvements and new features
Background
NanaZIP began as a modern, Microsoft Store–friendly fork of 7‑Zip, with the stated aim of bringing the raw power of the 7‑Zip engine to a Windows 11‑style user experience. The project has been available via GitHub, SourceForge, and the Microsoft Store, and has long emphasized Fluent/XAML styling, automatic updates through the Store, and tighter integration with Explorer context menus. (github.com)The 6.0 Preview continues that trajectory: more UI elements have been ported to XAML to feel native on modern Windows builds; several dialogs and the progress UI have been rewritten; and under the hood NanaZIP swaps some codec implementations and drops legacy 32‑bit support. Those are the headlines users will notice right away, and they also indicate priorities—polish, security, and a narrower OS support window. (neowin.net, github.com)
What’s new in NanaZIP 6 (quick summary)
- Extended XAML adoption: Address bar, status bar, property and info dialogs, and progress dialog now use XAML-based Windows controls for a more native look and behavior. (neowin.net)
- Extract‑on‑open: Opening archives can now automatically extract their contents to a temporary or chosen location—behaving more like macOS/iPadOS archive handling—skippable with Shift and toggleable in settings. (neowin.net)
- File associations added: Native association support for CBR, CBZ, and ASAR file types. (neowin.net)
- Zstandard (zstd) decoder changes: NanaZIP is using a different Zstandard decoder than the 7‑Zip mainline implementation, a change promoted as improving reliability and reducing attack surface. (github.com)
- Performance and footprint: Faster startup and a removal of 32‑bit components; minimum OS is now 64‑bit Windows 10 2004 (build 19041) or Windows Server 2022 (build 20348). (neowin.net, github.com)
Deeper look: UI modernization and XAML adoption
Native controls and the Windows 11 aesthetic
NanaZIP 6 moves more UI surfaces away from legacy Win32 dialogs and custom-drawn controls toward XAML-based components. The practical outcome is improved visual consistency with Windows 11: rounded corners, Fluent theming, and native accessibility support that comes with platform controls. The team explicitly lists the address bar, status bar, properties, information dialogs, and the progress dialog among the newly ported parts. (neowin.net, github.com)From an engineering standpoint, XAML adoption reduces the amount of bespoke UI glue the maintainers must support across OS updates. That can improve stability in the long run and make it easier to adopt new Windows features like Mica and dark mode correctly. However, porting UI surfaces is not risk‑free: previews often reveal edge cases where older automation, scripts, or custom themes behave differently. Users who rely on automation that interacts with NanaZIP’s windows should validate workflows against the preview. (github.com)
Progress dialog and UX improvements
A new progress dialog replaces the previous implementation with a control that aligns with Windows 11 dialogs—this means better visual feedback and potentially more granular cancellation/resume options in future iterations. For users who frequently copy large archives or extract multi‑GB datasets, the improved progress experience is a welcome usability enhancement. As with any UI rewrite, early preview builds may expose regressions; users with critical workflows should wait for the stable release or test in isolated environments. (github.com)The Extract‑on‑Open feature: usability vs. expectations
What it does
The extract‑on‑open feature causes NanaZIP to extract an archive automatically when you open it, rather than presenting the archive contents inside a read‑only viewer list inside the app. This mirrors how many modern mobile and macOS file managers behave, with the goal of making opening archives more frictionless. Holding the Shift key while opening an archive will bypass extract‑on‑open, and the feature can be disabled entirely in settings. (neowin.net)Why the change matters
- For casual users, extract‑on‑open reduces steps: double‑click and the files are ready. It aligns NanaZIP’s behavior with contemporary consumer expectations on mobile and macOS. (neowin.net)
- For power users, it can break muscle memory. Many workflows rely on inspecting archives before extracting, or on selectively extracting individual files. Automatic extraction must be easy to disable or temporarily bypass; NanaZIP’s Shift override and settings toggle aim to address that. (neowin.net)
Risk and policy considerations
Automatically extracting archives can expose users to immediate risks if they inadvertently extract and run executables from untrusted sources. While the feature can speed routine tasks, it increases the importance of default security behaviors—such as Zone.Identifier propagation, SmartScreen checks, and clear warning dialogs for executable content. The preview notes indicate the skip and disable mechanisms, but users in sensitive environments should treat extract‑on‑open as a feature to opt into rather than leave enabled by default until they’ve validated controls. (neowin.net)Codec and security changes: the Zstandard swap and what it means
NanaZIP’s release notes indicate a swap in Zstandard decoder implementations, moving away from the 7‑Zip mainline’s Zstandard code to an alternative decoder. The stated reasoning is to improve reliability and reduce potential vulnerabilities tied to the previous implementation. The project also mentions synchronization with 7‑Zip mainline on other fronts while selectively replacing components where the NanaZIP maintainers deem it necessary. (github.com)This is material. Compression codecs have been the root cause of several archive‑parsing vulnerabilities over the years; replacing or changing codec implementations is a legitimate hardening step. But it also means regression testing is essential: codecs touch many codepaths and interact with container formats in subtle ways. Users who rely on edge‑case archives—multi‑layer nested formats, obscure flags, or self‑extracting executables—should verify that the new decode paths handle their data identically to prior versions. GitHub release notes show these changes were deliberate and part of a wider synchronization to modern 7‑Zip code, but they also underscore the need for continuous validation. (github.com)
Platform support and the end of 32‑bit builds
NanaZIP 6’s preview raises the minimum supported OS and explicitly removes 32‑bit components: the new minimums are 64‑bit Windows 10 version 2004 (build 19041) or Windows Server 2022 (build 20348) or newer. The preview’s changelog notes that all 32‑bit components were removed from the app package. That reduction simplifies testing and allows the team to optimize binaries for 64‑bit platforms, but it excludes older machines and 32‑bit OS deployments. (neowin.net, github.com)The practical effect: enterprises with legacy 32‑bit fleets, or users on older Windows 10 service updates, may need to remain on NanaZIP 5.x or consider alternate builds. The Store still hosts stable and preview channels; administrators should plan compatibility and rollout testing accordingly. (github.com)
File type associations and format coverage
NanaZIP 6 adds file associations for CBR, CBZ, and ASAR—formats commonly used for comic archives and some Electron app packaging respectively. This makes NanaZIP a more natural double‑click handler for those formats on Windows, moving it closer to a one‑stop archive tool for everyday use. For users who prefer different tools for those file types, Windows’ default app settings still allow reassignment. (neowin.net)Format support remains broad: because NanaZIP is a 7‑Zip derivative, it inherits robust support for ZIP, 7z, TAR, gzip, bzip2, ISO, and can extract RAR archives using compatible libraries, even if it cannot produce proprietary RAR archives. The inability to create RAR remains a legal/technical limitation shared across open‑source 7‑Zip forks. (github.com)
Installation, preview access, and update channels
NanaZIP is distributed through multiple channels: the Microsoft Store (stable and Preview packages), GitHub releases (MSIX packages), and SourceForge mirrors for older distribution preferences. The preview build is explicitly available in the Microsoft Store as “NanaZip Preview” and via the project’s GitHub releases for sideloading. For enterprise deployment, MSIX packages can be deployed using standard enterprise tools; the project’s documentation includes guidance for unpackaged modes and MSIX installation. (github.com)As with any preview software, automatic updates and Store semantics can change the behavior of installed packages. Administrators and power users should test preview builds in isolated environments before broad rollouts. The project’s GitHub also lists known issues and behavior differences introduced by MSIX packaging and Desktop Bridge constraints that can affect edge cases. (github.com)
Critical analysis: strengths, real benefits, and potential pitfalls
Notable strengths
- Modern UX that fits Windows 11: The move to XAML and Fluent‑style controls produces a cleaner, more accessible interface that aligns with current Windows design language. This reduces cognitive friction for new users and brings interface parity with other modern apps. (github.com)
- Security-first codec decisions: Moving to an alternative zstd decoder signals proactive security attention. Given history, swapping or hardening codec implementations is a defensible approach to reduce vulnerability exposure. (github.com)
- Convenience features: Extract‑on‑open and added file associations reduce friction for common tasks, especially for casual users moving between devices and mobile ecosystems. (neowin.net)
- Open‑source transparency: NanaZIP’s public source and Store distribution model mean updates and fixes are auditable and community‑driven—an advantage for security and longevity compared with closed binaries.
Potential risks and trade‑offs
- Behavioral regressions from UI rewrites: Replacing many UI components with XAML can introduce accessibility or automation regressions. Scripts and integrations that relied on previous window structures may require updates. Preview testers should exercise edge workflows. (github.com)
- Extract‑on‑open security considerations: While convenient, automatic extraction increases the chance of inadvertent execution of malicious content. The Shift override is useful, but organizations should treat the feature cautiously and potentially disable it by default in managed environments. (neowin.net)
- Compatibility and deployment scope: Dropping 32‑bit support and raising platform minimums simplifies engineering but excludes users on older or specialized hardware. Enterprises with mixed OS baselines must plan phased migrations. (neowin.net, github.com)
- Codec replacement regressions: Swapping a core codec implementation reduces one risk surface while potentially introducing subtle incompatibilities with certain archives. Rigorous test coverage and community reports will be essential to surface any edge‑case failures. (github.com)
Performance claims and verification
Community assessments and forum testing frequently report that NanaZIP’s extraction speeds and overall workflow feel competitive with—sometimes faster than—7‑Zip and WinRAR in common scenarios. However, performance can be highly environment‑dependent: CPU generation, storage medium (HDD vs SSD), archive type, and threading settings all alter results. Benchmarks cited in community threads are useful indicators but should be validated against representative workloads before making deployment decisions. Any specific performance claim in preview notes should be verified on the target hardware.Practical recommendations
- For everyday users who value a modern UI and convenience, test NanaZIP 6 Preview on a secondary machine or in a VM, and keep automatic updates enabled only after confirming compatibility with your workflows. (github.com)
- For IT departments and enterprises, hold off on wide deployment until the stable channel arrives. If NanaZIP’s replacement of codec components addresses a known vulnerability you currently mitigate manually, factor that into your upgrade timeline and perform compatibility testing. (github.com)
- If you rely on 32‑bit systems or older Windows versions, remain on the stable 5.x series or evaluate alternate archivers; NanaZIP 6’s 64‑bit requirement is explicit and removes 32‑bit support. (neowin.net)
- Treat extract‑on‑open as opt‑in for security‑sensitive machines; configure endpoint policies or use NanaZIP’s settings to disable it by default in managed images. (neowin.net)
Final verdict
NanaZIP 6 Preview is an important step toward a polished, Windows‑native archiving experience: the UI modernization and accessibility gains are real, and the security‑minded codec changes show pragmatic stewardship. For individual power users and Windows 11 adopters, the preview hints at a smoother day‑to‑day experience; for administrators, the project’s evolving minimums and codec swaps raise legitimate testing and compatibility priorities.This preview is not just cosmetic refreshment—it's a deliberate reprioritization that trades broader legacy compatibility for tighter integration, modern UI, and a lower security profile surface. That trade is defensible for many users, but it should be approached with verification: test critical workflows, confirm that the zstd and other codec behaviors match your archived data, and treat extract‑on‑open as a helpful convenience that must be managed carefully in security‑conscious environments. (github.com, neowin.net)
NanaZIP 6 Preview can be acquired through the Microsoft Store’s Preview channel or by downloading the preview MSIX packages from the project’s GitHub releases. Users who want the safest route should wait for the stable rollout; those who want to influence testing and file early bug reports will find the preview an appropriate testing ground. (github.com)
(Notes: feature details and exact system requirements are taken from NanaZIP’s preview release notes and contemporary coverage; readers should consult the project’s release page and test environments for the most up‑to‑date specifics and to verify behavior in their unique contexts.) (github.com, neowin.net)
Source: Neowin NanaZIP 6 is out in preview with a lot of UI improvements and new features
