Hello We have been deploying Java via GPO for about a year now, and follow the well documented approach of grabbing the MSI from the offline.exe installer. (Double click the installer and grab the msi & cab file from C: Users administrator AppData LocalLow Sun Java) But with the recently released Version 8 Update 60 this no longer seems to work. An MSI is extracted to C: Users administrator AppData LocalLow Oracle Java jre1.8.0_60 now, and to C: Windows Installer, but no.cab file and neither work if double clicked. It's looking like Oracle will only release an.msi installer to enterprise customers on a support agreement.

Something we just cannot afford. Has anyone else experienced this and has anyone found a work around? I see that you've already got it nailed down via GPO. Just a heads up on a few things. The separate.cab file was discontinued after Java 7.

In version 8 all the necessary JRE files are bundled into the actual MSI file. The error that you saw is usually the result of running the Java msi file in a non-elevated session. This is why it works via GPO (since computer level GPOs already run elevated). Also, as Jeremy_B noted the MSI is no longer (starting with Update 60) copied to.LocalLow Sun. But instead to.LocalLow Oracle. Also note that since Java 8 Update 20 the JRE is installed in STATIC mode meaning each update will be installed in a separate folder.

For the PDQ Deploy package we make sure to uninstall previous Java 8 versions prior to installing the new update and we also force the installation back to the standard%PROGRAMFILES% Java jre8 folder. Ekolu Down In The Valley Rar here. I'm not sure why Oracle changed the installations to Static mode. This option used to be optional and was (at least originally) only used when certain applications needed specific Java versions to run. Anyway, I'm happy to hear you were able to get it to run. I see that you've already got it nailed down via GPO. Just a heads up on a few things.

Oracle has released a new version of Java 7 Update 11. The direct download links to the offline installers are included at the end of this article.

The separate.cab file was discontinued after Java 7. In version 8 all the necessary JRE files are bundled into the actual MSI file. The error that you saw is usually the result of running the Java msi file in a non-elevated session.

This is why it works via GPO (since computer level GPOs already run elevated). Also, as Jeremy_B noted the MSI is no longer (starting with Update 60) copied to.LocalLow Sun.

But instead to. Romanian Map Ets 2 Torrent Pes 14 here. LocalLow Oracle. Also note that since Java 8 Update 20 the JRE is installed in STATIC mode meaning each update will be installed in a separate folder.

For the PDQ Deploy package we make sure to uninstall previous Java 8 versions prior to installing the new update and we also force the installation back to the standard%PROGRAMFILES% Java jre8 folder. I'm not sure why Oracle changed the installations to Static mode. This option used to be optional and was (at least originally) only used when certain applications needed specific Java versions to run. Anyway, I'm happy to hear you were able to get it to run. Thanks for the new location Waitsain.

I also used the obvious msi from C: windows installer and edited it in ORca to remove the Updates function and it worked. I have found that running the install a second time will invoke the 'There is a problem with this windows installer package.' This actually is OK since running it silent doesn't do anything if the PC already has this version. I'm wondering if I can get the latest version to remove all previous versions silently before installing itself. I tried this with WSUS Packager which pushes non Microsoft updates through WSUS and it worked great! I like so many others in this thread got the 'There is a problem with this windows installer package. A program required for this install to complete could not be run.'