Known Issue – Microsoft Edge Launching on Startup

%3CLINGO-SUB%20id%3D%22lingo-sub-1457853%22%20slang%3D%22en-US%22%3EKnown%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1457853%22%20slang%3D%22en-US%22%3E%3CP%3EGreetings%20Insiders%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJoin%20us%20in%20gathering%20information%20about%20a%20new%20issue%20that%20our%20team%20is%20investigating.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20we%20know%20so%20far%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe've%20heard%20from%20our%20community%20that%20some%20versions%20of%20Microsoft%20Edge%20are%20automatically%20launching%20whenever%20users%20start%20their%20PCs%20and%20log%20into%20Windows%2C%20regardless%20of%20their%20selection%20in%20edge%3A%2F%2Fsettings%2FonStartup.%20It%E2%80%99s%20currently%20unknown%20whether%20there%20are%20any%20accompanying%20behavioral%20changes%20with%20this%20bug.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20this%20is%20something%20that%20you're%20experiencing%20with%20Microsoft%20Edge%2C%20we%20want%20to%20know%20in%20the%20comments%20below!%20And%20if%20you%E2%80%99d%20like%20to%20roll%20up%20your%20sleeves%20and%20start%20the%20debugging%20process%20with%20us%2C%20we%E2%80%99d%20love%20your%20assistance.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20to%20help%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETo%20help%20our%20devs%20understand%20and%20address%20this%20as%20quickly%20as%20possible%2C%20we%20ask%20that%20you%20kindly%20share%20diagnostic%20data%20through%20our%20secure%20in-browser%20feedback%20tool.%20So%2C%20if%20you're%20familiar%20with%20your%20device%E2%80%99s%20command%20prompt%2C%20please%20run%20the%20following%20steps%20to%20create%20and%20submit%20additional%20log%20files.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3EOpen%20the%20command%20prompt%20from%20an%20Admin%20account%20%E2%80%93%20Press%20the%20Windows%20key%20then%20type%20in%20%E2%80%9Ccmd%E2%80%9D%20or%20%E2%80%9Ccommand%20prompt%E2%80%9D%20into%20the%20search.%20You%E2%80%99ll%20see%20a%20black%20window%20open.%3CP%3E%26nbsp%3B%3C%2FP%3EEnable%20Logging%26nbsp%3B%E2%80%93%20run%20these%20two%20commands%20(hint%3A%20the%20second%20is%20one%20line)auditpol.exe%20%2Fset%20%2Fsubcategory%3A%22Process%20Creation%22%20%2Ffailure%3Aenable%20%2Fsuccess%3Aenable%20reg%20add%20HKLM%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CPolicies%5CSystem%5CAudit%20%2Fv%20ProcessCreationIncludeCmdLine_Enabled%20%2Ft%20REG_DWORD%20%2Fd%200x1%20%2Ff%3CP%3E%26nbsp%3B%3C%2FP%3ESave%20all%20open%20files%2C%20Reboot%20your%20PC%20and%20log%20in%26nbsp%3B%3CP%3E%26nbsp%3B%3C%2FP%3ECreate%20and%20Save%20the%20log%20file%26nbsp%3B%E2%80%93%20Open%20Powershell%20as%20an%20admin%20and%20run%20the%20following%20commandGet-WinEvent%20-FilterHashTable%20%40%7BLogName%3D%22Security%22%3B%20ID%3D%224688%22%7D%20%7C%20fl%20%26gt%3B%20c%3A%5Cusers%5Cedgelogfile.txt%3CP%3E%26nbsp%3B%3C%2FP%3EOpen%20the%20feedback%20tool%20and%20attach%20the%20file%26nbsp%3Bc%3A%5Cusers%5Cedgelogfile.txt%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA.%20Open%20the%20feedback%20tool%20by%20holding%20down%20the%20keys%20Shift%2BAlt%2BI%2C%20or%20by%20navigating%20through%20the%20%22%E2%80%A6%22%20menu%20%26gt%3B%20Help%20and%20feedback%20%26gt%3B%20Send%20feedback.%3C%2FP%3E%3CP%3EB.%20In%20the%20pop-up%2C%20please%20ensure%20that%20%22Send%20diagnostic%20data%22%20is%20checked%3C%2FP%3E%3CP%3EC.%20To%20attach%20a%20file%2C%20click%20the%20diagnostic%20date%20hyperlink*%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E*Note%3A%20some%20users%20may%20see%20a%20different%20version%20of%20the%20tool%20that%20has%20a%20second%20button%20at%20the%20bottom%20for%20adding%20attachments%20directly%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ED.%20In%20the%20next%20feedback%20window%2C%20select%20%22Attach%20a%20file%2C%22%20then%20%22Choose%20file%20to%20upload%22%3C%2FP%3E%3CP%3EE.%20After%20attaching%20c%3A%5Cusers%5Cedgelogfile.txt%2C%20click%20%22Save%20and%20include%22%3C%2FP%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EF.%20Then%20back%20in%20the%20first%20window%2C%20be%20sure%20to%20hit%20%22Send%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E6.%20Clean%20up%26nbsp%3B-%20from%20an%20Admin%20Command%20Prompt%20run%20these%20three%20commands%26nbsp%3B%3C%2FP%3Eauditpol.exe%20%2Fset%20%2Fsubcategory%3A%22Process%20Creation%22%20%2Ffailure%3Adisable%20%2Fsuccess%3Adisable%20reg%20delete%20HKLM%5CSoftware%5CMicrosoft%5CWindows%5CCurrentVersion%5CPolicies%5CSystem%5CAudit%20%2Fv%20ProcessCreationIncludeCmdLine_Enabled%20%2Ff%20del%20%2Ff%20c%3A%5Cusers%5Cedgelogfile.txt%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20your%20help.%20We%20look%20forward%20to%20hearing%20from%20you!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20The%20Microsoft%20Edge%20Product%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1461133%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1461133%22%20slang%3D%22en-US%22%3E%3CP%3E1.%20What%20would%20the%20settings%20in%20edge%3A%2F%2Fsettings%2FonStartup%20have%20to%20do%20with%20this%20at%20all%3F%3CBR%20%2F%3E2.%20Wouldn't%20this%20simply%20be%20from%20the%20Windows%20setting%20for%20automatically%20restarting%20apps%20on%20logon%20(under%20Accounts%20-%26gt%3B%20Sign-in%20options)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1461149%22%20slang%3D%22en-US%22%3ERe%EF%BC%9A%20%E5%B7%B2%E7%9F%A5%E9%97%AE%E9%A2%98%20%E2%80%93%20%E5%BE%AE%E8%BD%AF%E8%BE%B9%E7%BC%98%E5%90%AF%E5%8A%A8%E5%90%AF%E5%8A%A8%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1461149%22%20slang%3D%22en-US%22%3E%3CP%3E%E6%88%91%E5%9C%A8%E6%98%A8%E5%A4%A9%E9%81%87%E5%88%B0%E4%BA%86%E8%BF%99%E4%B8%AA%E6%83%85%E5%86%B5%EF%BC%8C%E4%BD%86%E7%9B%AE%E5%89%8D%E5%B0%9A%E4%B8%8D%E6%98%8E%E7%A1%AE%E4%B8%BA%E4%BB%80%E4%B9%88%E4%BC%9A%E8%BF%99%E6%A0%B7%E3%80%82%3C%2FP%3E%3CP%3EWindows%E7%89%88%E6%9C%AC%EF%BC%9A18363.900%3C%2FP%3E%3CP%3Eedge%E7%89%88%E6%9C%AC%EF%BC%9A%3CSPAN%3E%E7%89%88%E6%9C%AC%2085.0.538.0%20(%E5%AE%98%E6%96%B9%E5%86%85%E9%83%A8%E7%89%88%E6%9C%AC)%20dev%20(64%20%E4%BD%8D)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%E6%88%91%E4%BC%9A%E5%9C%A8%E4%B8%AD%E5%8D%88%E8%BF%9B%E8%A1%8C%E6%97%A5%E5%BF%97%E6%8F%90%E4%BA%A4%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1467938%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1467938%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3B%26nbsp%3Bbugs%20316808%20-%20%5BWCTAP%5D%20Build%2019624%3A200502%20-%20after%20the%20update%20of%20the%20machine%20Edge%20is%20keeping%20opening%20and%20closing%20by%20itself%20I%20have%20raised%20this%20issue%20in%20connect%20portal.%20Will%20upload%20the%20details%20in%20the%20portal%20with%20extended%20logging%20enabled%20and%20once%20the%20issue%20reappear%20..%20for%20me%20it%20happen%204-5%20times%20during%20the%20work%20time%20%2C%20not%20only%20at%20the%20cold%20boot%20and%20login%20(that%20time%20it%20happen%20for%20sure)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1468173%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1468173%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3BHave%20you%20rule%20out%20the%20users%20enabling%20%22Restart%20Apps%22%20under%20%22Sign-in%20options%22%3F%20because%20it%20sounds%20exactly%20like%20someone%20enabled%20the%20option%20hence%20Edge%20restart%20itself%20when%20you%20login%20to%20Windows.%20I%20actually%20had%20the%20opposite%20of%20the%20problem.%20I%20had%20the%20option%20enabled%20but%20it%20doesn't%20restart%20edge%20every%20single%20time%2C%20only%203-4%20times%20out%20of%2010.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1469591%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1469591%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F701046%22%20target%3D%22_blank%22%3E%40megablue%3C%2FA%3E%26nbsp%3BI%20have%20the%20same%20problem%3A%20Edge%20doesn't%20always%20launch%20automatically.%20In%20my%20case%2C%20I%20have%20multiple%20instances%20of%20Edge%20Canary%20running%20at%20the%20same%20time%20-%20the%20windows%20are%20distributed%20across%20two%20monitors.%20Once%2C%20two%20windows%20normally%20side%20by%20side%20were%20relaunched%20one%20on%20top%20of%20the%20other.%20Another%20time%2C%20Edge%20Canary%20had%20not%20restarted%20automatically%20after%20a%20reboot.%20When%20I%20launched%20Edge%2C%20I%20got%20only%20one%20instance%20with%20a%20message%20telling%20me%20that%20Edge%20had%20not%20shut%20down%20properly%20and%20asking%20me%20if%20I%20wanted%20to%20restore%20those%20instances.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1470735%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1470735%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3BI%20observed%20this%20behavior%20in%20default%20browsers%20like%20Internet%20Explorer%20and%20Legacy%20Microsoft%20Edge.%20The%20workaround%20was%20opening%26nbsp%3B%3CSTRONG%3ESettings%3C%2FSTRONG%3E-%26gt%3B%3CSTRONG%3EAccounts-%26gt%3BSign-in%20options%26nbsp%3B%3C%2FSTRONG%3Eand%20under%20%3CSTRONG%3EPrivacy%3C%2FSTRONG%3E%20%2C%20there%20is%20option%20called%20%3CSTRONG%3EUse%20my%20sign-in%20info%20to%20automatically%20finish%20setting%20up%20my%20device%20and%20reopen%20my%20apps%20after%20an%20update%20or%20restart%20%3C%2FSTRONG%3Eand%20we%20could%20turn%20it%20off%20and%20then%20we%20observe%20this%20problem%20won't%20reproduce.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAs%20I%20investigate%2C%20I%20observed%20that%20when%20user%20close%20down%20Internet%20Explorer%20or%20Microsoft%20Edge%2C%20it%20still%20running%20in%20background%20and%20has%20some%20session%20and%20even%20after%20shutdown%2C%20system%20assumes%20Internet%20Explorer%20was%20running%20and%20therefore%20when%20user%20turn%20on%20PC%2C%20they%20observe%20this%20behavior.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20recommend%20check%20this%20option%20and%20see%20if%20turn%20it%20off%20would%20solve%20the%20issue%20and%20if%20yes%2C%20it%20probably%20was%20the%20issue%20I%20observed%20in%20Legacy%20Microsoft%20Edge%20and%20Internet%20Explorer.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1476315%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1476315%22%20slang%3D%22en-US%22%3EIf%20anyone%20out%20there%20confirms%20if%20this%20fixes%20the%20issue%20for%20them%3F%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1479670%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1479670%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F316442%22%20target%3D%22_blank%22%3E%40NicolSD%3C%2FA%3E%26nbsp%3Bi%20found%20the%20fix%2C%20disallow%20Edge%20from%20keeping%20the%20background%20process%20solved%20the%20issues%20for%20me.%20Even%20on%20Chromium%2FChrome%2C%20the%20background%20process%20kind%20of%20not%20working%20reliably.%20It%20frequently%20treats%20the%20background%20process%20as%20last%20closed%20window%20hence%20forgetting%20the%20tabs%20that%20were%20opened%20when%20you%20closed%20your%20main%20browsing%20window%20or%20in%20this%20case%2C%20windows%20think%20it%20wasn't%20%22running%22%20when%20you%20shutdown%20because%20the%20background%20process%20were%20ended%20last.%20hence%2C%20when%20it%20reopens%20during%20a%20restart%2C%20it%20reopens%20only%20the%20background%20process.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1488598%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1488598%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3BI%20hate%20to%20state%20the%20obvious%2C%20but%20can't%20Microsoft's%20own%20tools%20help%20here%20to%20trace%20up%20the%20process%20tree%20to%20find%20out%20which%20process%20is%20starting%20msedge.exe%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20Autoruns%20by%20SysInternals%20might%20show%20what%20is%20autostarting%20it%3F%3C%2FP%3E%3CP%3E2)%20Failing%20that%2C%20can't%20you%20use%20SysInternal's%20Process%20Explorer%20to%20see%20what%20the%20parent%20process%20of%20msedge%20is%2C%20and%20trace%20through%20that%20what%20process%20started%20it%20(going%20up%20the%20process%20tree)%3F%20(Or%20Process%20Hacker%20or%20other%20similar%20tools)%3F%3C%2FP%3E%3CP%3E3)%20Alternatively%20Process%20Monitor%20and%2For%20SysMon%20by%20SysInternals%20can%20be%20configured%20to%20monitor%20processes%20starting%20up%2C%20and%20that%20can%20of%20course%20be%20setup%20to%20run%20during%20boot%20etc.%20to%20catch%20an%20early%20process%20launch%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMike%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1503378%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1503378%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F484598%22%20target%3D%22_blank%22%3E%40fawkes%3C%2FA%3E%26nbsp%3BInfo%3A%20This%20is%20only%20a%20problem%20with%20chromium%20it%20self%2C%20not%20Edge.%20When%20I%20was%207%2C%20I%20had%20this%20problem%20in%202017%20when%20I%20unwillingly%20installed%20chromium.%20I%20showed%20it%20to%20my%20mom%2C%20and%20she%20did%20not%20know%20what%20to%20do.%20We%20now%20know%20where%20the%20issue%20is%20coming%20from%2C%20Chromium%2C%20the%20source%20of%20New%20Edge%2C%20so%20we%20need%20to%20fi%3CFONT%20color%3D%22%23000000%22%3Ex%26nbsp%3B%3CSTRONG%3EChromium%2C%3C%2FSTRONG%3E%20not%26nbsp%3B%3CFONT%20color%3D%22%230000FF%22%3EEd%3CFONT%20color%3D%22%2300FF00%22%3Ege.%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1516334%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Issue%20%E2%80%93%20Microsoft%20Edge%20Launching%20on%20Startup%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1516334%22%20slang%3D%22en-US%22%3Ewell%20it%20is%20fine%20after%20turning%20that%20thing%20you%20mentioned%20(from%20win%2010%20build%202004)%20off%20%3D)%3C%2Fimg%3E%3CBR%20%2F%3Eproblem%20solved%3C%2FLINGO-BODY%3E
Highlighted
Microsoft

