64-bit Windows MSI doesn't remove previous 32-bit installs

[dtjohnso]

I suspect that this may be related to the fix applied in this issue: #4795

Today, as I upgrade to 2.6 on several Windows systems (some previously had 2.3, others previously had 2.2.3.2 [or something like that, I forget exact version but it was in the 2.2.x stream]), the installer would complete, but running pandoc --version in cmd would return the previous version.

Upon inspection, I found that the MSI had installed 2.6 into the C:\Program Files\Pandoc\ folder properly for a 64-bit system. However, there remained a folder in C:\Program Files (x86)\Pandoc\ that contained my previous installed version.

As soon as I deleted the folder under Program Files (x86), a call to pandoc --version returned the proper output indicating that the upgrade was successful. I suspect that Windows checks the x86 folder first in the PATH system variable, and thus was running the pandoc executable from there because it still found something there. Once that folder was absent, the system found the 64-bit version without any problems.

Perhaps the MSI installer could be set up to check both locations for previous installs and remove to prevent this happening in future?

[jgm]

There may be a way to do this, but I don't think I'm going to worry about it.
The present behavior actually seems like a good default, since it's possible someone might intentionally have both 64 and 32-bit versions installed.