Default Browser for a Link in Windows: How to Open a Site in a Browser Other Than the System Default

Браузер по умолчанию для url в Windows

Quick answer
Windows has no built-in way to set a different default browser per link — only one default for the whole system. The workaround: build a .lnk shortcut whose target isn’t the site itself, but the browser’s exe with the URL as a parameter. Doing this by hand takes five minutes through shortcut properties. Doing it for a dozen links, and for coworkers who won’t touch shortcut properties, needs a tool. Below I cover both the manual approach and my own utility, Browser Shortcut Creator, which does the same thing in one click.
Содержание: показать

1. The Problem

You set a default browser for a link in Windows — and suddenly every link in the system, from Outlook to Telegram, opens in that one browser. Sound familiar?

Here’s what it looked like for me. The corporate portal needs Edge with an AD profile — otherwise SSO breaks and you’re typing your password for the third time. Personal mail and everything else goes to Chrome, because that’s where the extensions and bookmarks live. Online banking goes into a separate «clean» browser with zero extensions, because who knows what some rogue DevTools extension might poke at. And a layout tester needs the same URL opened in four browsers at once, from four different shortcuts, without picking a browser manually every time.

Windows just doesn’t do this. There’s exactly one «default browser» slot in the system, shared across every link. Want Edge for the corporate portal and Chrome for everything else? You either flip the system default back and forth constantly, or find a workaround.

In this article:

  • why Windows’ built-in settings can’t solve this
  • how to build the shortcut by hand through properties — fine for a one-off case
  • what Browser Shortcut Creator does and how it automates the same thing for dozens of links
  • a separate section on portable browsers, which don’t register in the registry
  • an honest talk about antivirus false positives on a brand-new exe

Setting up one shortcut manually takes three to five minutes. With the utility, fifteen seconds. Here’s where that difference comes from.

2. Why It Happens

Let’s break down why Windows’ built-in tools can’t solve this, and why the usual workarounds are clunky in practice.

Cause Why it’s a problem
Windows stores one default browser handler system-wide The http/https association in the registry is global, not tied to a specific URL or shortcut
A shortcut to a site created the default way produces a protocol link A double-click always routes through the system default handler, bypassing any browser choice
Manually editing a shortcut’s target works, but requires knowing the browser exe path Paths differ across Chrome/Firefox/Edge versions, and portable builds can live anywhere
A .bat file with a launch command works, but scares off non-technical users A console window flashes on every click, and some antivirus tools flag a .bat that launches an exe with a URL parameter
Editing the registry to change the default browser solves a different problem It changes the browser for the whole system, not for one link
Portable browsers don’t register under StartMenuInternet Automatic scanning won’t find them, so the path has to be entered manually

Nice request you’ve got there — said Windows, and quietly reset the default browser to Edge after the next update. Anyone who’s dealt with this knows exactly what I mean.

3. The Fix

Option 1: by hand, through shortcut properties

For a single link, this is enough. Nothing to install.

  1. Create a new shortcut on the desktop: right-click → New → Shortcut.
  2. In the target field, put the path to the browser’s exe and the URL as a second parameter in quotes.

"C:\Program Files\Google\Chrome\Application\chrome.exe" "https://portal.example.com"

Result: a shortcut that opens exactly this URL in Chrome, no matter which browser the system currently has as default.

The downside: you need to know the exact exe path, and it varies per machine. Some have Chrome in Program Files, some in Program Files (x86), and some run a portable Chrome off a flash drive. Handing this instruction to ten coworkers means explaining ten times where to find the exe.

Option 2: Browser Shortcut Creator

The program does the same thing, minus the manual path hunting. On launch it scans the Windows registry under HKLM/HKCU\SOFTWARE\Clients\StartMenuInternet and App Paths and finds every installed browser on its own. All you do is pick one from the list.

Download Browser Shortcut Creator — a single exe around 50 KB, with an embedded icon. Written in C# / .NET Framework, with zero third-party libraries: PyInstaller-style packers were deliberately avoided, since packed exes are exactly what trips up antivirus heuristics most often. The file creates no config files, writes nothing to the registry beyond reading the browser list, and never touches the network — not at launch, not while running.

