Microsoft Technical Takeoff
Nov 27 2023 07:00 AM - Nov 30 2023 11:30 AM (PST)
Microsoft Tech Community

Isolating JRE within an MSIX container.

Copper Contributor

I have packaged a legacy version of Java (1.6.27) for a browser application that requires a specific version.
The MSIX package works using Edge in Internet Explorer mode.


However if there is a locally installed version of Java which is a later version, the packaged version no longer works, Edge launches the locally installed Java instead.  I have tried using Tim Mangan's JREBlock, but that has not worked either.


Could this be due to MSIX not having merge/override settings that App-V does?


Any ideas?

12 Replies
You mis-characterized the cause, but yeah. When looking for the version of Java to use, it enumerates the Classes keys for java (which are version encoded numbers, not "real GUIDS").

Under App-V, we used JREBlock in the capture to cause deletion markers inside the package virtual registry. So the deletion marker was a merge overlay hiding the local value (not override in the traditional App-V sense) but those hide the local registry entries.

The MSIX virtual registry does not have a similar deletion marker strategy in the virtual registry. But there is a new capability available in the AppXManifest file that allows for the specification of deleted registry items there.

At this time there is no automated way to create those entries, and I'm sure that you've seen how many that can be; more than you'd want to manually add (in the hundreds).

Your best option today may be to get rid of the native install of Java. Does it really need to be in the image any more?
Oh that's interesting... Have you an example of using the deletion marker strategy in the AppXManifest? Could try to specifically set the markers for only the version we have installed.

And no, getting rid of Java is a no go at this point for our client.



There's no such setting or an option to do that yet. However, you can submit this as an idea on MSIX feedback - Microsoft Community Hub.


Meanwhile, if you can share the installer for your app, we can check if there's a workaround available.

I did have an idea, but it is more work for YOU. When you packaged Java in App-V you probably used JavaBlock to create the deletion markers in the registry. As I mentioned, Microsoft did not bring along virtual registry deletion markers to MSIX. But it should be possible to create all of the additional CLSID keys for future Java versions, but point them to the Java in your package.

So rather than run JavaBlock with the addkeys option prior to packaging and then run again with the delete keys while packaging, but before you install crusty java version, you do the following:
1) Edit a version of JavaBlock for the add keys case that looks for existing keys and adds future keys with the content you find in your last found key.
2) No pre-package script needed.
3) While packaging, install crusty java first, then run that script to add in the future keys.

As I said, Java should die, so I'm not planning a script update myself. Good luck!

Hi @SajidRavat 

Please share the JRE packaged application on this thread using the drag and drop feature and we will investigate into it further. 

Fiza Azmi
PM, MSIX Team 

Hi @fizaazmi 

There is no application.  The JRE is required in Edge within a session running in Internet Explorer mode.

Hi @SajidRavat 

Which is the MSIX package in question in this case?

Fiza Azmi

Hi @fizaazmi 

The MSIX package contains the JRE only. Version is 1.6.27.





It occurred to me to ask if the Java package has ExectionAlias extension, and is this for Windows 11, and is there a shared package container.



I think I did try ExecutionAlias... It is for Windows 10 for now and we are attempting as a standalone package.

@SajidRavat Yes, Execution alias needs only Win 10 1703. It is Shared Package Container that needs Win 11. The idea here is that Edge needs the shated container since it is also running in a container. This might not also work, but is the best idea that I have.

That makes sense... I'll give that a go on Windows 11 when I get an opportunity.