Pause or Remove Microsoft Defender on Windows 11: Safe Methods and Best Practices

Microsoft Defender Antivirus can be paused quickly for a single task or disabled persistently for an entire deployment — but how you do it, and why you do it, matter far more today than they did a few years ago. This feature guide and analysis walks through safe, supported temporary disables, the administrative Group Policy route for persistent changes, the recommended way to replace Defender with a third‑party product, the pitfalls Windows 11 Home users face, and the real security risks and operational caveats you must accept before you flip a single switch. Wherever possible I verify the technical steps and platform behavior against community-tested guidance and modern platform realities.

Background / Overview​

Microsoft Defender (formerly Windows Defender) ships built into Windows 11 and provides real‑time protection, cloud‑assisted detection, and integrated endpoint features. For most consumer and business users it delivers effective baseline protection with minimal administration. That said, legitimate scenarios exist where pausing or removing real‑time scanning is warranted: controlled software testing, compatibility troubleshooting, AV migrations in managed fleets, or running specialized pentesting tools in an isolated lab. These scenarios require different approaches — a quick UI toggle for a one‑off test is not the same as making a fleet‑wide change with Group Policy.
There are three practical, supported approaches you’ll see repeatedly:

• Temporary disable: turn off Real‑time protection via the Windows Security UI for short maintenance windows. This is reversible and safe for brief tasks.
• Permanent disable (enterprise): use Group Policy or MDM to set a persistent policy on Windows 11 Pro, Enterprise, or Education. This is the supported administrative route for managed devices.
• Replace with third‑party AV: install a reputable antivirus that registers with Windows Security; Defender will automatically step into passive mode. This works across all Windows editions.

Two caveats shape everything that follows: Tamper Protection, which blocks unauthorized changes to Defender settings, must often be handled first for permanent edits; and Microsoft has deprecated or changed the behavior of several legacy registry disable keys, making registry “hacks” brittle or ignored on modern builds and managed endpoints. Treat registry-based permanent disables as fragile and version‑dependent.

---

Temporary disable: the safe, reversible method​

Why use the UI toggle​

The UI toggle under Windows Security is the recommended way to pause scanning for short activities: installers blocked by false positives, compilation tasks that suffer from on‑access scanning, or running a trustworthy tool for testing. It’s the least risky option because Windows will typically re‑enable real‑time protection automatically after a short time or when you reboot.

Step‑by‑step (supported)​

• Open the Windows Security app (Start → type Windows Security → Open).
• Select Virus & threat protection.
• Click Manage settings under Virus & threat protection settings.
• Toggle Real‑time protection to Off and confirm any UAC prompts.
• Do the maintenance task, then return and toggle Real‑time protection back to On immediately when finished.

Optional toggles while you’re there​

• Cloud‑delivered protection: can be turned off for a test that triggers cloud checks.
• Automatic sample submission: can be toggled off to stop automatic file uploads.
• Tamper Protection: must be turned off only temporarily if you plan permanent policy changes later. Be cautious.

Practical tips and safety​

• When you must disable protection, isolate the device from the network if feasible and avoid downloading or executing untrusted content.
• Prefer adding targeted exclusions for the specific file, folder, or process instead of a blanket disable; exclusions are precise and reversible.
• Expect auto‑re‑enable: Windows intentionally re‑enables real‑time protection to reduce prolonged exposure windows. Don’t rely on the UI toggle for long operations.

---

Permanent disable via Group Policy (Pro / Enterprise)​

When this is appropriate​

Use Group Policy only when you have a controlled reason: migrating a fleet to a third‑party AV, imaging specialized servers in a hardened lab, or applying policies as part of an enterprise deployment. It’s a supported, auditable route for persistent changes on managed devices.

Precondition: Tamper Protection​

Before Group Policy changes will reliably take effect on modern consumer devices, you often must disable Tamper Protection through Windows Security. Tamper Protection is enabled on many consumer devices to stop unauthorized changes and will silently block registry or service edits otherwise. Do not leave Tamper Protection off longer than necessary.

Step‑by‑step Group Policy​

• Press Windows + R, type gpedit.msc, and press Enter (available in Pro/Enterprise/Education).
• Navigate to: Computer Configuration → Administrative Templates → Windows Components → Microsoft Defender Antivirus.
• Double‑click Turn off Microsoft Defender Antivirus, set the policy to Enabled, click Apply and OK.
• Restart the machine to apply the policy. Defender should not run real‑time protection after the reboot.

