and Edge crash on start if customer use Roaming Profile (Win10 1511)

Fixed Issue #6098167

Details

Created
Jan 7, 2016
Privacy
This issue is public.
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

URL:

Repro Steps:

  1. IE11 Reset, IE11 crash on start after next reboot
  2. Reinstall Windows 10 1511 and install all required Applications, User log on, reboot, IE11 crash on start
  3. Reinstall Windows 10 1511 and install NO Applications, User log on, reboot, IE11 crash on start
  4. Reinstall Windows 10 1511 and install NO Applications, Remove profile from server, User log on and a blank profile was created, reboot, IE11 crash on start
  5. Reinstall Windows 10 1511 and install NO Applications, Disable all GPO’s, User log on, reboot, IE11 crash on start
  6. Reinstall Windows 10 1511 and install NO Applications, Create a new User with Roaming Profile, New User log on, reboot, IE11 crash on start
  7. Reinstall Windows 10 1511 and install NO Applications, Create a new User with Roaming Profile, New User log on, switch Roaming-profile to Local-profile,Reboot, reboot, IE11 crash on start
  8. Reinstall Windows 10 1511 and install NO Applications, Create a new User with local profile, New User log on, reboot, jippiehh…IE11 and Edge is functioning normally
  9. Reinstall Windows 10 1511 and install all required Applications, User with local profile log on, reboot, IE11 and Edge is functioning normally

Please see the following link for more details and workaround

https://connect.microsoft.com/IE/feedback/details/2031419/ie11-and-edge-crash-on-start-if-customer-use-roaming-profile-win10-1511

Expected Results:

I can open and use the IE11 or Edge App

Actual Results:

Dev Channel specific:

No

Attachments

0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Sermet I.”

      Changed Assigned To from “Sermet I.” to “IE S.”

      Changed Status to “Not reproducible”

      Changed Assigned To to “Ted D.”

      Changed Status from “Not reproducible”

      Changed Assigned To to “Bruce M.”

      Changed Assigned To from “Bruce M.” to “Ross H.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Ross H.” to “IE S.”

      Changed Status from “Confirmed” to “Fixed”

    • It strikes me as extremely odd that Microsoft is not addressing this issue in the currently available builds for productive use.

      I’d love to finally roll out Windows 10 in our company, but our 50 computers all run on roaming profiles and as long as there is no Hotfix, there won’t be an upgrade to Windows 10 in our company!

      The issue was fixed a long time ago in the Insider Preview. Microsoft, when will you deliver?

    • This issue has been resolved: https://support.microsoft.com/en-us/kb/3144319?sd=rss&spid=18165
      Experiences are that this fix will not always work for running systems and when you use your own reference builds it might only completely work when Windows will release a new production build 1607, soon to come (current branch servicing).

      Original support thread for me:
      https://social.technet.microsoft.com/Forums/en-US/fd436515-6423-4015-9afe-d7e6034909ab/windows-10-threshold-2-edgesearch-issues-for-domain-joined-pcs

    • And I believe the exact build this is fixed is 14279.
      Your company is still on 10586 I guess?

      https://blogs.windows.com/windowsexperience/2016/03/04/announcing-windows-10-insider-preview-build-14279/

    • Arien,

      I just upgraded 10 computers to Windows 10 10586.318 using the MediaCreator, an ISO file I created today with it and letting the setup.exe search for recent updates.

      On ALL 10 computers Edge was broken and needed additional troubleshooting. On one computer not even the workaround fixed the issue. I am still troubleshooting the issue two hours later.

      In my eyes the issue has NOT been resolved! How do you even call this a fix if the official statement is that "that this fix will not always work for running systems"? This is ridiculous.

      It does not help that “the exact build this is fixed is 14279” because I refuse to install an Insider Preview on production computers. Although I could take that into consideration as 10586 with it’s broken Edge browser doesn’t feel any better than a preview build.

      I understand that bugs happen and I assume fixing bugs is not a trivial thing and needs to run through testing, QA, more testing and other various stages until it can be deployed. And I assume this takes a lot of time. But I do consider roaming profiles a widely implemented feature within business environments and this issue straightforwardly makes Windows unusable.

      My opinion on this matter has not changed. You aggressively force the Windows 10 upgrade but do not provide a reasonable working system.

      Daniel

    You need to sign in to your Microsoft account to add a comment.

    Sign in