Tranquil IT Forum

Published: **September 16, 2026 - 10:21**

Hello everyone

@dcardon
Thank you for your feedback
I didn't see any "Edge" processes running in the background, but Microsoft knows how to trick us

@t.heroult
Thanks for the info, this alternative is indeed easier than installing via .exe files

Just in case, I used MeshCentral in PowerShell (completely transparent to the user)

Code: Select all

# Trouver la clé "Edge"
Get-ChildItem "HKLM:\SOFTWARE\Classes\Installer\Products" | Where-Object {
    (Get-ItemProperty $_.PSPath -Name ProductName -ErrorAction SilentlyContinue).ProductName -like "*Edge*"
} | Select-Object PSChildName, @{N="ProductName";E={(Get-ItemProperty $_.PSPath).ProductName}}


# verifier la clé (optionnel)
Get-ItemProperty "HKLM:\SOFTWARE\Classes\Installer\Products\<clé_trouvée>"

# Supprimer la clé
Remove-Item "HKLM:\SOFTWARE\Classes\Installer\Products\<clé_trouvée>" -Recurse -Force


# Installation via wapt (ou via la console)
wapt-get install tis-microsoft-edge

Published: **September 16, 2026 - 3:07 PM**

Hello Emmanuel64,

this is an elegant solution to (in my case) prevent it from searching for a previous .msi file that it can't find.

My error is that Wapt fails because the new MSI is looking for the MSI that was used for the installation.

Deleting the registry key with Mesh in PowerShell then validates the installation.

Many thanks

. Best

Published: **September 16, 2026 - 3:12 PM**

Glad I could help.

On my end, everything is back to normal, except for a few jobs that will patiently wait for Monday's WithSecure update.

Have a good day!

Tranquil IT Forum

[SOLVED] Files corrupted, SHA not matching

Re: files corrupted, SHA not matching

Re: files corrupted, SHA not matching

Re: files corrupted, SHA not matching