Has anyone experienced issues with Edge blocking favorite imports after an update?

0
29
Asked By TechieTraveler42 On

We've encountered a problem in our enterprise where users are unable to import favorites into Microsoft Edge after the latest update to version 142. This used to work smoothly; we'd export favorites to a file and then import them across different workstations and profiles. However, now when users click 'choose file', the option is disabled. We adhere to DISA STIG settings, and while we have importing browser history and data disabled, I compared it with an older version (Edge 140) and everything operated just fine. The issue seems to have arisen with the latest update, possibly linking the import feature to the disabled GPO policy. Has anyone faced a similar situation or found any useful documentation related to this change?

2 Answers

Answered By ITFixer99 On

We're facing the same issue here. Our CIS policies prevent any data imports into Edge, yet the conflicting policies seem to allow imports too. With this update, importing functionality has been completely broken. To regain the ability to import, we’ve found we have to completely delete any policies managing import settings from the registry. It’s frustrating, especially since we’re in the middle of a system migration. For a temporary fix, I’ve applied a version control in our update policies.

HelpfulTech123 -

For us, manually transferring the Bookmarks file from the local app data directory to the new machine has worked as a stopgap measure. Another quirky workaround involves using developer tools to remove the 'disabled' attribute from the button itself! It seems like Microsoft might have messed up this update.

Answered By SysAdminGuru91 On

In our setup, it looks like something broke between the updates from version 142.0.3595.90 to 142.0.3595.94 regarding the favorite import feature. I noticed that the user interface for version x.90 isn't quite the same as in x.94, which might indicate Microsoft is making some adjustments that have caused this. Interestingly, the .94 version isn’t even listed as part of the stable release on Microsoft’s official documentation, so something definitely seems off.

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.