How to Install Microsoft Edge on Debian (13, 12, 11)

Edge is the only Chromium browser that syncs bookmarks, passwords, and open tabs natively with a Microsoft account, and it supports the full Chrome extension library. To install Microsoft Edge on Debian, you add Microsoft’s official APT repository through a DEB822 repository configuration, and APT handles updates from there.

The instructions below cover Debian 13 (Trixie), 12 (Bookworm), and 11 (Bullseye), including stable, beta, and dev channel selection, troubleshooting common APT issues, and clean removal.

Update Debian Before Installing Microsoft Edge

Before adding a new third-party repository, update your existing Debian packages so the base system is current. This reduces the chance of dependency conflicts when APT pulls in Microsoft Edge:

sudo apt update && sudo apt upgrade

This guide uses sudo for commands that need root privileges. If your user is not in the sudoers file yet, run the commands as root or follow the guide on how to add and manage sudo users on Debian.

This command runs interactively so you can review package changes before confirming. For non-interactive upgrades in scripted deployments, add the -y flag (for example, sudo apt update && sudo apt upgrade -y).

Install Microsoft Edge on Debian

Debian’s extrepo tool can also enable the Edge repository, but the extrepo catalog currently bundles an outdated copy of Microsoft’s GPG key with a SHA-1 self-signature. On Debian 13, APT’s sqv verifier rejects SHA-1 binding signatures, which breaks apt update. Until the extrepo catalog ships an updated key, use the manual method below instead.

Install the Required Packages for Microsoft Edge

Most Debian desktop installations include the tools needed for repository setup, but minimal or server installations may lack them. Install or refresh them:

sudo apt install curl gpg ca-certificates -y

Specifically, these packages provide SSL certificate validation (ca-certificates), file downloading via curl, and GPG key handling (gpg) needed to securely add the Microsoft repository.

Import the Microsoft Edge GPG Key on Debian

Next, APT uses GPG keys to verify that packages come from the repository they claim to originate from. Import the Microsoft signing key and store it in a dedicated keyring under /usr/share/keyrings:

curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft-edge.gpg

This downloads Microsoft’s ASCII-armored public key and converts it to binary format with gpg --dearmor. The resulting keyring file lives in /usr/share/keyrings and gets referenced by the Signed-By field in the repository definition. Avoid the deprecated apt-key workflow.

Verify the Microsoft Edge GPG Key Fingerprint

Before trusting the key, verify its fingerprint against Microsoft’s published value to ensure authenticity. After saving the keyring locally, display the fingerprint:

gpg --no-default-keyring --keyring /usr/share/keyrings/microsoft-edge.gpg --with-fingerprint --list-keys

/usr/share/keyrings/microsoft-edge.gpg
--------------------------------------
pub   rsa2048 2015-10-28 [SC]
      BC52 8686 B50D 79E3 39D3  721C EB3E 94AD BE12 29CF
uid           [ unknown] Microsoft (Release signing) <gpgsecurity@microsoft.com>

The fingerprint must match BC52 8686 B50D 79E3 39D3 721C EB3E 94AD BE12 29CF as documented on Microsoft’s Linux packages page. If the fingerprints do not match, do not add the repository and investigate further.

Microsoft’s Edge repository uses a Suites value of stable rather than a Debian codename like bookworm. This means the same repository definition works across Debian 11, 12, and 13 without modification.

Create the Microsoft Edge DEB822 Repository File

Microsoft Edge for Linux is only published for amd64 (x86_64) architectures. It does not work on ARM, ARM64, or other architectures. To check your system architecture, run dpkg --print-architecture. If it does not return amd64, the repository will not provide Edge packages and installation will fail.

Now use the modern DEB822 .sources format to define the Microsoft Edge repository. This format works on all supported Debian releases (11, 12, and 13+):

sudo tee /etc/apt/sources.list.d/microsoft-edge.sources > /dev/null << 'EOF'
Types: deb
URIs: https://packages.microsoft.com/repos/edge
Suites: stable
Components: main
Signed-By: /usr/share/keyrings/microsoft-edge.gpg
Architectures: amd64
EOF

