Group policy to disable the "Welcome to the new Microsoft Edge" dialog from FirstRun wizard

%3CLINGO-SUB%20id%3D%22lingo-sub-1068359%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068359%22%20slang%3D%22en-US%22%3ESame%20to%20us.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068381%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068381%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F467665%22%20target%3D%22_blank%22%3E%40csrswalch%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYes%20please.%3C%2FP%3E%3CP%3EAnother%20scenario%20is%20VDI%20where%20the%20VM%20is%20destroyed%20and%20redeployed%20as%20soon%20as%20the%20user%20logs%20off.%3C%2FP%3E%3CP%3EThe%20VDI%3As%20do%20have%20public%20access%20and%20they%20are%20used%20for%20banking%2C%20social%20security%20and%20government%20interaction%20so%20we%20need%20to%20be%20100%25%20sure%20they%20are%20%22clean%22%20for%20the%20next%20user%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068773%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068773%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F467665%22%20target%3D%22_blank%22%3E%40csrswalch%3C%2FA%3E%26nbsp%3BFull%20ACK.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1068987%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1068987%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F467665%22%20target%3D%22_blank%22%3E%40csrswalch%3C%2FA%3E%26nbsp%3Balso%20looking%20for%20this.%20I'm%20testing%20in%20a%20Citrix%20environment.%20I%20had%20to%20add%20an%20inclusion%20in%20Citrix%20for%20the%20EdgeBeta%20user%20directory%20so%20it%20would%20save%20the%20first%20run%20having%20been%20applied%20already.%20So%20any%20subsequent%20launches%20do%20not%20show%20it%20even%20after%20logging%20off%20and%20back%20on%20again.%20I%20do%20wish%20I%20could%20prevent%20it%20for%20brand%20new%20users%20as%20well%20though.%20So%20far%20nothing%20I've%20found%20or%20tried%20has%20been%20able%20to%20disable%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1069798%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1069798%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F467665%22%20target%3D%22_blank%22%3E%40csrswalch%3C%2FA%3E%26nbsp%3Bwe%20are%20looking%20for%20something%20similar%20as%20it's%20driving%20me%20crazy%20with%20our%20local%20roaming%20profiles%20on%20our%20domain.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1076070%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1076070%22%20slang%3D%22en-US%22%3E%3CP%3EI%20already%20reported%20this%20in%20October%202019%2C%20see%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FEnterprise%2FEdge-v78-asks-User-on-first-start-which-New-Tab-Design-to-choose%2Fm-p%2F909174%22%20target%3D%22_blank%22%20rel%3D%22noopener%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FEnterprise%2FEdge-v78-asks-User-on-first-start-which-New-Tab-Design-to-choose%2Fm-p%2F909174%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBut%20no%20response%20yet.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20figured%20out%20how%20this%20%22First%20Run%20Experience%22%20ist%20triggered%3A%3C%2FP%3E%3CP%3EIn%20the%20Edge%20UserProfile%20there%20is%20a%20file%20%22Local%20state%22%20which%20is%20as%20JSON%20formatted%20Settings-File.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20setting%20%22has_user_seen_fre%22%20has%20to%20be%20true%2C%20if%20not%20existent%20or%20false%20the%20First%20Run%20Experience%20is%20shown.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20prevent%20the%20First-Run-Experience%20I%20create%20an%20empty%20Edge-Userprofile%20just%20Containing%20a%20almost%20empty%20%22Local%20state%22%20file%2C%20just%20having%20this%20one%20setting%20in%20it.%20This%20solution%20is%20ugly%20but%20works.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EAs%20there%20is%20no%20Solution%20provided%20by%20Microsoft%2C%20I%20created%20a%20Script%20(as%20a%20workaround).%20I%20published%20it%20here%3A%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fgithub.com%2Fgunnarhaslinger%2FMicrosoft-Edge-based-on-Chromium-Scripts%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgithub.com%2Fgunnarhaslinger%2FMicrosoft-Edge-based-on-Chromium-Scripts%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1087142%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1087142%22%20slang%3D%22en-US%22%3EI%20too%20would%20like%20a%20policy%20to%20disable%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092271%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092271%22%20slang%3D%22en-US%22%3EHi%20everyone%3CBR%20%2F%3E%3CBR%20%2F%3EI%20am%20a%20PM%20in%20the%20Edge%20team%20and%20I%20am%20happy%20to%20say%20that%20we%20are%20currently%20working%20on%20this%20very%20policy.%20While%20I%20can't%20give%20a%20hard%20timeline%2C%20we%20should%20be%20good%20to%20release%20it%20in%20the%20next%20couple%20of%20months.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092473%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092473%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317109%22%20target%3D%22_blank%22%3E%40rishavsharan%3C%2FA%3E%26nbsp%3BThat%20is%20good%20news%2C%20thanks.%20Whilst%20looking%20at%20GPOs%2C%20could%20you%20take%20a%20look%20at%20this%20issue%20please%3F%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fenterprise%2Fnew-tab-logo-gpo%2Fm-p%2F1087949%23M724%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fenterprise%2Fnew-tab-logo-gpo%2Fm-p%2F1087949%23M724%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1092584%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1092584%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F493736%22%20target%3D%22_blank%22%3E%40LBXComputers%3C%2FA%3E%2C%20Thanks.%20I%20have%20taken%20a%20bug%20on%20this%20and%20notified%20the%20appropriate%20team.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1114590%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1114590%22%20slang%3D%22en-US%22%3EHow%20are%20we%20looking%20for%20this%20with%20the%20recent%20release%20of%20the%20stable%20version%20of%20Edge%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1114721%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1114721%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F491253%22%20target%3D%22_blank%22%3E%40itsupportBH%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAccording%20to%20the%20docs%20the%20policy%20is%20slated%20for%20a%20realease%20in%20version%2080%2C%20stable%20is%20version%2079%20so%20we%20probably%20have%20to%20wait%20for%20the%20first%20update%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CH4%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%20id%3D%22toc-hId--738278282%22%3EHide%20the%20First-run%20experience%20and%20splash%20screen%3C%2FH4%3E%3CBLOCKQUOTE%3E%3CP%3ESupported%20Versions%3A%20Microsoft%20Edge%20on%20Windows%20and%20Mac%20since%20version%2080%20or%20later%3C%2FP%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23hidefirstrunexperience%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fdeployedge%2Fmicrosoft-edge-policies%23hidefirstrunexperience%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1114910%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1114910%22%20slang%3D%22en-US%22%3E%3CP%3ENice%20sleuthing.%20%3AD%3C%2Fimg%3E%3CBR%20%2F%3EThe%20current%20plan%20is%20to%20push%20it%20out%20in%20E80%20stable.%20We%20are%20on%20track%20so%20far.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20should%20be%20able%20to%20test%20it%20right%20now%20in%20Beta%2FDev%20and%20Canary%20channels%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1136841%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1136841%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F317109%22%20target%3D%22_blank%22%3E%40rishavsharan%3C%2FA%3E%26nbsp%3BI'd%20like%20to%20deploy%20this%20setting%20using%20Endpoint%20Manager%2C%20is%20there%20any%20idea%20on%20when%20this%20is%20being%20deployed%3F%20The%20article%20above%20seems%20to%20mention%20only%20ADMX%20and%20reg%20key%20settings.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1137179%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1137179%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F433672%22%20target%3D%22_blank%22%3E%40JornMich%3C%2FA%3E%26nbsp%3BI%20don't%20think%20the%20policy%20has%20any%20effect%20on%20any%20version%20below%2080.%20I%20tried%20the%20reg%20key%20settings%20and%20only%20the%20Beta%20Edge%20honored%20the%20%22HideFirstRunExperience%22%20reg%20value.%20Stable%20build%20does%20not%20honor%20this%20setting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1272096%22%20slang%3D%22en-US%22%3ERe%3A%20Group%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20w%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1272096%22%20slang%3D%22en-US%22%3E%3CP%3EIt%20works%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22Stefan_Moser_0-1585774538155.png%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F181374i885FB3870AE72ECD%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20title%3D%22Stefan_Moser_0-1585774538155.png%22%20alt%3D%22Stefan_Moser_0-1585774538155.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1067325%22%20slang%3D%22en-US%22%3EGroup%20policy%20to%20disable%20the%20%22Welcome%20to%20the%20new%20Microsoft%20Edge%22%20dialog%20from%20FirstRun%20wizard%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1067325%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20chance%20you%20could%20provide%20a%20group%20policy%20to%20hide%20the%20FirstRun%20Get%20Started%20dialog%3F%20In%20a%20managed%20environment%20it's%20largely%20redundant%2C%20or%20at%20least%20will%20be.%20Also%20more%20often%20then%20not%20these%20changes%20are%20communicated%20internally.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOur%20customer%20site%20is%20heavily%20locked%20down%20via%20group%20policy%2C%20using%20automatic%20AAD%20sign%20in%20and%20sync%2C%20importing%20all%20existing%20settings%20from%20Internet%20Explorer%3B%20so%20the%20FirstRun%20experience%20is%20largely%20seamless%20which%20is%20great.%20Removing%20that%20extra%20click%20and%20allowing%20customers%20to%20get%20straight%20into%20the%20browser%20is%20what%20we're%20after%20-%20no%20doubt%26nbsp%3Bthe%20majority%20of%20your%20enterprise%20customers%20would%20appreciate%20having%20the%20ability%20to%20manage%20this%20setting%20too.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20and%20keep%20up%20the%20great%20work!%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Any chance you could provide a group policy to hide the FirstRun Get Started dialog? In a managed environment it's largely redundant, or at least will be. Also more often then not these changes are communicated internally.

 

