Help! Can’t Update or Remove Edge Due to Corruption

0
21
Asked By TechNinja47 On

I'm dealing with a frustrating situation on several Windows 11 machines where Microsoft Edge is corrupted, and I can't update or uninstall it. Here's everything I've tried so far:

- MSI repair using the '/fa' switch, but it failed with error 1605.
- Tried uninstalling via the '/x' switch, but still got error 1605.
- Used the Edge setup.exe with options '--uninstall --force-uninstall --system-level,' which failed with error 93.
- Conducted manual cleanup of the registry and file system, but that didn't help either.
- Tried looking up the Product GUID and targeted uninstall, but it didn't work.
- Various MSI logging parameters indicated corruption but didn't provide a fix.
- Even tried terminating processes before running the operations, with no luck.
- Experimented with different combinations of the Edge setup.exe parameters, all resulting in error 93.

Currently, I can still use a manual executable installer, but it doesn't support silent switches, which is a hassle since I have hundreds of machines affected. The MSI database seems corrupted (1605 errors), and the Edge setup.exe doesn't accept standard uninstall parameters (error 93). Any advice would be greatly appreciated!

2 Answers

Answered By CleanSlateHero On

Honestly, wiping the PC and doing a fresh install might be the quickest fix. Sometimes it’s just not worth the hassle when you have so many systems affected!

SkepticalTechie -

I get your point, but considering OP mentioned hundreds of computers, a wipe would be way too time-consuming. Plus, the EXE installer works, so there’s definitely an easier workaround here. I'm more curious about how this problem even started on such a large scale. Has anyone else experienced similar issues with Edge?

Answered By DebugWizard99 On

You might want to try running `msiexec.exe /x msi.msi /L*V logpath.txt` to generate a detailed log file. The error 1605 usually means the original MSI is missing, so check under `ComputerHKEY_LOCAL_MACHINESOFTWAREClassesInstallerProducts` to see if you can find the source lists. I faced a similar issue with a WSL installation and had to delete a specific key to fix it.

Related Questions

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.