

You can see everything replaced in a Repair Install by opening the install ISO's sources\install.esd | | install.wim within 7zip (prior to doing so, you'll want to determine the specific index to look within by executing from an admin terminal: Dism /Get-ImageInfo /ImageFile:"Z:\sources\install.wim" - you can mount the image, in lieu of using 7zip, but I find 7zip more efficient: Dism /Mount-Image /ImageFile:"Z:\sources\install.wim" /Index: /MountDir:"C:\Mount" and unmount via Dism /Unmount-Image /MountDir:"C:\Mount" /Discard).If a repair install doesn't fix an issue, the issue isn't the OS but a third-party program or malware, as a repair install replaces all files within %WinDir%, as well as a handful of system files within %ProgramData%, %ProgramFiles%, and %ProgramFiles(x86)% Once Dism and Sfc don't fix an issue, and the cause of the issue isn't readily apparent after an hour or so of searching online, I generally recommend a Repair Install since it's simply more efficient than spending hours troubleshooting.Even using the 64-bit version of 7-zip, and running the installer as admin, and running 7zip as admin & changing the settings, it still didn't work until I did this.I missed your comment, so on a side note as a general FYI: This was the only thing that worked for me.



If you find 7-zip Context Menu extension and the Filename column shows 7-zip32.dll and it is enabled, then you should right-click and Disable selected items Sort by Description column and look for 7-Zip Shell Extension.Run it and make sure Options-> Show 32-bit Shell Extensions is ticked.Download and unzip ShellExView (圆4 version) from the NirSoft website.It turns out that even with 64bit 7zip installed you can end up with 32bit shell extension enabled, possibly a hangover from previous 32-bit install. If you're using the correct bitness of 7zip and have the correct settings set but it still doesn't work, then it may be that the wrong Explorer shell extension is enabled.