Greetings Insiders,

 

Join us in gathering information about a new issue that our team is investigating.

 

 

What we know so far

 

We've heard from our community that some versions of Microsoft Edge are automatically launching whenever users start their PCs and log into Windows, regardless of their selection in edge://settings/onStartup. It’s currently unknown whether there are any accompanying behavioral changes with this bug.

 

If this is something that you're experiencing with Microsoft Edge, we want to know in the comments below! And if you’d like to roll up your sleeves and start the debugging process with us, we’d love your assistance.

 

 

How to help

 

To help our devs understand and address this as quickly as possible, we ask that you kindly share diagnostic data through our secure in-browser feedback tool. So, if you're familiar with your device’s command prompt, please run the following steps to create and submit additional log files.  

 

  1. Open the command prompt from an Admin account – Press the Windows key then type in “cmd” or “command prompt” into the search. You’ll see a black window open.

 

  1. Enable Logging – run these two commands (hint: the second is one line)
auditpol.exe /set /subcategory:"Process Creation" /failure:enable /success:enable
 
reg add HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Audit /v ProcessCreationIncludeCmdLine_Enabled /t REG_DWORD /d 0x1 /f

 

  1. Save all open files, Reboot your PC and log in 

 

  1. Create and Save the log file – Open Powershell as an admin and run the following command
