Forum Discussion
rishavsharan
Microsoft
MicrosoftHow to hide the First Run Experience in the new Microsoft Edge?
One of the most frequent Enterprise asks around the new First Run Experience has been for a way to hide the new First Run Experience.
It could be that you do not want your users to change these con...
in V81?? Really??. i Will be killed from my Users if i wait that long with the Rollout. And there is even no Schedule for the Versions 
so i can't plan a rollout date. I hoped i could finish the Rollout on our 80 Terminalservers around Mid February
Maybe i should switch to firefox instead for my company
rishavsharanMicrosoft
MicrosoftAs far as the release schedules go, a good rule of thumb is to take the chromium release cycle and add a couple of days for us.
https://chromiumdash.appspot.com/schedule
https://chromiumdash.appspot.com/schedule
rishavsharan We are exactly in the same situation as mentioned in this thread. We realy need to push out Edge as the default browser in our company (a large hospital). But we realy need to get rid off the first run.
According to https://chromiumdash.appspot.com/schedule a stable release for version 80 was yesterday? Is that correct? So we can expect a download link within a few days for version 80 (Stable) right?We are in the same situation: we are using the stable Edge 79 version with the AutoAutoImportAtFirstRun option on a small group of machines, and I was waiting for version 80 which incorporates the deactivation of the first experience. So we were ready to deploy Edge 80 on all of our 2,500 machines, but AutoAutoImportAtFirstRun no longer works ... I don't understand that successive beta versions of the 80 have not corrected this problem, and we are now told to wait for version 81 ?! Is there not a possible workaround (registry)?
I deployed v79 without the Policy to hide FirstRunExperience and used a PowerShell-Script to preconfigure EdgeChromium-FirstRunExperience.ps1
you find my Script here:
https://github.com/gunnarhaslinger/Microsoft-Edge-based-on-Chromium-Scripts
Maybe this can help you out.
As far as the release schedules go, a good rule of thumb is to take the chromium release cycle and add a couple of days for us.
https://chromiumdash.appspot.com/schedulerishavsharan Which date do you mean? The "Stable Release" or "Stable Release (Chrome OS)" date? Can we expect to get something like this Chromiums-Release-Schedule for EdgeChromium in the near future to plan on-prem-Deployment-Cycle?
- rishavsharan
@josh_bodner
if there is no own public calender i would be happy about a rule. like 7 days after chromium stable release for example
So you want to say me i have to wait another 1.5 month for rollout. 2 month delay.
I dont know if that will be possible.