Refresh the APT Cache and Verify Microsoft Edge

After creating the repository definition, refresh your APT package list so Debian can see the new Microsoft Edge packages:

sudo apt update

Verify the Microsoft Edge packages are visible to APT with apt-cache policy:

apt-cache policy microsoft-edge-stable

microsoft-edge-stable:
  Installed: (none)
  Candidate: x.x.x
  Version table:
     x.x.x 500
        500 https://packages.microsoft.com/repos/edge stable/main amd64 Packages

If the output shows a version number under Candidate, the repository is working. Installed: (none) confirms the package has not been installed yet.

Install Microsoft Edge Stable on Debian

With the repository configured, install the stable package:

sudo apt install microsoft-edge-stable

Optional: Install Microsoft Edge Beta or Dev on Debian

If you want to preview upcoming features or test changes before they reach the stable channel, install the beta or dev builds. They run alongside the stable version in a separate profile. Microsoft updates stable every 6 weeks. Beta receives features about 6 weeks ahead of stable, and dev updates weekly with experimental changes.

Install the beta build:

sudo apt install microsoft-edge-beta

Install the dev (nightly-style) build:

sudo apt install microsoft-edge-dev

Stick with stable for daily work. Beta is useful for previewing upcoming features with reasonable stability, while dev suits testing experimental browser behavior or validating web apps against future Edge releases. Neither is recommended on production systems.

Verify Microsoft Edge Installation on Debian

Confirm Edge installed correctly:

microsoft-edge --version

Microsoft Edge x.x.x

If you installed beta or dev builds, check those versions with microsoft-edge-beta --version or microsoft-edge-dev --version.

Launch Microsoft Edge on Debian

Start Microsoft Edge from the Terminal

You can start Edge directly from a terminal session. This is useful when you want to see log messages in real time or launch a specific channel with flags. Use the command that matches the build you installed:

microsoft-edge

microsoft-edge-beta

microsoft-edge-dev

Launch Microsoft Edge from the Desktop Environment

For everyday use, you will typically start Microsoft Edge from your graphical desktop environment. On GNOME-based desktops, follow these steps:

1. Click Activities in the top-left corner of the screen.
2. Select Show Applications (the grid of dots icon, usually at the bottom-left of the screen).
3. Scroll through the application list or use the search box to look for Microsoft Edge, then click the icon to launch the browser.

To set Microsoft Edge as your default browser from the command line, use one of these commands depending on your desktop environment. On systems that support xdg-utils:

# Set Edge as default for the current user
xdg-settings set default-web-browser microsoft-edge.desktop

# Alternatively, use update-alternatives (system-wide selection, may require a .desktop name)
sudo update-alternatives --config x-www-browser

Manage Microsoft Edge Updates and Removal on Debian

Update Microsoft Edge on Debian

Microsoft Edge receives security fixes and feature updates through APT, just like other Debian packages. To check for updates across all configured repositories, including Microsoft’s:

sudo apt update

To upgrade Microsoft Edge along with other available package updates:

sudo apt upgrade

If you want to prevent a package from being upgraded (for example, to keep a stable channel pinned while you test beta/dev), you can hold it with apt-mark:

# prevent upgrades to the stable package
sudo apt-mark hold microsoft-edge-stable

# later, to allow upgrades again:
sudo apt-mark unhold microsoft-edge-stable

For more control you can use APT pinning via /etc/apt/preferences.d/. Pinning allows finely grained control over which versions or origins are preferred. See your distribution documentation for details.

If you prefer to upgrade only Edge without touching the rest of the system, target the specific package for the channel you installed, for example:

sudo apt install --only-upgrade microsoft-edge-stable

Remove Microsoft Edge from Debian

Remove the Microsoft Edge Package

If you no longer need Microsoft Edge, remove the package for the channel you installed:

sudo apt remove microsoft-edge-stable

sudo apt remove microsoft-edge-beta

sudo apt remove microsoft-edge-dev

To also remove configuration files stored under /etc, you can use purge instead of remove:

sudo apt purge microsoft-edge-stable

