Jre 8 Update 101
HelloWe 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 administratorAppDataLocalLowSunJava)But with the recently released Version 8 Update 60 this no longer seems to work.An MSI is extracted to C:UsersadministratorAppDataLocalLowOracleJavajre1.8.060 now, and to C:WindowsInstaller, 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?TIAMartin. 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 JeremyB noted the MSI is no longer (starting with Update 60) copied to.LocalLowSun. But instead to.LocalLowOracle.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%Javajre8 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. I see that you've already got it nailed down via GPO.
Me@yb.io:$ java -version java version '1.8.0101' Java(TM) SE Runtime Environment (build 1.8.0101-b13) Java HotSpot(TM) 64-Bit Server VM (build.
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).
How to download igi. You can never get the best link of this game from any other website so Download Project IGI 2 Game Highly Compressed For PC from here and enjoy playing it without any worry.Project IGI 2 is an awesome Action video game that includes good scenes. Project IGI 2 is a Action Stealth video game that was developed by Innerloop Studios and it was published by Codemasters.It was released in March 3, 2003 and platforms in which this installment was published were Microsoft Windows. In this game, the action scenes are awesome and players enjoy while playing it. I am personally playing this game for many years and I guarantee you that the link which I provided here is 100% working so you need no worry about its working just Download Project IGI 2 For PC Kickass from here and play it on your PC using Microsoft Windows.In this product there is only one mode, Single Player, you cannot play this game online.Recently, we have uploaded click on the link to get the file. There are many other creations of IGI series but the popularity of this creation is remarkable because of its amazing visuals and stunning gameplay people prefer this version of IGI to play and like it a lot.This is an awesome game and it includes a lot of Action Stealth scenes.
Also, as JeremyB noted the MSI is no longer (starting with Update 60) copied to.LocalLowSun. But instead to.LocalLowOracle.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%Javajre8 folder.I'm not sure why Oracle changed the installations to Static mode.
Jre Version 8 Update 101 Download
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:windowsinstaller 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.' I uploaded the 2 Java 8 update 60 msi files like normal to WSUS Packager, and it installed without a problem at all.Also, I think it is important to note that the MSI files that Oracle provides to paying customers seem to give the EXACT same error as the extracted ones. We tried both and they provide the same issues so they seem to be the exact same MSI's. I didn't investigate too closely but they seem to be the same.Thank you everyone for this assistance, this has been a struggle. Maddog2050 wrote:Please see my blog post below for how to modify the installer so that you can install Java 8 Update 60 by GPO%uFEFFHey I just tried this and it seems to have worked!
The first steps got me the MSI which I went ahead and put in a GPO. It deployed and thus far I have not received any errors. Next I will try logging in to a computer as a mere mortal and see if it is still successful.edit. BTW, when the new version installed the old versions were removed.
I've been able to do this pretty consistently now on several machines.