Get-WinEvent -FilterHashTable @{LogName="Security"; ID="4688"} | fl > c:\users\edgelogfile.txt

 

  1. Open the feedback tool and attach the file c:\users\edgelogfile.txt

 

A. Open the feedback tool by holding down the keys Shift+Alt+I, or by navigating through the "…" menu > Help and feedback > Send feedback.

B. In the pop-up, please ensure that "Send diagnostic data" is checked

C. To attach a file, click the diagnostic date hyperlink*

fawkes_0-1591920302443.png

 

*Note: some users may see a different version of the tool that has a second button at the bottom for adding attachments directly

 

D. In the next feedback window, select "Attach a file," then "Choose file to upload"

E. After attaching c:\users\edgelogfile.txt, click "Save and include"

fawkes_1-1591920302446.png

 

F. Then back in the first window, be sure to hit "Send"

 

6. Clean up - from an Admin Command Prompt run these three commands 

auditpol.exe /set /subcategory:"Process Creation" /failure:disable /success:disable
 
reg delete HKLM\Software\Microsoft\Windows\CurrentVersion\Policies\System\Audit /v ProcessCreationIncludeCmdLine_Enabled /f
 
del /f c:\users\edgelogfile.txt

 

Thanks for your help. We look forward to hearing from you!

 