How to reverse​

Set the same policy to Not Configured (or Disabled), apply, and reboot. Re‑enable Tamper Protection in Windows Security if you previously turned it off.

Caveats for enterprise environments​

• Devices enrolled in Intune, Defender for Endpoint, or governed by centralized MDM may ignore or override local GPO edits. Persistent changes should be deployed through enterprise channels.
• Always test on a pilot group: management policies, telemetry, and product registration can create edge cases where Defender enters passive mode rather than fully stopping services. Validate product registration with Windows Security Center after a change.

---

Replace Defender: install a reputable third‑party AV (recommended for Home users who want "permanent" off)​

Installing mainstream, Windows‑compatible antivirus software is the simplest, supported method to make Defender step back. Windows Security automatically detects registered third‑party engines and disables Defender’s real‑time protection to prevent conflicts. This works across Home, Pro, and Enterprise editions.

Why this is often the best permanent path​

• It is supported and less brittle than registry hacks.
• You retain active endpoint protection (from the new vendor) rather than leaving the device naked.
• Windows will put Defender in passive mode, not attempt to fully remove system components.

Steps​

• Choose a reputable AV vendor and ensure the product supports Windows 11.
• Download the installer from the vendor’s official distribution channel (don’t use untrusted mirrors).
• Install, accept prompts, and reboot if required.
• Open Windows Security → Virus & threat protection to verify that your third‑party product is active and that Defender’s real‑time protection is shown as off or passive.

Tip: Periodic Scanning​

If you want an additional layer, you can enable Microsoft Defender’s Periodic Scanning to run occasional supplementary scans alongside your primary AV. This option is available in Windows Security and is compatible with most reputable third‑party solutions.

---

Windows 11 Home — limitations and recommended path​

Windows 11 Home lacks the Local Group Policy Editor (gpedit.msc), which eliminates the straightforward GPO path for persistent disables. Many guides recommend registry edits for Home users, but that approach is increasingly unreliable and risky on modern Windows builds. Microsoft has deprecated or removed the legacy DisableAntiSpyware key behavior in many scenarios, and Tamper Protection can block registry edits.
Recommendation for Home users:

• Prefer installing a reputable third‑party AV (see previous section) — this provides a supported replacement and works consistently across editions.
• For short tasks, use the supported UI toggle or add targeted exclusions rather than registry changes.

If you still consider registry edits for advanced scenarios, create a System Restore point, export affected keys, and understand the fragility and future‑proofing limitations. Registry hacks are brittle across updates and may be ignored on Defender for Endpoint‑onboarded systems.

---

Registry keys, legacy behavior, and why hacks fail on modern builds​

Historically, the DWORD DisableAntiSpyware under:
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows Defender
was used to disable Defender. Today that key is treated as legacy. Microsoft has removed or limited the behavior of these keys on many modern platform versions and on systems managed by Defender for Endpoint. Tamper Protection also prevents unauthorized registry changes on many consumer devices. Relying on these keys for a permanent disable is brittle and can leave you with inconsistent results across updates.
If you use the registry anyway, do so only with full backups and a restore point — and accept that a future Windows update may re‑enable protections or ignore your tweak. Flag this approach as a last resort for advanced users only.

---

Tamper Protection: a short primer​

Tamper Protection defends Defender settings from silent changes by malware (or well‑meaning scripts). It is enabled by default for many consumer devices and is often enforced in managed environments. If you plan any permanent changes via Group Policy or registry, you’ll likely need to disable Tamper Protection first through the Windows Security UI — but only disable it temporarily and re‑enable it right after completing your work. Leaving Tamper Protection off increases the risk of stealthy, persistent attacks.

---

Troubleshooting, verification, and recovery​

Verify Defender status programmatically​

Run an elevated PowerShell and execute:
Get‑MpComputerStatus
This cmdlet reports AMServiceEnabled, AntivirusEnabled, RealTimeProtectionEnabled, PassiveMode and AMProductVersion — useful for troubleshooting and automation checks after policy or product changes.

Restart Defender services if needed​

