Microsoft Edge Freezes When Attaching Files

[qmarsn]

Checklist

• [x] I have searched for existing issues/discussions and didn't find any similar ones.
• [x] I haven't used any other scripts, tools or programs that might have caused this issue.

Windows version

Windows 11 Pro Version 10.0.26100 Build 26100

Script mode/options

Default Mode

Describe the issue

When using Microsoft Edge to attach a file via the "attach" button on any website, the browser consistently freezes, rendering it unresponsive. This issue persists across various websites and file types, indicating a systemic problem rather than an isolated incident.

https://github.com/user-attachments/assets/49293cc2-9f9e-4c1a-9da7-9c562e9c2009

Steps to reproduce

Reproduction Steps:

1. Open Microsoft Edge.
2. Navigate to any website that has a file attachment feature (e.g., email clients, document sharing platforms).
3. Click on the "attach" button.
4. Select a file from the file explorer.
5. Observe the browser freezing, becoming unresponsive, and requiring a force quit.

Expected Behavior:

The browser should allow users to select and attach files without freezing or becoming unresponsive.

Actual Behavior:

Microsoft Edge freezes, and the user is unable to complete the file attachment process. The browser remains unresponsive until a force quit is performed.

Environment:

Operating System: Windows 11 Browser: Microsoft Edge (latest version) Debloat Script: https://github.com/Raphire/Win11Debloat/

Error output

All details included above. Please let me know if any questions.

Additional context

https://github.com/user-attachments/assets/3a127f4b-a7f1-4ee2-b789-f119246f61d4

[Raphire]

Heya, This is a strange one. Does this happen with any other browser, or when using file explorer normally, like moving files around, copy/pasting between drives?

[qmarsn]

Hey Raphy!

Hope you're doing well.

This only happens with MS-Edge and no other browser. I've tested FireFox & Chrome and both were working as expected without any issues. When I deployed the script, MS Edge started acting like this.

Is there a script to reverse the debloat action? Only reason I'm using Edge is the resource usage aspect of it. If Chrome or Firefox offered the same memory usage I would've switched long time ago but unfortunately, those two hog up a lot of resource overhead.

Thanks!

-Q

[Raphire]

Hey,

Thanks for your quick reply. Interesting that the issue is limited to just Microsoft Edge. Win11Debloat doesn't do anything related to Edge in the Default mode. So I'm not sure what to revert here, except for maybe doing a system restore through the restore point created by the script.

Could you check Event Viewer for any possible errors or warnings that could point us in the right direction.

1. Open Event Viewer by searching for it in Windows Search.
2. Open and check both the Application and System Windows Logs, highlighted red.

3. Filter the results for easier viewing. You can enter the filtering options via the option highlighted green in the image above.

4. Apply the filters to only show Critical, Error and Warning events, and click OK.

Please report back any events that may be relevant here.

In the mean time, you could try a repair via the Settings app:

1. Press Win + I to open settings.
2. Select Apps.
3. On the left pane select Apps and features.
4. Look for Microsoft Edge and click it then select Modify.
5. A windows will pop-up, click Yes.
6. Click the Repair button, follow the steps on your screen.

[Raphire]

@qmarsn Heya, do you have any updates on this? I haven't been able to reproduce this issue, more information is required to troubleshoot this.

[qmarsn]

Hi @Raphire ! So sorry for not replying back earlier to you on this. I had done a system restore and didn't perform the debloat task again but if I do and it does the same thing, I will be sure to record event viewer and get back to you with my findings.

Thanks again for all of your help!

[Raphire]

Hi @Raphire ! So sorry for not replying back earlier to you on this. I had done a system restore and didn't perform the debloat task again but if I do and it does the same thing, I will be sure to record even viewer and get back to you with my findings.

Thanks again for all of your help!

No worries @qmarsn! Thanks for reporting back. I'll leave the issue open in case anyone has more information on reproducing the issue or has a potential cause.

[Raphire]

I will be closing this issue as stale, it's unknown what the exact issue/cause was here. If anybody does encounter this in the future then please open up a new issue and reference this one :)