- 
    Bug 
- 
    Resolution: Fixed
- 
     P3 P3
- 
    None
- 
        b12
- 
        Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build | 
|---|---|---|---|---|---|---|
| JDK-8045913 | 8u25 | William Harnois | P3 | Closed | Fixed | b01 | 
| JDK-8039505 | 8u20 | William Harnois | P3 | Closed | Fixed | b14 | 
| JDK-8052828 | emb-8u26 | William Harnois | P3 | Resolved | Fixed | b17 | 
                    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.
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.
- backported by
- 
                    JDK-8052828 msi installers should support rollback -           
- Resolved
 
-         
- 
                    JDK-8039505 msi installers should support rollback -           
- Closed
 
-         
- 
                    JDK-8045913 msi installers should support rollback -           
- Closed
 
-