You type the name of a file on your own PC, and the Start menu goes off to ask the internet first. This guide removes Bing from Windows Search the way the video does it — one registry script — so search answers locally, instantly, and only with your own apps, files and settings.
This is the complete written version of the fix from the video: disable Bing inside Windows Search so the Start menu stops mixing web results with local ones. You will see what the registry script actually changes, what improves the moment it applies — and, just as important, the honest boundary of the fix. If your search is slow because the index underneath is broken, this page tells you that plainly and points you at the right repair.
Open the Start menu and type the name of a file that is sitting on your own desktop. Windows finds it — but not instantly, and not alone. The result list mixes your apps, files and settings with web results from Bing: suggested searches, web links, and sometimes pictures and news. Those web entries are not stored on your PC. They are fetched over the internet while you type, which means the search box is quietly doing two jobs at once — a local search against an index on your disk, and a live web query that has to travel out and back.
On a fast connection the delay is small. On a slow office line, a weak Wi-Fi signal, or a metered connection, the web half stalls the whole panel, and results keep shuffling as late web entries land. Worse, the thing you actually wanted — your own file — can end up below web clutter you never asked for. That is the complaint in the video: a search that should be offline and instant has been made online and slow.
The video solves this with a custom one-click registry script that disables Bing integration in Windows Search, so the Start menu answers from your PC only. Underneath, the script applies the well-known policy value that controls this behaviour:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\ExplorerDisableSearchBoxSuggestions — a DWORD set to 1BingSearchEnabled set to 0 under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Search — current builds read the policy value above, which is why the script uses it.The script is linked from the video page and the video description — always download scripts like this from the creator's own link, never from a random "free registry fix" site, and create a restore point first. Any registry change deserves that two-minute safety net.
Search becomes local only: apps, files, folders and settings, ranked by the index on your disk. Nothing in the panel needs the internet, so results stop reshuffling, the panel opens with the same speed offline as online, and a slow connection can no longer hold your own files hostage. On an office PC there is a second benefit IT engineers notice straight away — staff stop clicking web links when they were hunting for an internal file or the company app.
Be honest about what this does not do. It does not make your disk index bigger or healthier, it does not fix a corrupt search database, and it does not speed up the local half of search if that half was already broken. If search stays slow with web results gone, the problem was never Bing — it is the index, and the companion guides on this page cover the rebuild, the indexing scope, and the full reset. Treat Bing removal and index health as two separate repairs, because they are.
See the registry script applied live and the search panel before and after — the complete demo, step by step.
▶️ Watch Full VideoYes. It changes one documented policy value, DisableSearchBoxSuggestions, which tells the search box not to show web suggestions and web results. Your files, apps and settings are untouched, nothing is uninstalled, and deleting the value or setting it to 0 restores the original behaviour completely.
No, and any guide promising that is overselling it. It removes the internet round-trip and the web clutter from the Start search panel, so that panel answers faster and stays stable. It does not speed up boot time, apps, games, or a local search index that is itself damaged — that needs an index rebuild, which is a separate fix.
Yes. The video covers both, and the script applies the policy value current builds of Windows 10 (version 2004 and later) and Windows 11 both read. On very old Windows 10 builds the older BingSearchEnabled value was the equivalent switch.