Like the function Test-IsMutexAvailable from (you guessed it) PSADT. Second you need something to validate that MSIExec isn’t busy. Get-ChildItem | Where $WhereBlock | Select-Object -Property $selectProperties $UninstallKeys += Get-ChildItem HKU: -ErrorAction Silentl圜ontinue | Where-Object $null = New-PSDrive -Name HKU -PSProvider Registry -Root Registry::HKEY_USERS

If I stole this from you – post a comment and I will remove it and post a link instead.

Unfortunately I have no idea where I stole this from. I can see so many problems with it – but it works. I just found one that was small and did the trick. Let’s gather what we need to create something simplistic.įunction to retrieve installed software in Powershell. Now, to workaround this you can read the information regarding the installed Edge Chromium (it is installed, just not running) and then perform an over-ride (REINSTALL=ALL REINSTALLMODE=A according to the comments on Borncity). The previous version is installed, but version 84 always starts and you can’t upgrade because of this and for some reason Edge Chromium is special software that just doesn’t tag along? Yet, the users will be stuck with Edge Chromium 84.

This is installer will bomb-out with “there is a newer version already installed”. The issue at hand though is that Edge Chromium is a moving target, so including even the latest version today in whatever upgrade process you have – will most likely in a months time have an older version than what you have installed on your endpoint. If you deploy Edge Chromium later version (like 87? 88?) to your 1909/2004 devices – and then upgrade to Windows 10 20H2, you will effectively downgrade Edge Chromium to 84.Īs far as I can understand – the details, the workarounds and apparently a promise that this will be better is all published on Borncity. Specifically – Edge Chromium v84 (something something)

Ms edge current version