Grmbl ...

I was too fast: the changes I mentioned work for a _single_ word (which is
supposedly being regarded as a(n HTTP) server name), but not for two or more
(those still go to bing).

I've now been searching both the registry and the web for a few hours, and
have not come anywhere near to discovering how to change (and by it possibly
disable) the search provider/engine for the _file_ explorer (most of the
results are related to several kinds of webbrowsers). Neither has it
turned up anything in regard to which program/dll actually contains the
"search provider" (so I can possibly "attack" it from that angle).

Does anyone have an idea ?

Regards,
Rudy Wieser


-- Origional message:
"R.Wieser" wrote in message
news
Hey JJ,

The shell use below registry path to get the default URL prefix (i.e.
protocol).


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\URL\DefaultPrefix

Thanks. By appending the "no place like home" IP I've re-routed the
search to a place it cannot do any harm, and I can possibly even catch it
to return an appropriate "web page" for the attempt.

Not quite _disabled_ , but the possible the next-best thing. :-)

They're stored in below registry.


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\FindExtensions

Before posting here I found that GUID too. But when I googled it all I
got was 5 pages with 'how to fix a problem with ...' results. :-(

I've just tried to block access to the GUID (either prefixing it, or the
registry key its mentioned in, with an exclamation mark, but I still got
the "websearch" option, and it still tried to seach bing*

*I found an "SearchAssistant" entry and inserted a 127.0.0.1/ by which I
can, just as with #1, tell if a certain change is effective or not. It
also effectivily blocks the request, but doesn't remove the option (hence
the "crude" I mentioned earlier)...

Thanks for the response.

Regards,
Rudy Wieser


-- Origionalo message:
"JJ" wrote in message
news
On Fri, 8 Sep 2017 15:01:32 +0200, R.Wieser wrote:
Hello all,

#1: I would like to know if there is a way to stop file-explorer of
trying
to go online when something is entered in the adressbar it does not
recognise.

AFAIK, the Windows shell is hardcoded to treat typed text as an URL if
it's
not a valid application file searchable from the PATH environment
variable
or a file in the current working directory. The shell use below registry
path to get the default URL prefix (i.e. protocol).


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\URL\DefaultPrefix

When I check it with Process Monitor, it doesn't try to read any setting
after trying to find application-specific path (i.e. "App Paths"
registry)
and before trying to access the above URL registry. Neither Explorer
policy
setting or plain Explorer setting. That is, at least for the Windows 7's
shell.

#2: I would also like to remove the 'websearch' option thats made
available
when you, from the file-explorer, select "find".

They're stored in below registry.


HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\FindExtensions

If've _blocked_ both using very crude methods (registry editing
involved),
but would very much like to know how to do it the "clean" way.

Start by searching the above registry key. If MSDN doesn't have it,
chances
are that you can only find unofficial ways to remove them.

And a funny thing: #1 goes to google, #2 goes to bing. :-) :-(

IMO, it depends on the Find handler as specified in the above registry.
MSDN
*should* have an official documentations for that.