Registry fix for: Opening .UnityPackage in currently Active Unity (instead of opening new Unity instance)

An article by mgear    No Comments

I think after installing 5.6 32bit unity, it broke the Windows Explorer default application feature – Where clicking UnityPackage in Explorert would open in any currently active Unity instance.
(instead it started opening new Unity instance every time).
Found solution in forums (link)

Here is Registry Fix (with added fix for deleting old broken .unitypackage key)
*NOTE: you need to set one of your Unity installtion path there (i used 2017LTS path, but can try 2018 or later too)
https://gist.github.com/unitycoder/74ed2abca19fa227b0027bdad58ad65f

References:
– After 2018.x this might be always broken? https://issuetracker.unity3d.com/issues/double-clicking-a-unity-package-file-in-the-system-opens-a-new-unity-instance-instead-of-importing-the-package