[SOLVED] Files corrupted, SHA not matching

[Emmanuel64]

Hello x-davidl

, I sent a request to withsecure, I'm waiting for a response.

I'll post the information here.

[x-davidl]

Thank you.

I can't imagine uninstalling everything just to update Edge.

Another workaround for now is to run microsoftedgesetup.exe, which unfortunately downloads the entire MSI file. This results in multiple downloads per computer.
It overwrites everything without worrying about previous versions, but it's impossible to keep up with the Edge update schedule
. Regards.

[Emmanuel64]

Hello,

I just received a response from WithSecure...


Hello,
Thank you for your support request. Your incident has been assigned to me, and I will continue working with you on this.
Based on your description and tests, this aligns directly with an issue that was discovered in our EDR module. We have already completed internal testing and confirmed the issue and a solution. This solution is currently in Beta and will be released as an Early Access version on Monday the 14th. If no issues are reported, it should be deployed to General Availability on the 21st.
If you would like to test it, you can use the Early Access version from the profile assigned to the portal.
Enable Early Access on a Profile
1. Log in to elements.withsecure.com with your Business + MFA account
2. Select the client using the scope selector at the top (If applicable/partner)
3. Go to Security Configurations > Profiles
4. Choose the platform tab (Windows Computers, Servers, Mac, Linux, Mobile)
5. Open the client profile, or clone it (icon ⋮ > Clone profile)
6. Enable the Early Access option under General -> Client Software Access
7. Click Save and Publish
8. Go to Environment > Devices
9. Select the relevant devices
10. Click Assign profile > choose the profile > Assign

[x-davidl]

Hello,

ah, they admit it,

thank you very much. I'll check on my console to see if I'm eligible for Early Access.

Let's discuss it in the forum.

Have a great weekend. Best
regards.

[sfonteneau]

Thank you so much for the feedback!

[x-davidl]

Hello everyone, hello Emmanuel64,

good news! Indeed, withsecure seems to have fixed the Edge update problem:

post at 2:00 AM:

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 isc-microsoft-edge(=152.0.4191.62-48) in C:\\Program Files (x86)\\wapt\\private\\install\\waptp8rj4yov, files corrupted, SHA not matching for [\'MicrosoftEdgeEnterpriseX64.msi\']\n']

the same post at 14:00

Installing: MicrosoftEdgeEnterpriseX64.msi (152.0.4191.62)
Waiting for key: {C21066D7-B43A-39B2-94E5-69B0FDCB13D5} to appear in Windows registry
Installed: isc-microsoft-edge(=152.0.4191.62-48)


Have a great day everyone

! Regards

[Emmanuel64]

Hello x-davidl,

thank you for your feedback

. I've installed the profile on 5 machines (X10 and Windows 11), some updated correctly, others didn't…
I've tried restarting the machines, so I'm not sure how the change is taking effect.

I'll wait until tomorrow to give feedback to withsecure

[t.heroult]

Hello,
I have the same problem with Edge and Chrome.
In short:
The package fails on some machines.
I recompile the package, and then it works on some machines where it didn't before, and fails on others where it worked fine.
Basically, it's completely random!

[Emmanuel64]

Hello

, do you have an antivirus or EDR WithSecure (or F-Secure)?

If not, try uninstalling the antivirus on the affected computer (disabling it didn't change anything for me).

Regards

[t.heroult]

We have withsecure across the entire network.
It's the same agent version on all workstations, regardless of whether the packet gets through or not.