Prerequisites

  • Windows 7 SP1 or later (7 / 8.1 / 10 / 11)
  • .NET Framework 4.5-4.8 — already present on Windows 10/11, may need installing on Windows 7
  • no administrator rights required — the program only reads the registry, never writes to system-level keys

Steps

  1. Launch BrowserShortcutCreator.exe. No installation needed — it’s portable.
  2. Pick a browser from the auto-detected list, or click «Specify location manually» for a portable build.
  3. Paste the full link, including https://.
  4. Name the shortcut — whatever you’ll see on the desktop or Start menu.
  5. Choose a save folder: desktop, a dedicated folder, or a network share for distributing to coworkers.
  6. Click «Create shortcut».

Result: a finished .lnk file in the chosen folder. The icon comes from the browser itself, not a generic Windows placeholder, so visually the shortcut is indistinguishable from a native one.

Under the hood, shortcut creation goes straight through the standard Shell COM API — the IShellLinkW and IPersistFile interfaces, no WSH wrapper (no WScript.Shell from VBScript) and no third-party libraries. This is the same API Windows Explorer itself uses when creating shortcuts, so the resulting .lnk is no different from one made by hand.

%%{init: {
  'theme': 'base',
  'themeVariables': {
    'primaryColor': '#f8fafc',
    'primaryTextColor': '#1e293b',
    'primaryBorderColor': '#94a3b8',
    'lineColor': '#64748b',
    'fontSize': '15px',
    'fontFamily': 'ui-sans-serif, system-ui, sans-serif'
  },
  'flowchart': {'curve': 'linear', 'nodeSpacing': 50, 'rankSpacing': 50}
}}%%
flowchart TD
    A["Double-click the shortcut"] --> B["Windows reads Target from lnk"]
    B --> C["browser.exe launches with URL parameter"]
    C --> D["The site opens in the chosen browser"]
    style A fill:#f8fafc,stroke:#3b82f6,stroke-width:2px,color:#1e40af
    style B fill:#f8fafc,stroke:#3b82f6,stroke-width:2px,color:#1e40af
    style C fill:#f8fafc,stroke:#f97316,stroke-width:2px,color:#9a3412
    style D fill:#f8fafc,stroke:#22c55e,stroke-width:2px,color:#15803d

Portable Browsers

Chrome Portable, Firefox Portable, and similar builds don’t write themselves into the Windows registry — they live in a single folder and launch straight from the exe. Automatic scanning won’t see them, and that’s not a bug, it’s the whole point of a portable build: don’t touch the system.

For these, the program has a «Specify location manually» mode: just point it at the browser’s exe, and everything else works the same — link, name, save folder. Useful for testers who keep one portable copy of each browser at a specific version, without depending on what’s installed system-wide.

4. Verification

After creating a shortcut, check three things: is the path correct, does the right browser open, and did the icon survive.

  1. Right-click the shortcut → Properties → «Shortcut» tab. The «Target» field should show the path to the browser exe and the URL as a second parameter in quotes.
  2. Double-click the shortcut. The browser you selected should launch, not whatever the system currently has as default.
  3. Check the address bar in the window that opens — the URL should match what you entered, with nothing extra and nothing truncated.

To check a .lnk’s contents programmatically instead of through properties, PowerShell pulls the target path and arguments in two lines:


$sh = New-Object -ComObject WScript.Shell
$lnk = $sh.CreateShortcut("C:\Users\Admin\Desktop\Portal.lnk")
$lnk.TargetPath
$lnk.Arguments

The output should show the browser’s exe path in TargetPath and the URL in Arguments. If TargetPath points to the browser itself, rather than some generic «open link» handler, the shortcut is set up correctly.

5. Troubleshooting