If Defender services have been disabled incorrectly, you can attempt to recover them with:
sc.exe config WinDefend start= auto
sc.exe start WinDefend
sc.exe config WdNisSvc start= demand
sc.exe start WdNisSvc
Use these cautiously and only on systems you control. If services were removed by registry or third‑party scripts, you may need a system repair.

System integrity checks​

If platform components are missing or corrupted, community guidance recommends running:

• sfc /scannow
• DISM /online /Cleanup-Image /RestoreHealth
  These commands help recover missing Defender platform files in many cases, though enterprise policies can make recovery more complex on managed devices.

---

Security warnings, abuse cases, and why Microsoft hardened Defender​

Turning Defender off isn’t merely an administrative risk — it’s an attack vector. Research and real incidents have demonstrated that attackers and researchers have attempted to force Defender into passive states via driver abuse, fake AV registrations, or vulnerable vendor drivers (a class of attacks often described as BYOVD — Bring Your Own Vulnerable Driver). Proof‑of‑concept tools have shown how a fake AV registration can silence Defender; ransomware campaigns have abused legitimate drivers to alter defense state prior to payload delivery. These threats are a major reason Microsoft hardened the platform and deprecated legacy disable keys.
Practical implication: any local, unsupported “disabler” script or gadget you find online may mirror techniques used by attackers and should be treated as high‑risk. Prefer auditable, managed channels (GPO/MDM) or the supported third‑party AV replacement path.

---

Operational checklist (what to do before you disable anything)​

• Create a System Restore point. Use the System Protection tool and create a restore point before registry or policy changes.
• Full backup of critical data. Disabling AV exposes you to risk — back up to external media or trusted cloud.
• If possible, perform changes in an isolated environment (offline or isolated VLAN) and re‑enable protection immediately after.
• Prefer precise exclusions or sandboxing (Windows Sandbox, Hyper‑V) over global disables when dealing with installers or development builds.
• If deploying changes across machines, use Group Policy or MDM and validate product registration and telemetry on a pilot batch.
• Re‑enable Tamper Protection and run a full scan after the maintenance window.

---

For administrators: migration and fleet considerations​

• Plan migrations: when replacing Defender with a third‑party AV, deploy the new product via your management stack and confirm Windows Security sees it as the active engine before disabling Defender fleet‑wide. This avoids "unprotected" windows.
• Use MDM/GPO for auditable, reversible changes: local hacks produce policy drift and complicate incident response.
• Monitor for re‑enables after Windows Feature Updates: major updates can reset Defender configuration. Include verification steps in post‑update checks.

---

What we verified and what remains version‑dependent​

Verified facts:

• The Windows Security UI toggle disables real‑time protection temporarily and Windows typically re‑enables it automatically after reboot or some interval.
• Group Policy contains a supported policy named Turn off Microsoft Defender Antivirus for Pro/Enterprise editions; applying it and rebooting can stop real‑time protection persistently.
• Installing a registered third‑party antivirus causes Defender to enter passive mode; this method works across Windows editions.

Version‑dependent or fragile items (flagged):

• The effectiveness of specific registry disable keys (e.g., DisableAntiSpyware) is version‑dependent. Microsoft has deprecated or altered their behavior on modern builds and on devices onboarded to Defender for Endpoint; these keys are not a robust method for permanent disablement across all customers. Treat those claims as fragile and potentially unverifiable on any given build without checking the current platform documentation and device state.

If you require absolute confirmation for a specific Windows 11 build or managed configuration, validate the behavior on a test box with the exact OS build and management enrollment you’re targeting and capture Get‑MpComputerStatus and GPO/MDM results. That is the only reliable way to confirm how your environment will behave.

---

Final analysis: strengths, trade‑offs, and a pragmatic recommendation​

Microsoft Defender is tightly integrated with Windows, which gives it advantages: low maintenance, cloud‑assisted intelligence, and administrative controls. Those same strengths mean Microsoft has intentionally hardened the product to make silent disables harder. For most users, disabling Defender is unnecessary and dangerous.
Pragmatic rules:

• For brief tasks, use the Windows Security UI toggle and targeted exclusions; isolate the device and re‑enable protection immediately.
• For permanent changes, replace Defender with a reputable third‑party AV or apply enterprise policies via GPO/MDM — do not rely on registry hacks.
• If you must use Group Policy, coordinate with endpoint management and telemetry teams, test on a pilot group, and re‑enable Tamper Protection as soon as work finishes.

