NanaZip - Open source file archiver intended for the modern Windows experience

Discussion in 'MDL Projects and Applications' started by Mouri_Naruto, Sep 25, 2021.

  1. Mouri_Naruto

    Mouri_Naruto MDL Developer

    Jul 10, 2014
    605
    2,130
    30
  2. rayman95

    rayman95 MDL Senior Member

    Oct 3, 2018
    450
    316
    10
    sad, that we can't install on 10 IoT LTSC without M$ Store..
     
  3. Windows_Addict

    Windows_Addict MDL Junior Member

    Feb 23, 2026
    56
    479
    0
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. sometogive

    sometogive MDL Novice

    Feb 5, 2026
    34
    24
    0
    #188 sometogive, Aug 22, 2026
    Last edited: Aug 22, 2026
    I have a point to raise regarding my own setup.
    I’ve moved on from 7-Zip and am now using NanaZip—a really great tool.
    However, what bothers me immensely is the fact that NanaZip associates itself with *.wim files—something that absolutely should not happen.
    I even had to roll back my system at one point because of this, only to later discover the culprit in the registry:
    Windows Registry Editor Version 5.00

    [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.WIM\OpenWithList]
    "a"="40174MouriNaruto.NanaZip_gnj4mf6z9tkrc!NanaZip.Modern"

    This must not happen under any circumstances; simply right-clicking a `boot.wim` file to open it with NanaZip just once is enough for the entry to embed itself in the registry and create the association.
    What can I do to prevent my *.wim files from becoming associated with it again—for instance, during a future NanaZip update? I never had these issues with 7-Zip.

    I also tried using the "Windows default apps" file association settings, but that isn't the solution I'm looking for; it doesn't help me. A *.wim file shouldn't be associated with that by default—unless I specifically configure that setting myself.