Error Cause Fix
Shortcut opens the browser but shows an empty tab, no URL The URL didn’t make it into the Arguments parameter, lost during copy-paste Recreate the shortcut, paste the full link with https://, no stray leading spaces
Portable browser isn’t found by auto-scan Portable builds don’t register under StartMenuInternet Use «Specify location manually» and point directly to the exe
Antivirus blocks the exe on first run A new, unsigned file with no reputation in ML-heuristic databases See the separate section below on antivirus and VirusTotal
Shortcut icon is generic, not the browser’s Windows’ icon cache hasn’t refreshed Restart explorer.exe or clear IconCache.db
Shortcut stopped working after a browser update The exe path changed during a major update (rare, but happens with some portable builds) Recreate the shortcut, auto-scan will pick up the new path

It’s not as bad as the table makes it look. It’s actually simpler — nine times out of ten it’s a typo in the link or the wrong browser picked from the list.

6. Alternatives

Here’s what else solves this same problem, and why I ended up writing my own tool instead of using something existing.

A manual .bat file

Works fine for one person who wrote it themselves. Doesn’t scale to handing out to coworkers: a console window flashes on every launch, and some antivirus tools are warier of a .bat launching an exe with a URL parameter than of a .lnk file.

Editing the registry to change the default browser

Solves a different problem — changes the default browser for the entire system. Doesn’t work at all for configuring a single link.

Third-party browser pickers (Browser Chooser and similar)

Pop up a browser-selection dialog on every link click. It works, but adds an extra click every single time — exactly the friction this whole approach is meant to avoid.

Group Policy (for corporate environments)

GPO can centrally push shortcuts to a network share or lay .lnk files onto every domain user’s desktop via Group Policy Preferences. Pairs well with Browser Shortcut Creator: generate the shortcuts once, then distribute them through GPO like any other file.

Why I ended up writing my own tool instead of using any of the above: none of them offered automatic browser detection without manually typing paths, while also not dragging in tens of megabytes of dependencies for a fifty-kilobyte job.

7. Keeping It Working

  • Monitoring: if you’re distributing shortcuts to coworkers centrally, add a check to your workstation-update checklist to make sure shortcuts survived any browser reinstall.
  • Browser versions: a portable build’s exe path can shift after a major update — regenerate manual-mode shortcuts quarterly if you rely on portable browsers heavily.
  • Backing up shortcuts: the .lnk files themselves are a few kilobytes each — keep the working set in a shared folder or repo so you’re not rebuilding them after a Windows reinstall.
  • Source on hand: if you’re using this in an organization with strict security requirements, keep a local copy of the source and know how to rebuild the exe without reaching out to any external server.
  • Auto-start: not needed — the program only runs when you’re creating a new shortcut, spawns no background processes, and never asks for a spot in startup.
  • Updating the exe: check the repository manually for new releases — there’s no auto-update by design, less code means less surface for «what is this thing doing in the background».

A drop of nicotine kills a horse. One mistyped URL in a shortcut parameter won’t kill anyone, but it will guarantee half a day of «why does this open an ad banner instead of the portal».

8. Security

Here’s an honest rundown of what the program actually does to the system, and why an unsigned exe deserves your trust anyway.

On antivirus and VirusTotal

A brand-new, unknown exe with no digital signature almost always picks up one to three false positives from ML and heuristic engines on VirusTotal — something like Trojan:Win32/Wacatac.C!ml from Microsoft Defender, or Trojan.Win32.VSX from Trend Micro. That doesn’t mean the file is malicious. It means the file has no reputation yet.

The difference between signature-based and heuristic detection matters here. Signature detection means the antivirus found a specific, known malicious code pattern matching something in its database. Heuristic or ML detection works differently: it looks at general traits — a small exe, unsigned, touching the registry, creating .lnk files — and scores the file as «resembling suspicious behavior.» That’s exactly what any shortcut-creating utility looks like to a model, including Windows Explorer itself, if it were freshly rebuilt and shipped as a standalone exe with no history or signature.

What you can check yourself
The source code is open. The program sends nothing over the network — not on launch, not while running — and that’s verifiable with any network monitor like Process Monitor or Wireshark in about a minute of watching. If you’d rather not trust a prebuilt binary, the exe can be recompiled locally from source using Windows’ own compiler, no extra tools required, giving you a binary you built yourself instead of one you downloaded.

