| Symptoms |
|---|
When deploying 32-bit Java updates to 64-bit operating systems when using SCUPdates, the update fails.
| Cause |
|---|
This issue is caused by a Java install bug. The installer reads information for deployment on Windows operating systems in the 64-bit region of the registry, rather than the 32-bit region, which causes the failure.
| Resolution |
|---|
Currently, there is no workaround or resolution available for this issue. Once a workaround or a resolution is available, this article will be updated.
Technical support has submitted a bug report to Sun/Oracle. For more information, see Oracle bug 6995830.
Update 1/16/14 - Shavlik will soon be releasing a new plugin for SCCM called Shavlik Patch for SCCM which should help to resolve Java installation issues. The plugin allows Shavlik to utilize the same mechanisms that the Shavlik Protect program uses to workaround the Java bug.
| Additional Information |
|---|
To be alerted when this article is updated, click Subscribe to Document in the Actions box.
We have implemented a workaround solution with our Shavlik Protect product. Unfortunately, SCCM does not have the advanced commands for patch deployment which are necessary for this solution to be used along with a publicly available download of Java patches. For SCUPdates, we are looking for ways around this problem, but for the time being will need to continue waiting for Oracle to fix the installer issue.
We submitted a bug over two years ago to Sun/Oracle stating the issue and the necessary fix. Oracle has a voting system from their consumers to decide on which non-security bugs will be fixed with each update.
| Affected Products |
|---|
Shavlik SCUPdates