- The Microsoft Edge Product Team

11 Replies
Highlighted

1. What would the settings in edge://settings/onStartup have to do with this at all?
2. Wouldn't this simply be from the Windows setting for automatically restarting apps on logon (under Accounts -> Sign-in options)?

Highlighted

我在昨天遇到了这个情况,但目前尚不明确为什么会这样。

Windows版本:18363.900

edge版本:版本 85.0.538.0 (官方内部版本) dev (64 位)

我会在中午进行日志提交

Highlighted

@fawkes  bugs 316808 - [WCTAP] Build 19624:200502 - after the update of the machine Edge is keeping opening and closing by itself I have raised this issue in connect portal. Will upload the details in the portal with extended logging enabled and once the issue reappear .. for me it happen 4-5 times during the work time , not only at the cold boot and login (that time it happen for sure)

Highlighted

@fawkes Have you rule out the users enabling "Restart Apps" under "Sign-in options"? because it sounds exactly like someone enabled the option hence Edge restart itself when you login to Windows. I actually had the opposite of the problem. I had the option enabled but it doesn't restart edge every single time, only 3-4 times out of 10.

Highlighted

@megablue I have the same problem: Edge doesn't always launch automatically. In my case, I have multiple instances of Edge Canary running at the same time - the windows are distributed across two monitors. Once, two windows normally side by side were relaunched one on top of the other. Another time, Edge Canary had not restarted automatically after a reboot. When I launched Edge, I got only one instance with a message telling me that Edge had not shut down properly and asking me if I wanted to restore those instances.

