1 Reply Latest reply on Jun 30, 2017 10:16 AM by cwinning

    Java MSI followed by Shavlik Java Patch

    bharris Rookie

      So we recently had a Critical issue come up where in Windows 7 devices the software hive file located at C:\Windows\System32\Config\Software was becoming bloated to over 2 gigs in size. We spent a little over a week hand fixing close to 1500 machines because once the machine does this it becomes inoperable after a reboot, even attempting to image the devices WinPE was attempting to access this bloated registry somehow and machines would have to be completely wiped and reloaded. So anyway after extensive testing the issue was found to be a unique combination. Listed below is the testing steps I used to determine this exact combination. As you can see from below, only when there was a mandatory deployment of the Java MSI and the Shavlik update pushed at the same time did it break the machine. Interestingly enough the MSI installation is using the GUID for both 121 and 131 as detection methods so if the 131 were to be installed after 121 it would no longer attempt to install 121 from the MSI deployment.  At this point at I'm at a loss on why this would happen. Does anyone have any further insight or has anything similar happened on your end that could point me in the direction of the smoking gun for the issue? On a side note we had about a dozen machines experiencing registry bloat before this debacle, is it possible Shavlik patch with another deployment of the same software in the background was causing it on these machines or it just happened to be a coincidence? Has anyone experienced issues with Shavlik and Registry bloat in the past?

       

      1. Remove all installations of Java from a test machine.

      2. Make a required deployment of Java 8 Update 121 MSI installation to test machine.

      3. Wait for installation to finish. Reboot.

      4. Push Java 8 Update 131 Software Update file to test machine.

      5. Monitor C:\Windows\System32\Config\Software file to witness bloat occur.

      6. Bloat started immediately as Java 8 Update 131 Software Update started to install.

      7. Stop Java 8 Update 131 installation. Reboot device.

       

      8. Remove all instances of Java from machine again.

      9. Install Java 8 Update 121 via MSI Installation again.

      10.   Stop deployment of Java 8 Update 121 to test machine.

      11.   Push Java 8 Update 131 Software Update file to test machine.

      12.   Monitor C:\Windows\System32\Config\Software file to witness bloat occur.

      13.   Bloat did not occur

      14.   Machine successfully updated to Java 8 Update 131 with no bloat.