Our customer site is heavily locked down via group policy, using automatic AAD sign in and sync, importing all existing settings from Internet Explorer; so the FirstRun experience is largely seamless which is great. Removing that extra click and allowing customers to get straight into the browser is what we're after - no doubt the majority of your enterprise customers would appreciate having the ability to manage this setting too.

 

clipboard_image_0.png

 

Thanks and keep up the great work!

15 Replies
Highlighted
Highlighted

@csrswalch 

 

Yes please.

Another scenario is VDI where the VM is destroyed and redeployed as soon as the user logs off.

The VDI:s do have public access and they are used for banking, social security and government interaction so we need to be 100% sure they are "clean" for the next user

Highlighted
Highlighted

@csrswalch also looking for this. I'm testing in a Citrix environment. I had to add an inclusion in Citrix for the EdgeBeta user directory so it would save the first run having been applied already. So any subsequent launches do not show it even after logging off and back on again. I do wish I could prevent it for brand new users as well though. So far nothing I've found or tried has been able to disable it.

Highlighted

@csrswalch we are looking for something similar as it's driving me crazy with our local roaming profiles on our domain.

Highlighted

I already reported this in October 2019, see: https://techcommunity.microsoft.com/t5/Enterprise/Edge-v78-asks-User-on-first-start-which-New-Tab-De... 

 