Clean up orphaned dependencies:

sudo apt autoremove

Remove the Microsoft Edge Repository

After fully removing Microsoft Edge, clean up the repository definition:

sudo rm /etc/apt/sources.list.d/microsoft-edge.sources

After removing the repository file, refresh the package list so APT no longer queries the Microsoft Edge repository:

sudo apt update

Remove the Microsoft Edge GPG Key

After removing both the Edge packages and repository, you can delete the now-unused GPG keyring file from /usr/share/keyrings:

sudo rm /usr/share/keyrings/microsoft-edge.gpg

Verify Repository Removal

Confirm the Microsoft Edge repository and packages are no longer visible to APT. First refresh the package cache, then check:

sudo apt update
apt-cache policy microsoft-edge-stable

N: Unable to locate package microsoft-edge-stable

This message confirms APT no longer knows about the Microsoft Edge package. If the output still shows version candidates from the Microsoft repository, the repository file or stale cache data still exists. Run sudo apt update after removing the repository file and check again.

Optional: Remove Microsoft Edge User Data

Removing the package does not automatically delete your browser profile data, which includes history, extensions, and cached files. If you want to fully wipe Microsoft Edge data for your current user, first identify what will be removed:

ls -la ~/.config/microsoft-edge* ~/.cache/microsoft-edge* 2>/dev/null

The following commands permanently delete all Microsoft Edge profile data for your account, including saved passwords, bookmarks, browsing history, extensions, and cached files. This cannot be undone. If you want to preserve any data, back up the directories first with cp -r ~/.config/microsoft-edge* ~/edge-backup.

Close the browser, then remove the configuration and cache directories:

rm -rf ~/.config/microsoft-edge*
rm -rf ~/.cache/microsoft-edge*

Run the removal as the user who owns the profile (do not prefix with sudo unless you intentionally need to remove another user’s data).

Troubleshoot Microsoft Edge Issues on Debian

Fix Signed-By Conflicts from a Previous extrepo Setup

If you previously used Debian’s extrepo tool to add the Edge repository and now follow the manual method above, APT will report a Signed-By conflict because both sources point to different GPG key paths:

Error: Conflicting values set for option Signed-By regarding source https://packages.microsoft.com/repos/edge/ stable: /var/lib/extrepo/keys/edge.asc != /usr/share/keyrings/microsoft-edge.gpg

Remove the extrepo configuration to resolve the conflict:

sudo extrepo disable edge
sudo rm /etc/apt/sources.list.d/extrepo_edge.sources
sudo apt update

Resolve Duplicate Repository Files from Edge Channels

If you install multiple Edge channels over time, the packages may create separate repository files such as microsoft-edge.list, microsoft-edge-beta.list, and microsoft-edge-dev.list under /etc/apt/sources.list.d/. When these entries overlap with a consolidated .sources file, APT warns that the repository is configured multiple times:

W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/microsoft-edge.sources and /etc/apt/sources.list.d/microsoft-edge.list

First, check which repository files exist:

ls -la /etc/apt/sources.list.d/microsoft-edge*

To clean up redundant Edge repository files while preserving your canonical .sources file, remove only the legacy .list entries:

# Remove legacy .list files (suppress errors if none exist)
sudo rm -fv /etc/apt/sources.list.d/microsoft-edge.list /etc/apt/sources.list.d/microsoft-edge-beta.list /etc/apt/sources.list.d/microsoft-edge-dev.list 2>/dev/null

This targets specific .list filenames rather than using wildcards, which prevents accidentally deleting your .sources configuration. After cleanup, run sudo apt update to verify no duplicate warnings appear.

Fix GPG Errors (NO_PUBKEY or Invalid Signature)

If APT reports a NO_PUBKEY or an invalid signature, confirm the keyring exists and the Signed-By path in your .sources or .list file is correct. Re-import the key if needed:

# Re-download and install the key
curl -fsSL https://packages.microsoft.com/keys/microsoft.asc | sudo gpg --dearmor -o /usr/share/keyrings/microsoft-edge.gpg
sudo apt update

