JAVA_HOME/PATH and empty folder remains after uninstall Corretto x86 and x64

[yamadamn]

Describe the bug

I uninstalled both Corretto x86/x64 in Windows;
But the JAVA_HOME and PATH environment variable remains, and the installed directory remains empty.

To Reproduce

1. Install both Corretto x86/x64 in Windows (with default option)
2. Uninstall both Corretto x86/x64.

Expected behavior

Both JAVA_HOME and PATH (x86/x64) environment will be removed after uninstall.

Screenshots

It depends on install/uninstall order.

Platform information

OS: Windows 10
Version "build 1.8.0_192-amazon-corretto-preview2-b12"

Additional context

This issue is related to #15, #22 and #37 .

[davecurrie]

Hi @yamadamn. Thanks for letting us know, we're taking a deeper look and will get back with an answer soon.

[yoroto]

Hi @yamadamn ,

Thank you for submitted the issue!

This is actually an known issue of Windows 10. You can find the Microsoft KB here: https://support.microsoft.com/en-us/help/3166232/windows-installer-package-doesn-t-update-system-environment-variables If you log off and log in again, you should see the environment variables get updated and the folder get removed. Otherwise you can apply the Microsoft hotfix mentioned in the post. Let me know whether it works for you.

We will also look into adding an option to warn Windows 10 customer to sign off after uninstall if the hotfix is not present. So I will leave this issue open until we added the improvement.

[yamadamn]

Hi @yoroto ,

Thank you for your investigation.
I have tried again with Corretto 8.202.08.2.
But, unfortunately, the behavior has not improved when logoff and login again, and even after the restart.
JAVA_HOME/PATH environment variables and empty folder still remains.
Could you reproduce the issue at your end?
I think this behavior is your installer's limitation. If so, I will give up this issue to be resolved.

[yoroto]

Hi @yamadamn

I have managed to reproduce your issue. The root cause was because the x86 and x64 MSIs share some installer code, and therefore are having the same IDs for some installation components. When you uninstall both of them, it confused the msiexec on which one to remove.

We will try to fix this in future releases. Thank you for submitting the issue!

[EricEdens]

@yoroto : When you look at this, it also happens when updating an existing MSI. Here are the steps that I did:

1. Install 64-bit 8u202 MSI
2. Install 64-bit 8u212 MSI
3. Uninstall 64-bit 8u202

Below is a screenshot of the environment variable editor in Windows 10:

[cliveverghese]

This issue was resolved in 8.222.x.x. Closing the issue.