Forum Discussion
AutoImportAtFirstRun policy not working since v97.0.1072.69
muene Hello! We just released MS Edge Stable Version 100.0.1185.29 (Microsoft Edge release notes for Stable Channel | Microsoft Docs) and it should contain the fix for the AutoImportAtFirstRun policy.
Let us know if you are still having issues. Thanks!
-Kelly
Microsoftmuene Hi! I believe the team is investigating backporting the fix. I'll follow up here once there is more information about the availability. Thanks!
-Kelly
Microsoftmuene Hello! We just released MS Edge Stable Version 100.0.1185.29 (Microsoft Edge release notes for Stable Channel | Microsoft Docs) and it should contain the fix for the AutoImportAtFirstRun policy.
Let us know if you are still having issues. Thanks!
-Kelly
Kelly_Y, our organization is unable to get the AutoImportAtFirstRun policy working on v103.0.1264.62. I tried targeting the Default Browser (IE11 and Chrome) and targeting the IE11 browser and Chrome individually. I did my testing with a fresh profile so that FirstRun was guaranteed to run.
Has there been a regression (feature broken again)?
- Works on 104.0.1293.47 I had to change the default app away from Edge to get the policy AutoImportAtFirstRun = 0 to get the default browser which I set to Chrome
I deleted the following for a first run experience every time for testing C:\Users\<username>\AppData\Local\Microsoft\Edge\User Data
What I would like is to be able to import from more than one browser on first run as in FF and Chrome at the same time automagically without input from a user
- I've confiemed that the issue is fixed in v100.0.1185.29 stable channel.
Thanks for your help.Hi,
Ok for me too.
Thank you
- Did it break again? I cannot get it to work in v102.0.1245.30
