Opening and reading PDF files in Microsoft Edge on Windows 10
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
This is a dup thread for one that was started in 2020. Same stuff is still happening. I'm about 5 minutes from uninstalling Edge. If my PC reboots, Edge takes over PDFs. So annoying
Opening and reading PDF files in Microsoft Edge on Windows 10
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
This is not a helpful response. I have gone through these motions literally **hundreds** of times, and Edge keeps taking over PDFs from Acrobat. Something else is going on with Windows and Edge, and I have yet to see Microsoft acknowledge it.
I have also tried a number of other suggestions about how I can reset the default app from Edge to Acrobat, and none of them stick. Windows eventually works around them and makes Edge the default app. Sometimes this happens several times per day, almost always when I'm working with PDF files I downloaded from another party's Sharepoint site.
A helpful response would address the problem, not the symptom.
This worked for me, thanks a lot!!!
No. This does not work at all.
Not working for me. Edge is repairing, but the default file app is refusing to change from Edge to what I would like.
😥
My MSEdge is a Windows app. Is that the reason?
We are also using Roaming Profiles that the get loaded for every RDS user session and deleted from the RDS server again on logout.
The issue in this case is that the Windows Explorer treats every user a a new one and takes actions to initialize the profile (despite the roaming profile being actually loaded).
One can see this in the Microsoft-Windows-Shell-Core/AppDefaults event log.
We have this group policy enabled to prevent this behaviour:
| Do not reinitialize a pre-existing roamed user profile when it is loaded on a machine for the first time | Windows Components\File Explorer |
|---|
Up to at least Server 2012R2 ithad the desired effect. But since Server 2022 (maybe earlier) this policy seems to be ignored by Windows Explorer. This is the root cause of the issue.
To work around, we simply cleared all associations from the exported C:\DefaultAssociations.xml before importing it again. (We are manging the desired associations with the "Set a default associations configuration file" group policy.)