Comment 5 for bug 1417146

Don Cady (doncady) wrote :

This is definitely an installer/packaging issue. Sure, windows has this quirk. But if the installer cleaned up the 32bit version entries, this behavior wouldn't occur. See bug 1417070