That's weird!
Although I chose Google, Edge is using Bing to do web searches.
*Version 78.0.245.0 (Official build) canary (64-bit)
I manually added the Google search engine...
Both URLs http://www.google.com.br/search?q=%s
and https://encrypted.google.com/search?q=%s works,
although I don't know which is the correct default
@Deleted
I do not use google. However, I tried to repro your issue & cannot. Changed to google, address bar searches immediately > Google. Change back to Bing, they immediately > Bing.
Cheers,
Drew
@Deleted I just got this issue as well with 78.0.245.0. As soon as I told Edge to restart to finish updating it started happening. I've tried removing all search engines, going back to google doing a search there so it shows up as a option in Edge again and it still uses bing when I use the address bar to search. Not a huge deal, I know to expect problems since I'm on the canary branch. Just wanted to make sure it wasn't just me.
Edit: Going into settings and adding Google search manually using this url
https://encrypted.google.com/search?q=%s
Gets it working again for me, so I'll just use that workaround for now.
@sean8102 @Deleted
Ooops, I should read more slowly. I think I had checked this in Dev not, Canary. Yes, in Canary when set to google it 'says' or looks like it's going to use google, but, does, still, use Bing. Good I prefer Bing, anyway. Obviously, it is something the Team needs to correct. I have submitted this to Mr. Smiley & urge others to follow suit.
Cheers,
Drew
@Deleted
Same issue. Canary. Selecting Google (Default) searches Bing, even though my entry looks correct, but look at the icon next to Google (it's Bing's icon):
Manually adding does work for me as well (even seems to fix the "bad" Google entry).
@Keith Davis
(Suggest) There is something worth noticing here. There are 3 beta channels (well, there will be 3 soon). Canary is the most like to have issues. And here we have a problem in Canary which, does not exist in Dev. It's this kind of scenario where running more than one track can be interesting. Sure should be reported as needing to be corrected in Canary, even though, it, already, does not need to be corrected in Dev.
Cheers,
Drew
@Keith Davis
I may not have worded what I'd written very well. The issue is in Canary, but, NOT in Dev. Meaning, it seemed interesting that was ok in Dev yet messed up back in Canary. In other words, in regard to your point, no bug seems to be 'carrying over' because, Dev does not have the issue. Or, it's a wee bit surprising finding something ok in Dev whilst awry back in Canary. I trust this is written more clearly than before.
And, I can certainly appreciate (1st hand), there are reasons why we IT Pros & Developers are drawn to particular beta levels; or more than one track.
Cheers,
Drew
@Keith Davis
Maybe, it's me, then that has or had it backwards & it will surface in Dev with the next Dev update, if they don't fix it first, of course. Either way, good we find & report things.
Cheers,
Drew
Yea, it's fixed and now I see that this is just a favicon, as I had to use it once for it to change.
If someone deleted Google Search Engine (like me), just add a new engine with these parameters:
Name: Google
Keyword: google.com
URL: {google:baseURL}search?q=%s&{google:RLZ}{google:acceptedSuggestion}{google:originalQueryForSuggestion}{google:assistedQueryStats}{google:searchFieldtrialParameter}{google:searchClient}{google:sourceId}{google:instantExtendedEnabledParameter}ie={inputEncoding}
The above huge URL is the "official" one (I suppose 
), but these two also work:
1) http://www.google.com.br/search?q=%s
2) https://encrypted.google.com/search?q=%s
Accepted Solutions