News, tips, advice, support for Windows, Office, PCs & more. Tech help. No bull. We're community supported by donations from our Plus Members, and proud of it
Home icon Home icon Home icon Email icon RSS icon
  • IE 11 may go nuts if you don’t have Default Search Provider specified

    Posted on June 6th, 2019 at 01:48 woody Comment on the AskWoody Lounge

    Here’s a weird one.

    At this moment – the middle of the night, US time – Microsoft lists a bug in many Win10 versions, but if you look for details about which patches may have introduced the bug, there’s no mention that I can find.

    Here’s the problem, as explained on the Release Information page:

    June 2019

    opening Internet Explorer 11 may fail

    Internet Explorer 11 may fail to open if Default Search Provider is not set or is malformed.
    Affected platforms:
    • Client: Windows 10, version 1809; Windows 10 Enterprise LTSC 2019; Windows 10, version 1803; Windows 10, version 1709; Windows 10, version 1703; Windows 10 Enterprise LTSC 2016; Windows 10, version 1607
    • Server: Windows Server 2019; Windows Server 2016
    Workaround: To set the Default Search Provider, use the following steps:
    1. Open an Administrator Command prompt and type the following: “C:\Program Files\Internet Explorer\iexplore.exe” http://microsoft.com
    2. After Internet Explorer has opened, go to the Settings menu and select Manage add-ons.
    3. Select Search Providers in left pane.
    4. Select the link Find more search providers in the bottom left of the dialog.
    5. A new Internet Explorer window should open, allowing you to select a search provider.
    6. Select Add under the Search Provider you prefer.
    7. The Add Search Provider dialog should open, select Add.
    8. You should now be able to open Internet Explorer 11 normally.
    Next steps: We are working on a resolution and estimate a solution will be available in mid-June.

    Got that?

    You might wonder, as I did, which patch(es) cause the problem — or if it’s a problem that’s affected all versions of Win10 since the early days. You might also wonder if Win10 1903 is affected.

    Looking at the individual patch listings, I don’t see this particular bug mentioned anywhere.

    Two possible conclusions: Either the patch docs are screwed up again — or this is a bug in Win10/IE 11 that’s been around, and not reported, since version 1607.