![jre sleep expert jre sleep expert](https://media1.popsugar-assets.com/files/thumbor/OAH17j_DBzIVQOzZO00OtfvhTqs/0x413:2990x1983/fit-in/1200x630/filters:format_auto-!!-:strip_icc-!!-/2019/11/06/564/n/38922805/74bba23b5dc2bd5507f6c8.01834427_.jpg)
The install log is 542KB too large to post.
![jre sleep expert jre sleep expert](https://i.ytimg.com/vi/ZGFVxQiLH8k/hqdefault.jpg)
So at this point, "S" also stands for "Stumped"! "MODE=U" wouldn't install at all unless there was a previous version installed (which makes sense), but was definitely an upgrade mode because you couldn't choose where to install it in the GUI. So I think MODE=S is part of the solution, but not all of it. When I clicked Yes, it removed the existing install, and started a new install, but the new install failed. If Java of the same version I was installing was already installed, it asked if I wanted to reinstall it. "MODE=S" did a "C" ("Consumer", not "Static") install when I installed when Java wasn't already installed. But I think there's more to it than just the MODE property, unfortunately. I suspect "S" stands for "Static", "U" for "Upgrade in Place," and "C" for "Consumer", the default being C. I see what you were noticing in the MSI there's a lot of logic relating to the type of install and the value of MODE I wasn't able to figure it all out though. I got all excited when I read your suggestion and was sure that MODE=S was going to do the trick.
![jre sleep expert jre sleep expert](https://assets.website-files.com/5cfbc938982a74a06bedeb1a/5d0f6c3ee9f1778479efe30e_sleep-article-02.jpg)
I'm currently working with the 1.6u11 MSI.want to get that made Static before installing 1.6u12. That isn't working I keep getting a Patch-In-Place install. In my MST, in the Property Table, I've created a new Property named STATIC whose Value is 1, and I've applied it as a Modification in the GPO. On the command line, one apparently appends STATIC=1.īut I'm trying to create a GPO that will use an MST to do a Static installation.so far without success. The "Static" installation is supposed to provide for this. But on servers, where we tend to have Java apps that break when Java is upgraded, I'd just as soon leave the old version behind until I am certain I don't need it. This works great for workstations, where you have few, if any Java applications looking for specific versions. describes Java's new "patch-in-place" behavior.