I'm using the Withsecure EDR.

I now need to find out why, and how to properly purge the installation.
With wsuninstaller it worked on one machine, but not on another.

Okay... I finally have the answer.

It was indeed the EDR that was causing the problem, despite a global policy applied to all workstations.
When the EDR is completely disabled, some filters should remain active.
After uninstalling it, everything returns to normal and Wapt works normally.

Still...

To clarify,

rather than waiting for an EDR scan, I scanned the file manually. A correct hash then appeared.

I'm finally starting to pinpoint the problem.

I download the .wapt file, extract it manually, and the hash is incorrect.
To speed things up, I manually scan the .msi file, and the hash is correct.

If I do the same thing with EDR completely disabled, the hash is incorrect for about twenty seconds...

Hello

, I hadn't seen your reply, so I added a line to my previous post which is still in the vein of bizarre things:


I copy the .msi to the desktop: hash OK.
I copy it to the root of C, the downloads folder, yes wapt\private\install: hash modified.
I bring it back to the...

I

placed the .msi file alone on the desktop of a problematic PC, then checked its hash
: `Get-FileHash MicrosoftEdgeEnterpriseX64.msi -Algorithm SHA256 | Format-List`

Algorithm: SHA256
Hash: 093D7CBE7019C7504446599632DD984DCE567DCB96604F14E4384C2C1420239B
Path: C:\Users\*\Desktop ...

Hello,

I'm continuing my research to understand what's modifying the SHA, without finding an answer :(

I've run scans with WithSecure without finding anything, I've tried to find similarities between the affected machines, but they could be new or old machines, running Windows 10 or Windows 11... so nothing...

Hello

, I had the same problem. I was using version 14.44.3521 "windows(>=6.0)" and the update 14.51.36247 is for "windows(>=10)"

. This happened to me with several packages. For some, it seemed strange that there hadn't been an update for a while, while others, like the vcredist error, led me to...

Hello,

thank you for this clarification on how package installation works. It's strange because, unless I'm mistaken, it only affects Edge. It happened once with Teams, but that was an isolated case that resolved itself.
I'll keep a close eye on it. Have

a good day.

Hello,

despite updating tis-microsoft-edge, I'm still having the same issue with corrupted SHA files on some machines...

I'm open to any suggestions.

Thanks.