But no response yet.

 

I figured out how this "First Run Experience" ist triggered:

In the Edge UserProfile there is a file "Local state" which is as JSON formatted Settings-File. 

 

The setting "has_user_seen_fre" has to be true, if not existent or false the First Run Experience is shown.

 

To prevent the First-Run-Experience I create an empty Edge-Userprofile just Containing a almost empty "Local state" file, just having this one setting in it. This solution is ugly but works.

 

As there is no Solution provided by Microsoft, I created a Script (as a workaround). I published it here: https://github.com/gunnarhaslinger/Microsoft-Edge-based-on-Chromium-Scripts

 

Highlighted
I too would like a policy to disable this.
Highlighted
Hi everyone

I am a PM in the Edge team and I am happy to say that we are currently working on this very policy. While I can't give a hard timeline, we should be good to release it in the next couple of months.
Highlighted
Highlighted
@LBXComputers, Thanks. I have taken a bug on this and notified the appropriate team.
Highlighted
How are we looking for this with the recent release of the stable version of Edge?
Highlighted

@itsupportBH 

According to the docs the policy is slated for a realease in version 80, stable is version 79 so we probably have to wait for the first update:

 

Hide the First-run experience and splash screen

Supported Versions: Microsoft Edge on Windows and Mac since version 80 or later

https://docs.microsoft.com/en-us/deployedge/microsoft-edge-policies#hidefirstrunexperience

Highlighted

Nice sleuthing. :D
The current plan is to push it out in E80 stable. We are on track so far.

 

You should be able to test it right now in Beta/Dev and Canary channels

Highlighted

@rishavsharan I'd like to deploy this setting using Endpoint Manager, is there any idea on when this is being deployed? The article above seems to mention only ADMX and reg key settings.

Highlighted

@JornMich I don't think the policy has any effect on any version below 80. I tried the reg key settings and only the Beta Edge honored the "HideFirstRunExperience" reg value. Stable build does not honor this setting.