Well, the problem is not that the process are failing directly. It is that the Main application Thinstall directory sandbox gets corrupted.
For example.
On a fresh system, never run anything before, nothing installed (Well, windows of course)
I launch Chrome Thinapp (Applinked to Java 60).
It works fine.
On a fresh system, never run anything before, nothing installed.
I launch Chrome Thinapp (Applinked to Java 55).
It works fine
Then I close out chrome completely (saying this before someone asks)
I update the Java location to the new Java 60 thinapp...using the exact same name as the previous java (or even utilizing inplace upgrade aka java.exe.1)....again Chrome is Applinked with this Java location/name
I Launch Chrome Thinapp (Now applinked to Java 60)
It throws an Error about the program being corrupt.
I revert Java to 55
It throws the same error
I Delete the Thinstall\Google Chrome directory
Launch Chrome Thinapp
Works fine
Update to Java 60
Launch Chrome, it fails
Delete the Thinstall\Google Chrome Directory
Launch Chrome, it launches.
The problem is that the update applink corrupts the working Thinstall Directory. This is a major issue for users where they will all need to delete their Thinstall directory to allow for the browser to work. This would also reset how they have tweeked their browsers. In terms of maintenance this is an issue.
So, what did i miss? IS it something with The Java Sandbox, or is this how updating applinked apps works? As in it breaks the app until reset?
Would merged isolation mode fix this? What am I missing in how it works with a new thinstall directory vs updating an application that has already created that thinstall directory?
Thanks,
Darren