Fix 404 or Suite Not Found Errors

If apt update reports a 404 for the repository suite, confirm the Suites: value matches what Microsoft publishes. Inspect the repo index to see available suites:

# List available suites on the vendor server
curl -fsSL https://packages.microsoft.com/repos/edge/dists/

Fix Architecture Mismatch

If packages are unavailable for your architecture, confirm the system architecture and the repo’s published architectures:

dpkg --print-architecture
# If the repo lacks your arch, you will see no candidate packages for Edge
apt policy microsoft-edge-stable

Fix Hardware Acceleration Problems

If Edge feels sluggish or videos stutter, hardware acceleration may be disabled or incompatible with your GPU drivers. Common symptoms include high CPU usage during video playback and tearing or dropped frames on high-resolution displays.

Check the current GPU status by navigating to edge://gpu in the address bar. Look for entries showing “Software only” or “Unavailable” which indicate hardware acceleration is not active:

Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Video Decode: Unavailable

To enable hardware acceleration, open Settings, navigate to System and performance, and toggle “Use hardware acceleration when available” to on. Restart Edge for the change to take effect. If problems persist with proprietary NVIDIA drivers, launch Edge with additional flags:

microsoft-edge --disable-gpu-driver-bug-workarounds --enable-gpu-rasterization

After restarting, return to edge://gpu and verify the status shows “Hardware accelerated” for the relevant features.

Fix Wayland Display Server Compatibility

On Debian systems running Wayland instead of X11, Edge may default to XWayland compatibility mode. Check your current session type:

echo $XDG_SESSION_TYPE

wayland

If you see “wayland” but Edge windows appear blurry on HiDPI displays or touchscreen gestures do not work, Edge is running through XWayland. Launch Edge natively on Wayland with:

microsoft-edge --enable-features=UseOzonePlatform --ozone-platform=wayland

To make this permanent, create a custom launcher script or edit /usr/share/applications/microsoft-edge.desktop to add the flags to the Exec line. Verify native Wayland mode by checking edge://gpu where the “GL_RENDERER” should show your GPU instead of “llvmpipe” or similar software renderers.

Fix Video Codec and DRM Playback Issues

Streaming services like Netflix, Disney+, and others require Widevine DRM support. If you see error messages like “This content requires Widevine” or playback fails with “M7111-1331-2206” error codes on Netflix, the DRM module may need updating.

Navigate to edge://components and locate “Widevine Content Decryption Module”. Click “Check for update” to ensure you have the latest version:

Widevine Content Decryption Module - Version: 4.10.x
Status: Component updated

For codec issues with VP9 or H.264 video causing “Video playback error” messages, install additional codec libraries. If you have enabled contrib and non-free repositories on Debian, install the extra codecs:

sudo apt install libavcodec-extra

Restart Edge and retry playback. Verify codecs loaded correctly at edge://media-internals.

Fix Microsoft Account Sync Failures

If Edge displays “Sync is paused” or “Can’t connect to sync” errors, authentication issues are usually the cause. Common error messages include “Sync has been turned off by your administrator” even on personal accounts, or the sync icon showing a persistent warning triangle.

First verify your Debian system clock is accurate, as sync services reject authentication tokens when system time drifts more than a few minutes:

timedatectl status | grep -E 'Local time|synchronized'

               Local time: Tue 2025-12-18 10:30:00 EST
System clock synchronized: yes

If the clock is not synchronized, enable NTP sync:

sudo timedatectl set-ntp true

Additionally, check that ca-certificates is installed and current so Edge can validate SSL certificates during the OAuth login flow:

sudo apt install --reinstall ca-certificates

If sync continues failing, sign out from Settings, clear browsing data including cookies and site data, restart Edge, then sign in again with a fresh authentication session.

Frequently Asked Questions

Conclusion

Edge updates alongside the rest of your Debian packages through APT, so new releases and security patches land automatically. For alternative browsers, see Google Chrome on Debian, Chromium on Debian, Firefox on Debian, or Brave on Debian. If video playback needs extra codecs, the contrib and non-free repository guide on Debian covers enabling libavcodec-extra.