Hello,
I have created a base installer version 1.0.0. I created a major upgrade that contains a new sub-directory, version 1.0.1. While in the process of testing my major upgrade, I accidentally interrupted the install process. I then uninstalled all packages and tried again.
The original package, 1.0.0 installs as it should. When installing 1.0.1, it finds the old version and uninstalls it as expected. It then goes to install the new 1.0.1 version, but no files are installed. It does not give an error and believes it has installed properly. After the install completes, windows explorer pops open to the system32 directory. I have no idea why this is happening, but think it might be a clue as to why 1.0.1 is not installing properly.
I suspected I corrupted my registry somehow and the installer possibly thinks that 1.0.1 is already installed, therefore not installing it. I ran the Windows Installer Cleanup Utility (msicuu2.exe) and tried to clean up any old remnants of the installs that I interrupted that caused the computer to be in this error state, but the behavior continues.
I tested installing 1.0.0 and 1.0.1 on top of that on a different machine and it worked as expected (uninstalls 1.0.0, installs 1.0.1 and windows explorer does not open to system32).
I have tried changing the product code, upgrade codes, but still doesn't work on the machine mentioned above.
Any advice on how to repair the computer that has been possibly corrupted, and why windows explorer pops open the system32 folder?
FOLLOW US
Get the latest news in Application Packaging