Turning off Defender is a technical capability — but in 2026 it is no longer a simple toggle you can safely leave off without consequences. Follow the operational checklist, prefer supported channels, and avoid undocumented tools. If your use case is a development or testing need, consider disposable VMs or sandboxes to keep your main system protected.
Conclusion: disabling Microsoft Defender is straightforward in the short term and possible permanently with enterprise controls or a third‑party replacement, but it carries real operational and security risks. Use the supported UI for temporary work, use managed policy or a reputable AV for long‑term changes, and always keep backups and a recovery plan ready before you proceed.

---

Source: H2S Media How to Disable Windows 11 Defender: Temporary and Permanent

 

[ChatGPT]

Adding a Google Chrome shortcut to your Windows desktop is one of those tiny productivity moves that pays back every day: one double‑click, zero hunting through menus. This guide explains three reliable ways to add Chrome (or a specific website) to your desktop on Windows 10 and Windows 11, checks the technical details you’ll want to understand, flags version differences and oddities you may encounter, and shows a couple of advanced options (including how to make a “web app” that opens in its own window). The instructions are practical, step‑by‑step, and backed up with platform documentation and community-tested notes so you won’t be surprised by small variations between machines or Chrome builds. com]

Background / Overview​

Desktop shortcuts are a basic Windows convenience: they let you place an external pointer (a .lnk or .url file) on the desktop that opens a program, file, folder, or website with a double‑click. Windows supplies multiple built‑in ways to create those shortcuts—dragging apps from the Start menu, using File Explorer’s Send to → Desktop (create shortcut) command, or creating new shortcuts manually—so the same end result can be achieved several ways depending on what’s fastest for you. Microsoft’s support resources and common support guides document these Windows behaviors, and Chrome exposes a separate “create shortcut / install as app” pathway for web pages that slightly differs from creating a normal program shortcut.
Why this matters for Chrome users:

• You can add a simple Chrome program shortcut (launch browser).
• You can add a Chrome shortcut that points to one specific website (open Gmail, Trello, etc.).
• You can make a site behave like an app (standalone window, optional taskbar pinning).

The short methods list below matches the common approaches found in how‑to guides and community documentation. Each method is safe, reversible, and requires no admin rights in most home setups.

---

Quick overview: three simple methods​

• Method 1 — Use Windows Search (best for a consistent Chrome program shortcut).
• Method 2 — Drag Chrome from the Start Menu to the desktop (visual, quick).
• Method 3 — Create a desktop shortcut for a specific website from inside Chrome (web shortcut or “open as window” app).

Below you’ll find step‑by‑step instructions, platform notes, troubleshooting, and advanced tips.

---

Method 1 — Using Windows Search (reliable for Windows 10 & Windows 11)​

This is the most deterministic method to create a Chrome program shortcut that launches the browser itself.

Steps​

• Press the Windows key (or click the Start button) and type Google Chrome.
• When Google Chrome appears in the results, right‑click the result and choose Open file location. On Windows 11 you may first need to choose Show more options to reveal the traditional context menu.
• In the File Explorer window that opens (this contains the shortcut used by Start), right‑click the Chrome icon and select Send to → Desktop (create shortcut).

Result: a Chrome shortcut will appear on your desktop and launch Chrome when double‑clicked. If you prefer a taskbar icon, right‑click that new desktop shortcut and choose Pin to taskbar.

Why this works / what’s happening​

The Start menu item is itself a shortcut pointing to the Chrome executable. When you open its file location you access that shortcut file (.lnk) so you can dispatch a copy to the desktop. Windows’ Send to → Desktop (create shortcut) preserves the working target and icon. Microsoft documents the drag/drop and Send to behavior as standard shortcut creation methods.

Platform notes​

• On Windows 11 you will sometimes see “Show more options” first; that expands to the legacy right‑click menu.
• If Open file location is missing (rare), the Start result might point to a Store app or an app installed per‑user; use File Explorer to search for chrome.exe (see advanced section below).

---

Method 2 — Drag and drop from the Start Menu (visual & fast)​

If you prefer gestures and quick visual results this is the fastest method.

Steps​

• Open the Start Menu (click the Windows icon).
• Click All apps (Windows 11) and scroll to Google Chrome.
• Click, hold, and drag the Chrome entry onto the desktop and release.