Building it yourself from source

Compilation goes through csc.exe, the standard compiler bundled with .NET Framework — no need to install Visual Studio or anything else.


build.bat

The script calls csc.exe with the asInvoker manifest (the program never requests elevated privileges) and produces the same exe as the prebuilt release. You can verify this by comparing hashes.

Other safeguards

  • No administrator rights required — asInvoker manifest, elevation is never requested.
  • No configuration files on disk — nothing to find and nothing to clean up after removing it.
  • No writes to system-level registry keys — it only reads StartMenuInternet and App Paths to find browsers.
  • Run the exe from a local folder rather than a widely-writable network share — standard hygiene for any portable tool, not specific to this one.

9. FAQ

Why does the shortcut still open the wrong browser after I set it up?

Most often it’s because the wrong browser was picked from the list, or the shortcut was built manually through properties with a typo in the exe path. Recreate the shortcut through the program and double-check TargetPath using the PowerShell command from the Verification section.

How do I check that a shortcut is set up correctly?

Right-click → Properties → «Shortcut» tab, and look at the «Target» field: it should contain the path to the intended browser’s exe with the URL as a second parameter in quotes. Or run the PowerShell WScript.Shell command from the verification section — it prints TargetPath and Arguments separately.

What do I do if antivirus blocks the exe?

Upload the file to VirusTotal and check whether it’s a signature detection or a heuristic/ML one — the verdict name usually carries a marker like .ml or a generic name with no specifics. For heuristic flags on a new unsigned exe, add an exclusion in your antivirus, or rebuild the exe locally from source — that removes the question of trusting someone else’s build entirely.

How is this different from editing a shortcut manually through properties?

The result is identical — both approaches produce a .lnk pointing at the browser’s exe. The difference is that doing it manually requires knowing the exact browser exe path, while the program finds every installed browser through registry auto-scan and skips that requirement entirely.

Do I need administrator rights to use it?

No. The program is portable, installs nothing, and runs from any folder without administrator rights — and reading the registry to find browsers doesn’t require elevated privileges either.

10. What You Get

Once you’ve set up shortcuts through Browser Shortcut Creator, you’ve got a desktop or shared folder full of links, each opening in a browser you chose ahead of time, regardless of whatever the system currently has as default. The corporate portal goes to Edge with an AD profile, everything else stays in your usual browser, no constant switching required.

Born in manual shortcut properties — not afraid of automation. If something doesn’t open the way it’s supposed to after setup, drop a comment and we’ll sort it out.

Download Browser Shortcut Creator

System Requirements

Parameter Value
OS Windows 7 SP1, 8.1, 10, 11
.NET Framework 4.5-4.8 (preinstalled on Windows 10/11)
Exe size ~50 KB, embedded icon, no external dependencies
Rights required User-level, no administrator needed
Supported browsers Anything registered under StartMenuInternet: Chrome, Firefox, Edge, Opera; portable builds via manual mode
Скачать
Андрей А.
Author: Андрей А.

Руководитель ИТ / Кризис-менеджер 25 лет в IT: от инженера в МегаФоне до руководителя отдела. Знаю, как выглядит бардак: нестабильные сети, устаревшая инфраструктура, конфликты в команде, раздутые сроки. Помогаю бизнесу выходить из кризиса: навожу порядок в легаси, стабилизирую то, что разваливается, выстраиваю прогнозируемые процессы. Не раз возвращал к жизни ИТ-структуры — знаю цену хаосу. 📍 Ищу проект для полной реорганизации / стабилизации. 📬 Telegram: @over_dude ✉️ mail@it-apteka.com

Оставайтесь на связи

Рецепты от IT-боли. Без воды, без рекламы, без маркетинговой шелухи.

Подписаться на IT-Аптеку →

Мы ВКонтакте

IT-Аптека — советы, новости и помощь рядом.

Вступить в группу ВКонтакте →
Поделитесь:

Связанные записи

Оставьте комментарий

Ваш адрес email не будет опубликован. Обязательные поля помечены *

Прокрутить вверх