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.
I was able to download an EXE from the Web Version of the store but .... but the thing is.... I want SCOOP to see it. so i don't have a redundancy. I am trying to bake a reference image of Windows 11 with Uniget controlling all the package managers.... And it's a headache dealing with MSIXBUNDLES because by default the WILL NOT install system wide....like 7-Zip Can! So....do I just GIVE UP, stick with 7-zip? I really like NAnaZip...but if it can't install system-wide all users....then what's the point?