none
Microsoft Edge will not start after installing November Update RRS feed

  • Question

  • Been trying Windows 10 on domain connected PC at work, things were OK until I installed the November update.

    Now when clicking Edge it appears very briefly then disappears without any error message. Same for the News and Money apps.

    Realized local accounts had no problem with these apps, so I deleted local copy of roaming profile  and deleted network copy of profile to reset to new user status.

    First login everything works OK but once logged out and back in again and the problem reappears.

    Using 2k8R2 domain controller

    Any help?

    Monday, November 16, 2015 9:18 PM

Answers

  • Regarding my original problem, there is a reply to another thread

    https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs?forum=win10itprogeneral

    That clears the problem on my system

    We're seeing the same issue here on a Win2008/R2 domain.  On Workstations with the 1511 update, users with roaming profiles cannot launch Edge, Cortana, Xbox, Bing News, Bing Money, Bing Sports.  Deleting the local app folder and re-adding it with powershell gets them going again.  However, the very next login, they'll be back to the same non-functional state.
    
    We did find another more persistent fix.  You'd have to repeat this process on each workstation the user logs in on but it might help some people in some scenarios.
    1.Use the advanced system settings to delete the roaming user profile from the affected workstation.
    2.Log in as that user to create a fresh, new copy of the roaming profile
    3.Verify Edge & other Win10 Bing apps work
    4.Before you logout for the first time, open regedit add add full control rights for ALL APPLICATION PROFILES on the HKCU\SOFTWARE\Classes key.  Apply the security change, then on the advanced security dialog, check the "Replace all child object permissions with inheritable permission entries from this object".  It will probably report that some items couldn't be updated.  That seems to be OK.
    
    There may be some collateral damage from this but we haven't seen it yet.  Unfortunately this isn't a great fix for us as our users do actually roam on a few machines and this fix has to be applied on each machine the first time they log in :(
    

    This may provide a clue as to what is going wrong.

    Regarding opencl.dll, I did notice there is also a copy in a nVidia folder on my laptop so maybe they are being replaced when video drivers are installed/updated? But I too think this is not related to my original issue.

    • Marked as answer by P Crowther Thursday, December 10, 2015 9:17 AM
    Wednesday, November 25, 2015 4:53 PM

All replies

  • That's unfortunate.

    Try a Clean Boot first.

    Use DISM Command:

    I) Press Windows + x on your keyboard.

    ii) Select Command prompt (Admin) to open Administrator Command Prompt .

    iii) In the Administrator: Command Prompt window, type the following commands. Press the Enter key after each command:
         dism.exe /online /cleanup-image /scanhealth
         dism.exe /online /cleanup-image /restorehealth

    Use sfc /scannow

    a. Click on Start button and type cmd in search box.

    b. Right-click on Command Prompt and select Run as administrator.

    c. Type the following command and hit Enter.

    sfc /scannow


    S.Sengupta, Windows Experience MVP

    Tuesday, November 17, 2015 12:45 AM
  • Hi,

    please search in this Forum for

    windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs

     (i can not insert links)


    I think it is a bug in Windows 10.

    Tuesday, November 17, 2015 9:52 AM
  • I can:

    https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs?forum=win10itprogeneral

    I've be hanging off us upgrading to Windows 10 until at least the "service pack" so built a test VM yesterday with clean install of v1511 and clean profile. Hit this bug immediately.

    Rob.

    Tuesday, November 17, 2015 10:03 AM
  • Thanks guys nice to know I am not alone.
    Tuesday, November 17, 2015 3:48 PM
  • @ S.Sengupta

    Thanks for your suggestions.

    Tried Clean Boot but made no difference.

    Tried DISM commands:

    dism.exe /online /cleanup-image /scanhealth completed successfully with the message "The component store is repairable"

    dism.exe /online /cleanup-image /restorehealth failed with the message Error 0x800f081f "The source files could not be found"

    Looking in the dism.log I see the lines:

    2015-11-18 12:43:57, Error                 DISM   DISM Package Manager: PID=2728 TID=6008 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f081f)
    2015-11-18 12:43:57, Error                 DISM   DISM Package Manager: PID=2728 TID=6008 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2015-11-18 12:43:57, Error                 DISM   DISM Package Manager: PID=2728 TID=6008 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f081f)
    2015-11-18 12:43:57, Error                 DISM   DISM Package Manager: PID=2728 TID=6008 The source files could not be found; their location must be specified using the /source option to restore the feature. - GetCbsErrorMsg
    2015-11-18 12:43:57, Error                 DISM   DISM Package Manager: PID=2728 TID=6008 Failed to restore the image health. - CPackageManagerCLIHandler::ProcessCmdLine_CleanupImage(hr:0x800f081f)
    2015-11-18 12:43:57, Error                 DISM   DISM Package Manager: PID=2728 TID=6008 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f081f)

    But I do not know the meaning of this.

    Is this relevant to my problem?

    Wednesday, November 18, 2015 12:57 PM
  • Looking in the dism.log I see the lines:

    2015-11-18 12:43:57, Error 

    Now look in the CBS.log (or the relevant archived portion of it) for the related messages at or before that time.


    Robert Aldwinckle
    ---

    Thursday, November 19, 2015 5:07 AM
  • Robert thanks for the reply.

    Looked in the CBS.log and the corrupt files is "opencl.dll"

    CBS    Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
    CBS    Exec: Clients specified using Windows Update.
    CBS    WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
    CBS    DWLD:Search is done, set download progress to 20 percent.
    CBS    Nothing to download, unexpected
    CBS    Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]

    (p) CSI Payload Corrupt wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
    Repair failed: Missing replacement payload.

    I appear to be failing to download the replacement file from the Microsoft Update service.

    Thursday, November 19, 2015 10:37 AM
  • Looked in the CBS.log and the corrupt files is "opencl.dll"

    If it is only that one file you could try finding it somewhere else and copying it there.  Apparently it links to  SysWOW64

    PS>LS -Re -Fi opencl.dll -Fo -Ea SilentlyContinue | sort LastWriteTime | ft Length, FullName -AutoSize Length FullName ------ -------- 103944 C:\WINDOWS\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll 103944 C:\WINDOWS\SysWOW64\opencl.dll 99856 C:\WINDOWS\System32\OpenCL.DLL 34816 C:\WINDOWS\System32\DriverStore\FileRepository\rdvgwddmdx11.inf_amd64_c43edca0d0f250bb\opencl.dll 34816 C:\WINDOWS\WinSxS\amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf2a87752df0d7\opencl.dll

    PS>fsutil hardlink list $env:windir\SysWow64\opencl.dll
    \Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
    \Windows\SysWOW64\opencl.dll


    I'd be curious to know if you had one in SoftwareDistribution, for example.



    Robert Aldwinckle
    ---


    Thursday, November 19, 2015 1:59 PM
  • Interestingly when I run the same command I see different file sizes 

    PS C:\> LS -Re -Fi opencl.dll -Fo -Ea SilentlyContinue | sort LastWriteTime | ft Length, FullName -AutoSize
    
    Length FullName
    ------ --------
      8914 C:\Windows.old\Windows\WinSxS\amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10240.16384_none_db4a03dd6584084a\opencl.dll
      7762 C:\Windows.old\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10240.16384_none_b928dea146e73395\opencl.dll
     69120 C:\Windows\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
     69120 C:\Windows.old\Windows\SysWOW64\OpenCL.DLL
     69120 C:\Windows\SysWOW64\opencl.dll
     72704 C:\Windows\System32\OpenCL.DLL
     72704 C:\Windows.old\Windows\System32\OpenCL.DLL
     34816 C:\Windows\WinSxS\amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf2a87752df0d7\opencl.dll
     34816 C:\Windows\System32\DriverStore\FileRepository\rdvgwddmdx11.inf_amd64_c43edca0d0f250bb\opencl.dll

    Thursday, November 19, 2015 3:15 PM
  • Interestingly when I run the same command I see different file sizes 

    Yeah, so since the checksum is supposed to be the same, yours is probably truncated.  The CBS.log may confirm that guess.  Can you get a full size copy from somewhere else?  Too bad that DISM isn't working.  This is what it is supposed to help with.  Otherwise you can try to find the appropriate .msu package to download, expand, extract and install manually.  JoscCon has some tips about such workarounds...

    Somewhere!  (I couldn't find what I wanted to show you but the comments here seem relevant to your case, both this one and the last page of this thread.)

    http://blogs.technet.com/b/joscon/archive/2012/09/26/fixing-component-store-corruption-in-windows-8-and-windows-server-2012.aspx#pi47623=4 

    <quote>
    Unfortunately, a lot of CSI based issues aren't repairable without a repair install.
    </quote>

    Good luck



    Robert Aldwinckle
    ---

    Thursday, November 19, 2015 6:30 PM
  • I have a laptop at home that I have also been testing Windows 10 on. It hasn't been going too smoothly so I thought I would download a new copy of the USB install for 1511, wipe my hard drive and start again from scratch. I could then use this as a source for the opencl.dll to repair my work computer which was a clean install of the RTM version back when it was released and then a recent upgrade to 1511.

    Interestingly I now see exactly the same problem when running the DISM commands on this separate computer with a fresh clean install of 1511, but with a file size of 105080.

    Are all Microsoft's current install images corrupt or is there some other explanation why this fails?

    Sunday, November 22, 2015 11:10 AM
  • Interestingly I now see exactly the same problem when running the DISM commands on this separate computer with a fresh clean install of 1511, but with a file size of 105080.

    So now it's too big? 

    Heh.  Mine has changed too.  Bigger.

    PS>cd $env:windir
    PS>LS -Re -Fi opencl.dll -Fo -Ea "SilentlyContinue" | sort LastWriteTime | ft Length, FullName -AutoSize
    
    Length FullName
    ------ --------
    103944 C:\WINDOWS\WinSxS\wow64_microsoft-windows-r..xwddmdriver-wow64-c_31bf3856ad364e35_10.0.10586.0_none_3dae054b56911c22\opencl.dll
    103944 C:\WINDOWS\SysWOW64\opencl.dll
     99856 C:\WINDOWS\System32\OpenCL.DLL
     34816 C:\WINDOWS\System32\DriverStore\FileRepository\rdvgwddmdx11.inf_amd64_c43edca0d0f250bb\opencl.dll
     34816 C:\WINDOWS\WinSxS\amd64_rdvgwddmdx11.inf_31bf3856ad364e35_10.0.10586.0_none_5fcf2a87752df0d7\opencl.dll
    

    but the (supposed) checksum is the same? How can this be?  Also, how is it that the 64-bit version is smaller, though it too is bigger than it was?

    Maybe DISM is giving us a red herring to chase.  Then we should go back to your original symptom...  Oh.  I didn't respond to that initially.  FWIW I would be using ProcMon  to supplement that "disappears without any error message" observation.  You could filter with Operation Begins with Proc to focus your analysis near where it would have happened.

     

    HTH



    Robert Aldwinckle
    ---

    Sunday, November 22, 2015 5:00 PM
  • Heh.  Mine has changed too.  Bigger.

    The VM's has changed again but now I see it is somehow related to RemoteFX, so I may try uninstalling Hyper-V in my host OS and see if that changes the report that  sfc  /verifyonly  gives.

    C.f.

    http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_install/corrupt-opencldll-need-windows-10-build-10586/90908ce2-a52b-4efc-9331-5383c1ebe70e#LastReply

    But I still can't imagine that this has anything to do with Edge not being able to open.   <eg>




    Robert Aldwinckle
    ---

    Wednesday, November 25, 2015 4:36 PM
  • Regarding my original problem, there is a reply to another thread

    https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs?forum=win10itprogeneral

    That clears the problem on my system

    We're seeing the same issue here on a Win2008/R2 domain.  On Workstations with the 1511 update, users with roaming profiles cannot launch Edge, Cortana, Xbox, Bing News, Bing Money, Bing Sports.  Deleting the local app folder and re-adding it with powershell gets them going again.  However, the very next login, they'll be back to the same non-functional state.
    
    We did find another more persistent fix.  You'd have to repeat this process on each workstation the user logs in on but it might help some people in some scenarios.
    1.Use the advanced system settings to delete the roaming user profile from the affected workstation.
    2.Log in as that user to create a fresh, new copy of the roaming profile
    3.Verify Edge & other Win10 Bing apps work
    4.Before you logout for the first time, open regedit add add full control rights for ALL APPLICATION PROFILES on the HKCU\SOFTWARE\Classes key.  Apply the security change, then on the advanced security dialog, check the "Replace all child object permissions with inheritable permission entries from this object".  It will probably report that some items couldn't be updated.  That seems to be OK.
    
    There may be some collateral damage from this but we haven't seen it yet.  Unfortunately this isn't a great fix for us as our users do actually roam on a few machines and this fix has to be applied on each machine the first time they log in :(
    

    This may provide a clue as to what is going wrong.

    Regarding opencl.dll, I did notice there is also a copy in a nVidia folder on my laptop so maybe they are being replaced when video drivers are installed/updated? But I too think this is not related to my original issue.

    • Marked as answer by P Crowther Thursday, December 10, 2015 9:17 AM
    Wednesday, November 25, 2015 4:53 PM
  • Perhaps very much related...

    click here

    Wednesday, November 25, 2015 6:15 PM
  • Obviously the Problem does still occur in build 10586.104:

    http://answers.microsoft.com/en-us/windows/forum/windows_10-performance/win-10-1511-post-upgrade-issues-start-cortana-edge/7d2af4ef-3dda-4261-8b41-471eb343094b?page=9


    • Edited by rd4711 Thursday, February 11, 2016 2:10 PM
    Thursday, February 11, 2016 2:08 PM
  • This issue has been fixed in Build 14279. In case (some of) your roaming profiles were already affected by this issue, a PowerShell script has to be executed in order to solve the issue for that profile.

    NOTE: Build 14279 is really needed to get rid of the issue. Simply running the PowerShell script is not enough if you're on a previous build.


    Sunday, March 6, 2016 4:22 AM
  • Has anybody already tested these problems with the latest build 10586.218, which was deployed last night as KB3147458?
    Wednesday, April 13, 2016 12:54 PM
  • On May 11th MS published another update - one day after the cumulative update for Windows 10 Version 1511 which increments the build number to 10586.318 (check with winver.exe).

    The new update is KB3152599 and the description seems to solve these problems:  https://support.microsoft.com/en-us/kb/3152599

    Nevertheless, I have not tried if it really fixes the problem. Has anybody else already done the test?


    Kind regards,

    Robert.


    • Edited by rd4711 Thursday, May 12, 2016 6:26 AM
    Thursday, May 12, 2016 6:25 AM
  • Obviously the issues are still not fixed in Anniversary Update 1607.

    Actually I am still struggling with roaming profiles and Windows 10 1607. To reproduce:

    • Log on with a clean user with no server-side roaming profile
    • Log out to upload the profile
    • Log on with local admin rights and delete the local roaming profile cache in system settings
    • re-login with the roaming-profile user

    The result is still that some apps crash right after startup (often now even the settings app crashes) and startmenu is entirely broken:

    • Random app crashes; right after launching the app they close
    • Start menu crashes when power button is pressed
    • Cortana crashes
    • Settings buton does not appear in start menu
    • Application tiles neither re-created from scratch nor roamed, the start menu tiles are just randomly appearing

    I found this page and will try to include the script provided in the logon scripts trying to fix registry permissions but I think I need to tweak it as also start menu app, cortana and others are affected.

    Microsoft seems to be unwilling or unable to fix the issue and even declares this bug as "by design".

    Thursday, August 18, 2016 7:54 AM
  • I found this page and will try to include the script provided in the logon scripts trying to fix registry permissions but I think I need to tweak it as also start menu app, cortana and others are affected.

    Thanks for the link, which propagates to more insight about the roaming profile issue.  Especially interesting to me then were the symptoms involving Edge and Cortana.  One thing I wondered about that was not covered anywhere in there is what diagnostics people were getting for their "crash" symptoms.  The only related thing I saw was a suggestion to leave writes to the "Application Event Log" commented out. But what about using (PowerShell cmdlet) Get-AppXLog (or better, e.g. as indicated in any relevant Events log entries) for clues?


    Robert Aldwinckle
    ---

    Thursday, August 18, 2016 12:54 PM