Page 1 of 2
files corrupted, SHA not matching
Published: August 13, 2026 - 09:32
by Emmanuel64
Good morning
On a few machines, I've been getting an error installing Edge directly from the WAPT repository without modification for a few days now.
I have the same problem today with "microsoft-teams-uwp" on 1 machine while it is properly installed on 20 other machines.
I cleared the cache on the computer, but it didn't change anything
Do you have any ideas or suggestions?
THANKS
Below is the log of the failure...
Code: Select all
File "C:\Program Files (x86)\wapt\waptservice\waptservice_common.py", line 1525, in _run
raise Exception(_('Error during install of {}: errors in packages {}').format(
Exception: Erreur lors de l'installation de ['hasp-microsoft-edge(=151.0.4129.78-49)']: erreurs dans les paquets [[PackageRequest(package='hasp-microsoft-edge',version=(Version('151.0.4129.78'), 49),architectures=['x64'],locales=['fr'],maturities=['PROD'],tags=['windows'],min_os_version=Version('10.0.17763'),max_os_version=Version('10.0.17763')), PackageEntry('hasp-microsoft-edge','151.0.4129.78-49' architecture='x64',maturity='PROD',target_os='windows'), 'Traceback (most recent call last):\n File "C:\\Program Files (x86)\\wapt\\common.py", line 5723, in install\n result = self.install_wapt(p.localpath,\n File "C:\\Program Files (x86)\\wapt\\common.py", line 4629, in install_wapt\n raise e\n File "C:\\Program Files (x86)\\wapt\\common.py", line 4368, in install_wapt\n packagetempdir = entry.unzip_package(cabundle=self.cabundle, target_dir = tempfile.mkdtemp(prefix=\'wapt\',dir=self.wapt_temp_dir))\n File "C:\\Program Files (x86)\\wapt\\waptpackage.py", line 2671, in unzip_package\n raise e\n File "C:\\Program Files (x86)\\wapt\\waptpackage.py", line 2663, in unzip_package\n verified_by = self.check_package_signature(cabundle,ignore_missing_files=ignore_missing_files)\n File "C:\\Program Files (x86)\\wapt\\waptpackage.py", line 2614, in check_package_signature\n raise EWaptCorruptedFiles(\'Error in package %s in %s, files corrupted, SHA not matching for %s\' % (self.asrequirement(), self.sourcespath, errors,))\nwaptpackage.EWaptCorruptedFiles: Error in package hasp-microsoft-edge(=151.0.4129.78-49) in C:\\Program Files (x86)\\wapt\\private\\tmp\\wapt4uhynhq1, files corrupted, SHA not matching for [\'MicrosoftEdgeEnterpriseX64.msi\']\n']]
Re: files corrupted, SHA not matching
Published: August 13, 2026 - 09:53
by Jarnaud
Hello,
The message indicates a SHA not matching. Could you compare the SHA of the package on the machine with the error and the SHA of the same package on a machine without the error?
On Windows machines, you can check the SHA of the MSI file using PowerShell:
`Get-FileHash .\filename.msi -Algorithm SHA256 | Format-List`.
On this machine, could there be any network intermediaries that might be interfering with the package installation? (antivirus, EDR, etc.)
There's a good chance the binary has been corrupted by an antivirus program.
Best regards.
Re: files corrupted, SHA not matching
Published: August 13, 2026 - 10:21
by Emmanuel64
Hello Jarnaud
, thank you for your help. The SHAs match correctly.
In the meantime, I edited the package in the editor for Edge, then rebuilt and imported it. This has worked for the moment (I have quite a few users on vacation, so few workstations are currently active
).
The idea naturally came to me after posting on the forum.
The same thing for Teams doesn't seem to have worked.
There is indeed an EDR on the workstations, but no message about it in the EDR console logs.
This is the first time I've had this kind of problem…
Re: files corrupted, SHA not matching
Published: August 14, 2026 - 10:10
by x-davidl
Hello everyone,
I'm having the same problem as Jarnaud. The catch is: it's not happening on all machines.
I tried editing and reposting the package, but no luck...
I'll wait for the next Edge
update.
-------------------------------
WAPT Enterprise
Version 2.6.1.17813
Server OS: Ubuntu 22.04
Administration machine OS: Windows Server 2022
Re: files corrupted, SHA not matching
Published: August 21, 2026 - 10:59
by Emmanuel64
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.
Re: files corrupted, SHA not matching
Published: August 21, 2026 - 4:46 PM
by sfonteneau
Hello.
What's certain is that the problem doesn't come from the package itself, since it works on some machines.
How it works:
When a machine downloads its package, it unzips it.
It checks the manifest signature (list of hashes of the signed package).
Then it verifies that the SHA2 sums in the package are the same as those declared in the manifest.
Here, it seems the file has been modified because the sum doesn't match.
The problematic file in the screenshot is indeed MicrosoftEdgeEnterpriseX64.msi.
So, the file that is present once unzipped doesn't have the same sum as the one indicated in the manifest
. Two explanations:
- The file has been modified directly within the package, in which case you need to be careful that it's not a compromise.
Or:
- Something on the machine is interfering with the file during the unzipping of the Wapt package (an antivirus program, for example, or the opposite... a virus).
This needs to be checked in your case.
Warning: I once encountered a virus installed on a computer that, every time an executable file was written to the machine, would modify that file to insert itself into it (to better spread). In your case, I have no way of saying that's what's happening, but you should still be careful.
Re: files corrupted, SHA not matching
Published: August 24, 2026 - 09:04
by Emmanuel64
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.
Re: files corrupted, SHA not matching
Published: August 26, 2026 - 4:05 PM
by f.fenouil
Good morning,
I am also experiencing the same problem.
I have tried several things, but nothing works (waiting for a higher version of the package, rebuilding the package, deleting it and then downloading it again, deleting the WAPT cache on the machines in question, reinstalling the agent, disabling the antivirus).
Code: Select all
Erreur : EWaptCorruptedFiles: Error in package mairie-microsoft-edge(=151.0.4129.107-48) in C:\Program Files (x86)\wapt\private\tmp\wapt3iazgawx, files corrupted, SHA not matching for ['MicrosoftEdgeEnterpriseX64.msi']
I should point out that this same package works perfectly on other machines in the same production environment and with similar settings.
While waiting for an idea that can solve the problem,
THANKS.
Re: files corrupted, SHA not matching
Published: September 3, 2026 - 2:11 PM
by Emmanuel64
Hello,
I'm continuing my research to understand what's modifying the SHA. Without finding an answer,
I've run scans with WithSecure, but found nothing. I've tried to find similarities between the affected machines, but they could be new or old, running Windows 10 or 11... so nothing is consistent.
Contrary to what I told "jarnaud" last time, the SHAs don't actually match (which makes sense). I was able to check in a package extracted to Program Files (x86)\wapt\private\install\wapt.... However, I don't understand when or how to find this package.
If anyone has any ideas on where to look, I'd be very grateful, because I'm completely stuck.
Thank you in advance for your help.
Re: files corrupted, SHA not matching
Published: September 3, 2026 - 3:39 PM
by Emmanuel64
D
I placed the .msi file alone on the desktop of a problematic PC, then checked the hash
Code: Select all
Get-FileHash MicrosoftEdgeEnterpriseX64.msi -Algorithm SHA256 | Format-List
Algorithm : SHA256
Hash : 093D7CBE7019C7504446599632DD984DCE567DCB96604F14E4384C2C1420239B
Path : C:\Users\*\Desktop\MicrosoftEdgeEnterpriseX64.msi
So far, so good
However, if I copy or drop the .msi file into "Downloads" or into .\wapt\private\install\", the hash changes
Even stranger, if I move it back to the desktop, the hash matches... so the file itself isn't modified. It's the hash calculation that seems to be altered
Compromise by a virus or malware seems, unfortunately, to be a serious possibility to consider
But I don't know how to find it, if that's what it is
The question remains: why this particular package?
I performed the same procedure with another MSI file, and the hashes matched