Ákos Bakos

".\VMware-Horizon-Client-2312.1-8.12.1-23531249.exe /silent /norestart" installs the following components:  winget install "vmware.horizonclient" --silent  Winget installs the following components: 

vmware.horizonclient can be installed like that: winget install "Microsoft.DotNet.Runtime.6" --silent --accept-source-agreements --accept-package-agreements winget install "Microsoft.VCRedist.2015+.x64" --silent --accept-source-agreements --accept-package-agreements winget install "Microsoft.DotNet.DesktopRuntime.6" -**-version 6.0.28** --silent --accept-source-agreements --accept-package-agreements winget install "VMware.HorizonClient" --silent...

But even when I get done this specific version for successfully installation. Then the upgrade process will fail, because these new dependencies which are wrong by VMware?! Or I am...

@gwblok yes it is - but we have found a workaround. I mean either use the workaround (iex (irm cu.osdcloud.ch) or install directly W11 ;-)

@gwblok the new function (Get-LenovoBiosCatalog) seems to work. The old functions which I was referencing back July 2022, doesn't exist anymore.

What about SSL Inspection config on your firewall? Could it be possible to check this behaviour in your home network if it's still the same?

Would it work like that for you: $Urls = @( 'http://www.msftconnecttest.com/connecttest.txt' ) foreach ($Uri in $Urls){ try { if ($null = Invoke-WebRequest -Uri $Uri -Method Head -UseBasicParsing -ErrorAction Stop) {...

If you need this connection check into WinPE, change the code in your boot media (and don't update the module and the start of the process). For WinRE, this change...

Any help on that @trongtinh1212?

As @joebartlett94 says your second issue should be solved now. For the first one, please try to avoid using white and/or special characters in the URL.