I found a small bug, not sure if it's related to your issue i forgot to update 7zSFX configuration switch /ai7 to reflect new 2019 packages the bug only affect this switch, all other switches and default mode are good pack updated switch is now /ai9
Weird... Now that I checked, msvc.exe /aiU didn't uninstall the runtimes. The cmd windows says "Finished" with no errors, but ARP panel still shows the runtimes with their installation date, even after a restart. Gonna try the manual way. Edit: Same thing, even after I manually start the msi's AND manually point to the file in the prompt. Though the error is about vc2017, not 2019... Edit #2: I can't even uninstall my current 2017's from the ARP panel lol. I think that's what it's going on about, it can't find the msi package for the previous version(I guess)? Edit #3: There doesn't seem to be a 7zip_bla-bla.001 folder in the Temp dir. Instead there's a 000 folder. After that, there's no 2017 folder(2019 instead). But even after I change those to their EXISTING values, installer throws the same error. I honestly have no idea how this happens. If anyone could try this and give feedback, would be nice. I'm already setting up a VM with the same windows 10 ltsc to test. Edit #4: No such issue on a clean VM install. Also, no idea how I could've caused this problem on my live system... On the VM, I ran v17 first, then ran v18b on top of the currently installed runtimes - no issue. Ran v17, ran v18b /aiU(uninstalled flawlessly), deleted %localappdata%\Temp folder, ran v18b - no issue.
Hi there, Well I just noticed that \2008\x86\vc_red.msi not installed for some reasons. On Windows 10 1809 X64. Have to check my Windows 7 later but tried running Uninstaller.cmd and checking in programs and features afterward to make sure of the removal of the runtimes and then running Installer.cmd. 2008 X86 did not install. Running the MSI file itself worked. Edit: My Windows 7 X64 was not effected.
I was going to tell yo use debug script i use to see why it's not installing, but you installed it already this is how the script detect 2008 x86 Code: file exist? %Windir%\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.7523_none_4bf3b680bf9ea69d\mfcm90.dll product code exist? hklm\software\wow6432node\microsoft\windows\currentversion\uninstall\{9BE518E6-ECC6-35A9-88E4-87755C07200F}
After using Uninstaller.cmd and also removing the left overs using programs and features (yes, I almost have different left over entries almost): mfcm90.dll was present in C:\WINDOWS\WinSxS\x86_microsoft.vc90.mfc_1fc8b3b9a1e18e3b_9.0.30729.7523_none_4bf3b680bf9ea69d I believe this is actually part of Windows 10 itself? I also had: [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{9BE518E6-ECC6-35A9-88E4-87755C07200F}] "DisplayIcon"="C:\\WINDOWS\\SysWOW64\\msiexec.exe,0" (Yes, only DisplayIcon) Maybe you could remove any possible left over registry keys via uninstall.cmd and do not just depend on the MSI uninstallers? I deleted the key and ran install.CMD. Now seams everything is fine.
MSI itself should have removed the DisplayIcon value, it's part of its components not sure why it didn't, but i will add registry clean leftovers to Uninstall.cmd anyway no, it's not inbox component in any Windows but WinSxS files are not removed immediately upon uninstallation (updates files too) the system must run scavenge process to remove orphaned files this process is usually part of DISM /Cleanup-Image operation, or Disk Cleanup (if superseded updates exist) thanks for the heads up
For some reason Visual C++ 2008 Redistributable - x86 9.0.30729.7523 was not installed when I used Installer.cmd, only x64. I installed with vc_red.msi manually afterwards. What could be the reason? EDIT: Same for Visual C++ 2010 x86 Redistributable