Page 4 of 5
Re: files corrupted, SHA not matching
Published: September 14, 2026 - 4:07 PM
by Emmanuel64
In this case, the cause has been identified at WithSecure.
You can try the "early access" deployed this morning (the process is just above) or wait for the patch which will be available on the 21st if the tests are successful.
Regards
Re: files corrupted, SHA not matching
Published: September 14, 2026 - 4:27 PM
by t.heroult
Thanks, I'll check it out.
But if a fix is planned, I think I won't waste time and will just wait.
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 10:09 AM
by Emmanuel64
Good morning
Tested on 6 devices, some reacted very quickly, others took longer. So overall it works
However, on two machines, I encountered errors when installing Edge using our "WAPT" solution. I then attempted a manual uninstallation, which failed silently. I then tried an installation using an MSI package, which also failed (installation logs below for reference)
I don't know if it's a side effect of the patch or something else…
To be continued
Installation using the MSI file:
Code: Select all
=== Verbose logging started: 15/09/2026 09:57:04 Build type: SHIP UNICODE 5.00.10011.00 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (24:18) [09:57:04:378]: Resetting cached policy values
MSI (c) (24:18) [09:57:04:378]: Machine policy value 'Debug' is 0
MSI (c) (24:18) [09:57:04:378]: ******* RunEngine:
******* Product: MicrosoftEdgeEnterpriseX64.msi
******* Action:
******* CommandLine: **********
MSI (c) (24:18) [09:57:04:378]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (24:18) [09:57:04:378]: Grabbed execution mutex.
MSI (c) (24:18) [09:57:04:428]: Cloaking enabled.
MSI (c) (24:18) [09:57:04:428]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (24:18) [09:57:04:428]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B0:D8) [09:57:04:428]: Running installation inside multi-package transaction c:\Users\emmanuel.fromentin\Desktop\MicrosoftEdgeEnterpriseX64.msi
MSI (s) (B0:D8) [09:57:04:428]: Grabbed execution mutex.
MSI (s) (B0:28) [09:57:04:441]: Resetting cached policy values
MSI (s) (B0:28) [09:57:04:441]: Machine policy value 'Debug' is 0
MSI (s) (B0:28) [09:57:04:441]: ******* RunEngine:
******* Product: c:\Users\emmanuel.fromentin\Desktop\MicrosoftEdgeEnterpriseX64.msi
******* Action:
******* CommandLine: **********
MSI (s) (B0:28) [09:57:04:441]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (B0:28) [09:57:04:441]: Note: 1: 2203 2: C:\WINDOWS\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (B0:28) [09:57:04:441]: Note: 1: 2205 2: 3: Property
MSI (s) (B0:28) [09:57:04:441]: MSCOREE not loaded loading copy from system32
MSI (s) (B0:28) [09:57:04:457]: End dialog not enabled
MSI (s) (B0:28) [09:57:04:457]: Original package ==> c:\Users\emmanuel.fromentin\Desktop\MicrosoftEdgeEnterpriseX64.msi
MSI (s) (B0:28) [09:57:04:457]: Package we're running from ==> C:\WINDOWS\Installer\72379a.msi
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 2205 2: 3: Property
MSI (s) (B0:28) [09:57:04:457]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (B0:28) [09:57:04:457]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (B0:28) [09:57:04:457]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (B0:28) [09:57:04:457]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C21066D7-B43A-39B2-94E5-69B0FDCB13D5}'.
MSI (s) (B0:28) [09:57:04:457]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 2205 2: 3: File
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 2205 2: 3: MsiFileHash
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 2205 2: 3: Component
MSI (s) (B0:28) [09:57:04:457]: Machine policy value 'DisablePatch' is 0
MSI (s) (B0:28) [09:57:04:457]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (B0:28) [09:57:04:457]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (B0:28) [09:57:04:457]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 2205 2: 3: Feature
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 2725
MSI (s) (B0:28) [09:57:04:457]: Note: 1: 1708
MSI (s) (B0:28) [09:57:04:457]: Produit : -- L’installation a échoué.
MSI (s) (B0:28) [09:57:04:457]: Windows Installer a installé le produit. Nom du produit : . Version du produit : . Langue du produit : . Fabricant : . Réussite de l’installation ou état d’erreur : 1603.
MSI (s) (B0:28) [09:57:04:457]: MainEngineThread is returning 1603
Erreur irrécupérable lors de l’installation.
c:\Users\emmanuel.fromentin\Desktop\MicrosoftEdgeEnterpriseX64.msi
MSI (s) (B0:D8) [09:57:04:457]: User policy value 'DisableRollback' is 0
MSI (s) (B0:D8) [09:57:04:457]: Machine policy value 'DisableRollback' is 0
MSI (s) (B0:D8) [09:57:04:457]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B0:D8) [09:57:04:457]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B0:D8) [09:57:04:457]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (B0:D8) [09:57:04:457]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (24:18) [09:57:04:457]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (24:18) [09:57:04:457]: MainEngineThread is returning 1603
=== Verbose logging stopped: 15/09/2026 09:57:04 ===
WAPT Installation
Code: Select all
Installing: MicrosoftEdgeEnterpriseX64.msi (153.0.4234.32)
MSI (s) (48:8C) [10:20:20:312]: Product: Microsoft Edge -- Installation failed.
MSI (s) (48:8C) [10:20:20:312]: Windows Installer a installé le produit. Nom du produit : Microsoft Edge. Version du produit : 153.0.4234.32. Langue du produit : 1033. Fabricant : Microsoft Corporation. Réussite de l’installation ou état d’erreur : 1603.
Traceback (most recent call last):
File "C:\Program Files (x86)\wapt\common.py", line 4534, in install_wapt
exitstatus = setup.install()
File "C:\Program Files (x86)\wapt\private\install\wapttjf_ck19\setup.py", line 65, in install
File "C:\Program Files (x86)\wapt\common.py", line 4451, in new_func
return func(*args, **kwargs)
File "C:\Program Files (x86)\wapt\setuphelpers_windows.py", line 1657, in install_msi_if_needed
run(r'"%s" /norestart /q /i "%s" /li %s %s ' % (makepath(system32(),'msiexec.exe'), msi, logfile, props), accept_returncodes=accept_returncodes, timeout=timeout, pidlist=pidlist)
File "C:\Program Files (x86)\wapt\waptutils.py", line 2423, in run
raise CalledProcessErrorOutput(proc.returncode, cmd, ''.join(output))
waptutils.CalledProcessErrorOutput: Command '"C:\\WINDOWS\\system32\\msiexec.exe" /norestart /q /i "MicrosoftEdgeEnterpriseX64.msi" /li C:\\WINDOWS\\TEMP\\tmpsm9pta90.log ' returned non-zero exit status 1603.
Output:
CalledProcessErrorOutput: Command '"C:\\WINDOWS\\system32\\msiexec.exe" /norestart /q /i "MicrosoftEdgeEnterpriseX64.msi" /li C:\\WINDOWS\\TEMP\\tmpsm9pta90.log ' returned non-zero exit status 1603.
Output:
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 2:56 PM
by x-davidl
Hello Emmanuel 64, I think it's the same as with many of my machines; it can't uninstall the old version. The .msi file is missing. Maybe the antivirus deleted it...
I found this error by forcing an Edge installation (right-click, force installation).
If you only have two, that's fine... I still have about a hundred with the same error.
I'm going to run microsoftedgesetup.exe /silent /install, which overwrites the existing version (you need at least one version difference), and forget about the Edge package for those machines. Then, at the next update, I'll update the machine package to make the Edge package reappear from WAPT.
I'm open to suggestions if you have a better solution
. Best regards.
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 3:03 PM
by Emmanuel64
Thank you for your feedback.
I spoke with WithSecure on the phone:
"The errors and reports from this are different from the initial problem and are not related. However, we also cannot confirm that this is not related to WithSecure based on the provided logs.
What we do find is that the installation finishes at 1603, and this is more likely due to corruption or another issue.
To clearly confirm whether this is related or not, I suggest you disable EDR from the profile and restart the machine. If the installation completes after this, it would confirm that it is indeed related."
I need to run some tests to try to confirm this.
I'll keep you updated.
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 3:54 PM
by sfonteneau
Emmanuel64 wrote: ↑Sep 15, 2026 - 3:03 PM
"The errors and reports from this are different from the initial problem and are not related, however we cannot confirm that this is not related to withsecure from the logs provided.
What we find is that the installation ends in 1603 and that this is more strongly a corruption/other problem.
I confirm
The problem here is different
Basically, the installation command (msiexec) returns error code 1603:
with the following log:
MSI (s) (48:8C) [10:20:20:312]: Product: Microsoft Edge -- Installation failed.
MSI (s) (48:8C) [10:20:20:312]: Windows Installer has installed the product. Product name: Microsoft Edge. Product version: 153.0.4234.32. Product language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
1603 is generic... so not enough information.
In any case, that's not a hash problem
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 4:01 PM
by Emmanuel64
Thanks sfonteneau for keeping an eye on things.
Indeed, it looks more like an installer corruption.
I have this issue on two machines with Edge and one with Chrome.
WithSecure has a built-in software updater; Edge and Chrome updates are disabled there, but perhaps it got ahead of the "early access" update.
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 5:02 PM
by Emmanuel64
As agreed, I performed tests.
On PC1, I downloaded MicrosoftEdgeEnterpriseX64.msi to the desktop, verified the SHA, disabled all "withsecure" security features, and restarted the PC. I then calculated the SHA again, with the same result. The installation fails silently in the same way, and the installation via our "WAPT" deployment software also fails.
On PC2, I downloaded MicrosoftEdgeEnterpriseX64.msi to the desktop, verified the SHA, uninstalled "withsecure," and restarted the PC. I then calculated the SHA again, with the same result. The installation fails silently in the same way, and the installation via our "WAPT" deployment software also fails.
Currently, therefore, withsecure does not appear to be directly at fault.
Re: files corrupted, SHA not matching
Published: September 15, 2026 - 6:20 PM
by dcardon
Hi Emmanuel,
I might have a lead... Today I was working on updating the tis-microsof-visual-studio-buildtools-2019 package and the installation crashed on a Windows 11 VM in our LUTI farm. After analysis, this crash was related to a side effect caused by an Edge update that was automatically launching in the background via a scheduled task (and which wasn't finishing for some unknown reason)...
Could you check if there's a MicrosoftEdgeUpdate.exe or an Edge setup.exe running in the background that might have been triggered by a scheduled task?
Best regards,
Denis
Re: files corrupted, SHA not matching
Published: September 16, 2026 - 09:35
by t.heroult
When I have installations that crash due to error 1603, in 99.99% of cases, the problem is solved as follows:
- Go to HKEY_CLASSES_ROOT\Installer\Products (or HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products, it's the same)
- Find the key that corresponds to the software
- Delete the key
- Restart the installation