Highlighted

@fawkes I observed this behavior in default browsers like Internet Explorer and Legacy Microsoft Edge. The workaround was opening Settings->Accounts->Sign-in options and under Privacy , there is option called Use my sign-in info to automatically finish setting up my device and reopen my apps after an update or restart and we could turn it off and then we observe this problem won't reproduce.

 

As I investigate, I observed that when user close down Internet Explorer or Microsoft Edge, it still running in background and has some session and even after shutdown, system assumes Internet Explorer was running and therefore when user turn on PC, they observe this behavior.

 

I recommend check this option and see if turn it off would solve the issue and if yes, it probably was the issue I observed in Legacy Microsoft Edge and Internet Explorer.

Highlighted
If anyone out there confirms if this fixes the issue for them??
Highlighted

@NicolSD i found the fix, disallow Edge from keeping the background process solved the issues for me. Even on Chromium/Chrome, the background process kind of not working reliably. It frequently treats the background process as last closed window hence forgetting the tabs that were opened when you closed your main browsing window or in this case, windows think it wasn't "running" when you shutdown because the background process were ended last. hence, when it reopens during a restart, it reopens only the background process.

Highlighted

@fawkes I hate to state the obvious, but can't Microsoft's own tools help here to trace up the process tree to find out which process is starting msedge.exe?

 

1) Autoruns by SysInternals might show what is autostarting it?

2) Failing that, can't you use SysInternal's Process Explorer to see what the parent process of msedge is, and trace through that what process started it (going up the process tree)? (Or Process Hacker or other similar tools)?

3) Alternatively Process Monitor and/or SysMon by SysInternals can be configured to monitor processes starting up, and that can of course be setup to run during boot etc. to catch an early process launch?

 

Mike

Highlighted

@fawkes Info: This is only a problem with chromium it self, not Edge. When I was 7, I had this problem in 2017 when I unwillingly installed chromium. I showed it to my mom, and she did not know what to do. We now know where the issue is coming from, Chromium, the source of New Edge, so we need to fiChromium, not Edge.

Highlighted
well it is fine after turning that thing you mentioned (from win 10 build 2004) off =)
problem solved