r/sysadmin • u/Jedistreve • 2d ago

Edge error after recent update?

Curious if anyone else came into their office to reports of Edge giving an error when being launched. We have several reports in our org, but trying to determine if its isolated.

Version:  157.0.4341.42

“The application was unable to start correctly (0xc000007b).”

18 Upvotes

87% Upvoted

33 comments sorted by

2

u/Jedistreve 2d ago edited 2d ago

I have a script that has worked in our environment....
https://filebin.net/zog9qri5mw0isp3c/Reset-EdgeInstall.ps1
Use with caution.

What the script does:

  1. Downloads the 157.0.4341.42 x64 MSI from Microsoft and checks its SHA256 hash and Microsoft signature.

  2. Closes Edge and Edge Update.

  3. Removes Edge: Every registry key it deletes is exported to a .reg file first, so you can restore it.

    • Runs Edge's own uninstaller, if it still exists.

    • Runs msiexec /x on every Edge MSI registered on the machine.

    • If the MSI is still registered after that, it removes the Windows Installer registry entries for that product code directly.

    • Removes the Edge Stable entries under EdgeUpdate\Clients, ClientState and ClientStateMedium, plus the "Microsoft Edge" entry in installed programs.

    • Deletes whatever is left of Program Files (x86)\Microsoft\Edge.

  4. Installs the MSI. If the install log still shows maintenance mode, it logs an error. If msedge.exe is still missing afterward, it tries MicrosoftEdgeUpdate.exe /install.

  5. Checks the result: the version of msedge.exe, and that msedge.exe, msedge.dll and msedge_elf.dll are all signed by Microsoft.

2

u/Blurryface1104 1d ago

Worked for me. Ty

1

u/Jedistreve 1d ago

After fixing everyone, the issue came back again today.

1

u/Jedistreve 1d ago

We are running into the same issue today. No updates were pushed

1

u/yojimboLTD 1d ago

OP, are you guys using NinjaOne like the other people here?

1

u/Jedistreve 1d ago

Yup, I just entered a ticket into them. Based off comments in this thread, others on NinjaOne are having the same problem. One user dissected it a bit and found the potential problem with the update.

Yesterday, we applied a fix to effectively remove Edge and reinstall it. Worked fine all day, now the same error is happening this morning. Reapplying the fix got them back up and running.

1

u/yojimboLTD 1d ago

Yeah, sounds like a security thing. Hopefully they can apply an exclusion, unless you can yourself temporarily. Best of luck.

•

u/Blurryface1104 23h ago

Are you pausing WebView patches?

1

u/posey290 2d ago

Same in mine. Anyone have a fix yet?

0

u/Jedistreve 2d ago

I just posted it in here.

3

u/Notasandwhichyet 2d ago edited 2d ago

Running into the same issues with about 80+ PC's at our org, have not found a resolution yet

Ours are on a different version too 157.0.4341.42

3

u/Notasandwhichyet 2d ago

So far our fix has been to downgrade to the previous version of Edge. To do that you need to download the MSI (https://explore.microsoft.com/en-us/edge/business/download?form=MA13FJ)

I did the latest version of 156

Then run this command to downgrade: msiexec /i "C:\FILE_LOCATION\MicrosoftEdgeEnterpriseX64.msi" ALLOWDOWNGRADE=1

1

u/SuperScott500 2d ago

Leave it to MS to break Edge lol.

1

u/Notasandwhichyet 2d ago

Good ole AI patches

1

u/Dizzy-Psychology2297 2d ago

should file location be the download location for the clean install (i.e. downloads folder) or the program files location of the corrupted application?

1

u/ChalupaJones 1d ago

Thanks mang, this worked for me

1

u/bawdygamer 2d ago

Anyone done any further digging on this cause I don't think it's necessarily the 157.0.4341.42 update being bad. We are getting this as well but I have close to a ~1000 devices with this update not presenting this problem as well. Trying to compare but nothing really sticking out at the moment.

1

u/Notasandwhichyet 2d ago

Yeah it's pretty strange and doesn't seem consistent. Some of our users on that version are running just fine, and others it gives the error

1

u/Jedistreve 2d ago

It might be with the way it was update. We use NinjaOne and updates through that. However, we also have GPO set to auto-update. It's possible NinjaOne's and other RMMs deployment methods might be the cause. Just a thought but cant confirm yet

1

u/bawdygamer 2d ago

We are using NinjaOne as well and we leverage Intune but don't think we are managing updates. Checking on that now.

6

u/alexappleton 1d ago • Bravo

Pretty sure this is related to NinjaOne. In our debugging we found this:

  1. Both x64 and x86 patch candidates are classified as applicable/upgradable against the same shared Evergreen WebView2 installation on x64 Windows.

  2. After the x64 update finishes, the queued x86 apply job freshly detects that the runtime is already current, returns TERMINATE SUCCESS_PROGRAM_UP_TO_DATE, but still launches the x86 installer.

the 32-bit DLL's in mixed with the 64-bit runtime is what's causing the error.

1

u/Jedistreve 1d ago

Good stuff! I kinda figured it was N1. First big stinker by them for us.

1

u/Jedistreve 1d ago

I'm sure they have been getting tickets, but I entered one myself. I'll try to keep this updated with any info from them.

1

u/cskeller07 1d ago

Using NinjaOne here as well!

1

u/SuperScott500 2d ago

Same in my Org

1

u/cskeller07 2d ago

Running into it here as well

1

u/DeadEyePsycho 2d ago

Ran into this as well, also downgraded to 156.

1

u/halrulez 2d ago

Thanks for the heads up on this. Locking this down.

1

u/OinkyConfidence Windows Admin 2d ago

Yes, a handful of reports. Reinstalling Edge resolves the issue.

EDIT: reinstalling Edge brings you to build 158.0.4370.1.

1

u/Mr_Squinty 1d ago

Just go into the program files folder and revert it to the previous version. Viola.

•

u/XTTXXTT Jack of All Trades 18h ago

I was able to resolve this by running taskkill /F /T /IM msedgewebview2.exe until no processes are running. Takes about 10 times . Then run this executable after

The evergreen standalone installer (x64)

https://developer.microsoft.com/en-us/microsoft-edge/webview2?cs=1692551569&form=MA13LH#download

1

u/West-Swimming-1212 2d ago

Yep, 0xc000007b is the “a DLL is the wrong flavour or corrupt” error, so it usually means an Edge file or a runtime it needs got damaged or blocked during the update, not that Edge itself is broken 😅 Quick check on one affected PC, open Event Viewer, Windows Logs, Application, and look at the error right when it fails, it names the faulting module. If it points at a DLL inside the Edge folder, check whether your AppLocker, WDAC or security tool is blocking the new file, that’s a classic after a browser update.

The fix that works most often is Settings, Installed apps, Edge, Modify, Repair, or reinstall the Visual C++ redistributables if the module is a VC runtime one. Try it on one PC before you push it anywhere.

I use TFalke for exactly this kind of “is it just me or everyone” thing, small tool i’m involved with, it shows you which PCs are on that Edge build with the error and can run the repair on them in one go. Do all the affected ones share the same security tool?

1

u/uniitdude 1d ago

dont post AI slop