Cannot find Unity 2019.2 installation on Windows

[JesseTG]

I can install it, but once it's actually installed I can't use it. I believe it's related to Unity 2019.2's lack of an ivy.xml, which this similar project is also running into.

This is how I'm invoking it:

Install-Module UnitySetup -Force -Verbose

Find-UnitySetupInstaller -Version 2019.2.2f1 -Components 'Windows' -Verbose | Install-UnitySetupInstance -Verbose

Get-UnitySetupInstance -Verbose

Here's the relevant part of the log for my GitHub Actions pipeline:

2019-08-30T22:06:01.1276722Z ##[group]Run ci/windows/install.ps1
2019-08-30T22:06:01.1277251Z �[36;1mci/windows/install.ps1�[0m
2019-08-30T22:06:01.3416527Z shell: C:\Program Files\PowerShell\6\pwsh.EXE -command ". '{0}'"
2019-08-30T22:06:01.3417035Z ##[endgroup]
2019-08-30T22:06:10.7166181Z Installing UnitySetup
2019-08-30T22:06:18.7384029Z VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.MetaProvider.PowerShell.dll
2019-08-30T22:06:18.7401058Z VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.ArchiverProviders.dll
2019-08-30T22:06:18.8413548Z VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.CoreProviders.dll
2019-08-30T22:06:18.8876010Z VERBOSE: Acquiring providers for assembly: C:\program files\powershell\6\Modules\PackageManagement\coreclr\netstandard2.0\Microsoft.PackageManagement.NuGetProvider.dll
2019-08-30T22:06:19.9589522Z VERBOSE: Using the provider 'PowerShellGet' for searching packages.
2019-08-30T22:06:20.7741530Z VERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.
2019-08-30T22:06:20.7851477Z VERBOSE: Getting the provider object for the PackageManagement Provider 'NuGet'.
2019-08-30T22:06:20.7911241Z VERBOSE: The specified Location is 'https://www.powershellgallery.com/api/v2' and PackageManagementProvider is 'NuGet'.
2019-08-30T22:06:21.2903530Z VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='UnitySetup'' for ''.
2019-08-30T22:06:22.5347533Z VERBOSE: Total package yield:'1' for the specified package 'UnitySetup'.
2019-08-30T22:06:22.8004680Z VERBOSE: Performing the operation "Install-Module" on target "Version '5.1.126' of module 'UnitySetup'".
2019-08-30T22:06:22.8985803Z VERBOSE: The installation scope is specified to be 'CurrentUser'.
2019-08-30T22:06:22.9012159Z VERBOSE: The specified module will be installed in 'C:\Users\runneradmin\Documents\PowerShell\Modules'.
2019-08-30T22:06:22.9234379Z VERBOSE: The specified Location is 'NuGet' and PackageManagementProvider is 'NuGet'.
2019-08-30T22:06:22.9240188Z VERBOSE: Downloading module 'UnitySetup' with version '5.1.126' from the repository 'https://www.powershellgallery.com/api/v2'.
2019-08-30T22:06:22.9709940Z VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='UnitySetup'' for ''.
2019-08-30T22:06:23.1538996Z VERBOSE: Searching repository 'https://www.powershellgallery.com/api/v2/FindPackagesById()?id='powershell-yaml'' for ''.
2019-08-30T22:06:23.1950254Z VERBOSE: InstallPackage' - name='powershell-yaml', version='0.4.0',destination='C:\Users\runneradmin\AppData\Local\Temp\1732613849'
2019-08-30T22:06:23.1967149Z VERBOSE: DownloadPackage' - name='powershell-yaml', version='0.4.0',destination='C:\Users\runneradmin\AppData\Local\Temp\1732613849\powershell-yaml.0.4.0\powershell-yaml.0.4.0.nupkg', uri='https://www.powershellgallery.com/api/v2/package/powershell-yaml/0.4.0'
2019-08-30T22:06:23.2005372Z VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/powershell-yaml/0.4.0'.
2019-08-30T22:06:23.3179935Z VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/powershell-yaml/0.4.0'.
2019-08-30T22:06:23.3193498Z VERBOSE: Completed downloading 'powershell-yaml'.
2019-08-30T22:06:23.3240906Z VERBOSE: InstallPackageLocal' - name='powershell-yaml', version='0.4.0',destination='C:\Users\runneradmin\AppData\Local\Temp\1732613849'
2019-08-30T22:06:23.6900448Z VERBOSE: InstallPackage' - name='UnitySetup', version='5.1.126',destination='C:\Users\runneradmin\AppData\Local\Temp\1732613849'
2019-08-30T22:06:23.6914109Z VERBOSE: DownloadPackage' - name='UnitySetup', version='5.1.126',destination='C:\Users\runneradmin\AppData\Local\Temp\1732613849\UnitySetup.5.1.126\UnitySetup.5.1.126.nupkg', uri='https://www.powershellgallery.com/api/v2/package/UnitySetup/5.1.126'
2019-08-30T22:06:23.6919393Z VERBOSE: Downloading 'https://www.powershellgallery.com/api/v2/package/UnitySetup/5.1.126'.
2019-08-30T22:06:23.7562238Z VERBOSE: Completed downloading 'https://www.powershellgallery.com/api/v2/package/UnitySetup/5.1.126'.
2019-08-30T22:06:23.7638218Z VERBOSE: Completed downloading 'UnitySetup'.
2019-08-30T22:06:23.7659527Z VERBOSE: InstallPackageLocal' - name='UnitySetup', version='5.1.126',destination='C:\Users\runneradmin\AppData\Local\Temp\1732613849'
2019-08-30T22:06:23.9424096Z VERBOSE: Validating the 'powershell-yaml' module contents under 'C:\Users\runneradmin\AppData\Local\Temp\1732613849\powershell-yaml.0.4.0' path.
2019-08-30T22:06:24.1591824Z VERBOSE: Test-ModuleManifest successfully validated the module manifest file 'C:\Users\runneradmin\AppData\Local\Temp\1732613849\powershell-yaml.0.4.0'.
2019-08-30T22:06:24.1619710Z VERBOSE: Validating the authenticode signature and publisher of the catalog file or module manifest file of the module 'powershell-yaml'.
2019-08-30T22:06:24.1870287Z VERBOSE: Catalog file 'powershell-yaml.cat' is not found in the contents of the module 'powershell-yaml' being installed.
2019-08-30T22:06:24.2600693Z VERBOSE: Checking for possible command collisions for the module 'powershell-yaml' commands.
2019-08-30T22:06:24.9559219Z VERBOSE: Installing the dependency module 'powershell-yaml' with version '0.4.0' for the module 'UnitySetup'.
2019-08-30T22:06:25.0541688Z VERBOSE: Module 'powershell-yaml' was installed successfully to path 'C:\Users\runneradmin\Documents\PowerShell\Modules\powershell-yaml\0.4.0'.
2019-08-30T22:06:25.1662207Z VERBOSE: Validating the 'UnitySetup' module contents under 'C:\Users\runneradmin\AppData\Local\Temp\1732613849\UnitySetup.5.1.126' path.
2019-08-30T22:06:25.5830963Z VERBOSE: Test-ModuleManifest successfully validated the module manifest file 'C:\Users\runneradmin\AppData\Local\Temp\1732613849\UnitySetup.5.1.126'.
2019-08-30T22:06:25.5849776Z VERBOSE: Validating the authenticode signature and publisher of the catalog file or module manifest file of the module 'UnitySetup'.
2019-08-30T22:06:25.5922904Z VERBOSE: Catalog file 'UnitySetup.cat' is not found in the contents of the module 'UnitySetup' being installed.
2019-08-30T22:06:25.6078633Z VERBOSE: Checking for possible command collisions for the module 'UnitySetup' commands.
2019-08-30T22:06:25.8210877Z VERBOSE: Module 'UnitySetup' was installed successfully to path 'C:\Users\runneradmin\Documents\PowerShell\Modules\UnitySetup\5.1.126'.
2019-08-30T22:06:25.8291862Z Done installing UnitySetup
2019-08-30T22:06:25.8306637Z Installing Unity
2019-08-30T22:06:26.5629864Z VERBOSE: GET https://unity3d.com/get-unity/download/archive with 0-byte payload
2019-08-30T22:06:26.6743117Z VERBOSE: received -byte response of content type text/html
2019-08-30T22:06:27.0877957Z VERBOSE: HEAD https://download.unity3d.com/download_unity/ab112815d860/Windows64EditorInstaller/UnitySetup64-2019.2.2f1.exe with 0-byte payload
2019-08-30T22:06:27.2408220Z VERBOSE: received 985188448-byte response of content type application/x-msdos-program
2019-08-30T22:06:27.3423410Z VERBOSE: Downloading https://download.unity3d.com/download_unity/ab112815d860/Windows64EditorInstaller/UnitySetup64-2019.2.2f1.exe to C:\Users\runneradmin\.unitysetup\Installers\Unity-2019.2.2f1\UnitySetup64-2019.2.2f1.exe
2019-08-30T22:08:57.0351715Z VERBOSE: Installing Windows Editor
2019-08-30T22:08:57.0426243Z VERBOSE: 08/30/2019 22:08:57: Installing Windows to C:\Program Files\Unity\Hub\Editor\2019.2.2f1.
2019-08-30T22:13:49.3631329Z VERBOSE: 08/30/2019 22:13:49: Succeeded.
2019-08-30T22:13:49.3653853Z Done installing Unity
2019-08-30T22:13:49.3917042Z VERBOSE: Creating UnitySetupInstance for C:\Program Files\Unity
2019-08-30T22:13:49.4163672Z VERBOSE: Attempting to find UnityVersion in C:\Program Files\Unity
2019-08-30T22:13:49.4165726Z VERBOSE: Looking for ivy.xml files under C:\Program Files\Unity\Editor\
2019-08-30T22:14:13.1999948Z VERBOSE: 	Looking for version in C:\Program Files\Unity\Editor\Data\PackageManager\Unity\PackageManager\2018.3.7\ivy.xml
2019-08-30T22:14:13.2162085Z VERBOSE: 	Found version!
2019-08-30T22:14:13.2426656Z 
2019-08-30T22:14:13.2460303Z VERBOSE: Creating UnitySetupInstance for C:\Program Files\Unity\Hub\Editor\2019.2.2f1
2019-08-30T22:14:13.2470168Z VERBOSE: Attempting to find UnityVersion in C:\Program Files\Unity\Hub\Editor\2019.2.2f1
2019-08-30T22:14:13.2508312Z VERBOSE: Looking for ivy.xml files under C:\Program Files\Unity\Hub\Editor\2019.2.2f1\Editor\
2019-08-30T22:14:13.6667767Z VERBOSE: 	Looking for version in C:\Program Files\Unity\Hub\Editor\2019.2.2f1\Editor\Data\UnityExtensions\Unity\UnityVR\ivy.xml
2019-08-30T22:14:13.6779769Z WARNING: Unable to find version for C:\Program Files\Unity\Hub\Editor\2019.2.2f1
2019-08-30T22:14:13.6812689Z Version    Components Path
2019-08-30T22:14:13.6814021Z -------    ---------- ----
2019-08-30T22:14:13.6815409Z 2018.3.7f1    Windows C:\Program Files\Unity
2019-08-30T22:14:13.6816106Z 
2019-08-30T22:14:13.7908604Z ##[group]Run ci/windows/activate.ps1
2019-08-30T22:14:13.7909200Z �[36;1mci/windows/activate.ps1�[0m
2019-08-30T22:14:13.7961898Z shell: C:\Program Files\PowerShell\6\pwsh.EXE -command ". '{0}'"
2019-08-30T22:14:13.7962632Z env:
2019-08-30T22:14:13.7963307Z   UNITY_USERNAME: ***
2019-08-30T22:14:13.7963772Z   UNITY_PASSWORD: ***
2019-08-30T22:14:13.7964193Z   UNITY_PLATFORM: Windows
2019-08-30T22:14:13.7964619Z ##[endgroup]
2019-08-30T22:14:14.3764150Z 
2019-08-30T22:14:14.3768824Z 
2019-08-30T22:14:14.3775969Z     Directory: D:\a\Chromavaders\Chromavaders
2019-08-30T22:14:14.3776403Z 
2019-08-30T22:14:14.3778736Z Mode                LastWriteTime         Length Name
2019-08-30T22:14:14.3779359Z ----                -------------         ------ ----
2019-08-30T22:14:14.3780603Z d-----         8/30/2019 10:14 PM                Windows
2019-08-30T22:14:17.9785588Z WARNING: Unable to find version for C:\Program Files\Unity\Hub\Editor\2019.2.2f1
2019-08-30T22:14:18.0619578Z Start-UnityEditor : Could not find Unity Editor for version 2019.2.2f1
2019-08-30T22:14:18.0622992Z At D:\a\Chromavaders\Chromavaders\ci\windows\activate.ps1:12 char:1
2019-08-30T22:14:18.0624206Z + Start-UnityEditor -Project "$env:GITHUB_WORKSPACE" -Credential $Crede ...
2019-08-30T22:14:18.0625006Z + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2019-08-30T22:14:18.0625780Z + CategoryInfo          : NotSpecified: (:) [Write-Error], WriteErrorException
2019-08-30T22:14:18.0626596Z + FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Start-UnityEditor
2019-08-30T22:14:18.0627263Z  
2019-08-30T22:14:18.0860009Z ##[error]Process completed with exit code 1.

[JesseTG]

A possible workaround, if you're only using the Windows component (as I am), is to run this as soon as possible after installing any version of 2019.2:

$url = "https://gist.githubusercontent.com/JesseTG/ddca04b554a895b416ce62f224807882/raw/c05fa772c4e5cab0b1e7c6d779a6347522ae9483/ivy.xml"
$output = "C:\Program Files\Unity\Hub\Editor\2019.2.2f1\Editor\Data\PlaybackEngines\WindowsStandaloneSupport\ivy.xml"

Invoke-WebRequest -Uri $url -OutFile $output

I'm trying it now; if it doesn't work, I'll update this post. Fixed the output path, now it works.

[StephenHodgson]

Yeah I remember missing the ivy paths can break this tool pretty easy. @jwittner did we ever look into using the updated .json schema that's defining all the editor installation data?

[jwittner]

Thanks for the issue report @JesseTG . @StephenHodgson , I'm not seeing any .json files in the install path that indicate the version. Doing a deep search on all files, the only reliable text files on Windows seem to be header files in the WindowsStandalone support. I'll keep digging, but if I don't find anything I'll add that as another fallback path for finding the version.

[jwittner]

@StephenHodgson - We do have the changes to inspect the modules.json file, but it appears if you only install the Windows installer that file doesn't exist.