JDK-8039397 : msi installers should support rollback
- Type: Bug
- Component: install
- Sub-Component: install
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2014-04-07
- Updated: 2017-06-29
- Resolved: 2014-04-08
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 8 | JDK 9 |
|---|---|
8u20Fixed  |
9 b12Fixed |
Description
Our msi installers currently call installer.exe and ignore the return code. If there is a failure in installer.exe process, such as unzipping/unpacking/patching/registering etc, it will fail silently. They will be left with an msi that appears to be installed, but is actually a broken product. If our installer.exe custom action returns anything other than 0, we should throw an error and rollback the install. They should be left with a clean machine.
Comments
|