Windows creates a desktop shortcut for you automatically. This is the same behavior Microsoft describes for dragging Start items to the desktop.

When this method may not work​

• On some versions of Windows 11, not all Start items support drag/drop depending on whether they are classic shortcuts or Microsoft Store packages. If drag/drop fails, fall back to Method 1 or use the shell:AppsFolder trick to expose all installed apps (advanced troubleshooting). Community support posts document these Windows 11 Start menu nuances.

---

Method 3 — Create a desktop shortcut for a specific website (Chrome’s built‑in option)​

Chrome lets you create a site‑specific shortcut that opens a single website directly—handy for Gmail, Google Docs, Slack, web dashboards, or banking sites.

Steps (typical, may vary across Chrome versions)​

• Open Chrome and navigate to the website you want to turn into a desktop shortcut.
• Open Chrome’s menu (three vertical dots).
• Look for Save and share → Create shortcut (some Chrome versions place this under More tools → Create shortcut…). Name the shortcut and (optionally) check Open as window to make it behave like a standalone app. Click Create.

Result: an icon will appear on your desktop that opens that website directly in Chrome (or in a window without the usual tabs and Omnibox if you checked Open as window).

Version headaches and why you might not see the option​

Chrome’s UI has shifted across releases. Users reported that the Create shortcut option moved between submenus (More tools vs Save and share) and occasionally disappeared when experimental UI flags were in use. If the menu item is missing for you, check Chrome flags (for example chrome://flags/#chrome-refresh-2023) or look under Save and share. Community threads document those exact changes and workarounds. If the menu item is absent, you can also create a manual shortcut (right‑click desktop → New → Shortcut and paste the URL) but the automatic site icon may not be preserved.

---

Advanced: make a site open as a Chrome “app” or a dedicated window​

If you want a website to behave like a first‑class desktop app — separate window, its own taskbar icon, and the possibility to auto‑start — use Chrome’s Create shortcut with Open as window, or create a custom shortcut that launches chrome.exe with the --app flag.

Example target line (advanced users)​

• Target field in shortcut properties:
  "C:\Program Files\Google\Chrome\Application\chrome.exe" --app=Example Domain

This launches the site in a compact, app‑like window without address bar and standard Chrome chrome UI. Guides and community answers explain using --app and the chrome_proxy approach for app shortcuts. Use this when you want a stripped UI and easier taskbar pinning.

Important: where chrome.exe lives (why the exact path matters)​

Chrome’s executable location can vary:

• 64‑bit Chrome installs to C:\Program Files\Google\Chrome\Application by default on modern systems.
• Older or 32‑bit installs may be in C:\Program Files (x86)\Google\Chrome\Application.
• In legacy setups Chrome may have been installed to the user’s AppData folder.

Because of historical changes in Chrome’s installer behavior, check both Program Files and Program Files (x86) if you need the exact path. Community documentation and Stack Overflow threads cover the common locations so you can craft an accurate Target string.

---

Windows 10 vs Windows 11 — small differences to expect​

Windows 10:

• Right‑clicking Start results normally shows Open file location directly.
• Dragging Start menu tiles or app entries to the desktop generally works as described.

Windows 11:

• The right‑click menu is simplified; you may need Show more options to reveal legacy commands like Open file location or Create shortcut.
• Some Microsoft Store apps or “modern” apps don’t expose a straightforward file location; use shell:AppsFolder (type Win+R and paste shell:AppsFolder) to view all installed app shortcuts and create desktop shortcuts from there. Microsoft documentation and Q&A threads explain these steps.

---

Troubleshooting: common issues and fixes​

• Shortcut doesn’t appear on the desktop:
• Confirm desktop icons aren’t hidden: right‑click desktop → View → Show desktop icons. Several how‑to guides highlight this as the first check.
• If Chrome isn’t installed or was removed, there’s nothing to shortcut — reinstall Chrome and repeat the steps.
• If the shortcut was created but looks generic, refresh the desktop (right‑click → Refresh) or sign out and sign back in.
• “Create shortcut” menu item missing in Chrome:
• Check Chrome’s menu under Save and share or More tools—Google moved the option in some updates.
• If you have experimental UI flags enabled (such as Chrome Refresh 2023), disabling that flag has been reported to restore the Create shortcut option. This is a behavior change tracked by Chrome users in community threads. Proceed with flags carefully; they control experimental features.
• Start menu entries won’t let you open file location:
• If the Start tile represents a Store app, right‑clicking may not show Open file location. Use shell:AppsFolder to access the internal list and create shortcuts from there. Microsoft community posts provide step guides for this scenario.
• Desktop shortcut opens the wrong icon or opens Chrome with a generic icon:
• If a site has no site‑specific icon metadata or Chrome’s creation method falls back to the browser icon, you can manually change the shortcut’s icon: right‑click shortcut → Properties → Change Icon → pick an .ico file. Many support articles show this process.

---

Security and privacy considerations​

• Be cautious about creating desktop shortcuts that point to login pages for sensitive services on shared machines. A desktop icon makes the service easier to reach for anyone who uses the PC.
• Shortcuts that open sites in Chrome will use your default Chrome profile; if you share the computer, consider using a dedicated profile or requiring password / Windows account separation.
• Creating a manual shortcut (New → Shortcut and pasting a URL) is innocuous, but always verify the URL before saving — don’t create shortcuts to suspicious or phishing sites.

---

Best practices and small productivity tips​

• Group related shortcuts in a desktop folder (e.g., “Work — Web Tools”) to keep the desktop tidy.
• Use Chrome’s Open as window option for daily web apps (Gmail, Slack web, Trello). These behave like apps and reduce tab clutter.
• Pin frequently used Chrome shortcuts to the taskbar or Start menu for one‑click access.
• If you maintain multiple Chrome profiles, create profile‑specific shortcuts by launching chrome.exe with the --profile-directory flag and a profile‑specific target. That prevents opening a work site in a personal profile by accident. (This is an advanced workflow; check your profile names carefully before using this option.)

---

Verifications and sources used to validate steps​

• Windows shortcut creation behavior and Start menu drag/drop are described in Microsoft’s support documentation and community Q&A. These are the authoritative behaviors for Windows 10 and Windows 11 context menus and Send to → Desktop functionality.
• Chrome’s site‑shortcut and “open as window” features are the same steps taught in Chrome hobbyist and IT admin guides; they’re widely documented and tested in community how‑tos that show the Create shortcut flow and mention the Open as window option. Chrome’s menu labels have shifted across releases, so community threads and guides track that movement.
• The location of chrome.exe can differ between Program Files and Program Files (x86) depending on your chrome build and when it was installed; Stack Overflow community answers summarize the typical paths and the historical reasons for variance. Referencing this avoids broken target lines when you create an advanced shortcut.
• Community reports document intermittent Chrome UI differences (Create shortcut moved or temporarily missing), and often provide practical fixes (check Save and share; disable Chrome Refresh flags). Use these notes if the Create shortcut menu entry is not where a guide says it should be.

If any of the above behavior is different on your PC, that difference is likely tied to:

• your Windows build (especially between major Windows 11 feature updates),
• Chrome release channel (stable vs beta vs dev), or
• enabled experimental flags (chrome://flags).

When something diverges from these instructions, check those three areas first.

---

Quick recap — pick the method that fits you​

• Need a simple Chrome program icon on the desktop? Use Windows Search → Open file location → Send to → Desktop.
• Prefer drag & drop? Drag Chrome from All apps in the Start menu to the desktop.
• Want a desktop icon that opens a specific web site? Use Chrome’s menu Create shortcut (Save and share or More tools), optionally Open as window for app‑like behavior.

---

Final thoughts​

Adding a Google Chrome shortcut to your Windows desktop is fast, reversible, and adaptable to your workflow. Whether you simply want a quicker way to launch the browser or you prefer to create app‑like shortcuts for your most‑used web tools, the three methods explained here cover the full range of straightforward to advanced use cases. Keep the platform notes in mind—especially the Chrome menu placement differences and the executable path nuances—and you’ll be able to create reliable shortcuts that behave exactly how you want them to. If you run into a missing menu item or an unexpected icon, the troubleshooting checklist above addresses the usual culprits: hidden desktop icons, Chrome experimental flags, and the possibility that Chrome was installed to a non‑default location. Armed with those checks and the simple steps in this guide, you’ll be one double‑click closer to a faster daily web routine.

---

Source: HowToiSolve How To Add Google Chrome Shortcut To Desktop In Windows