Windows 11 Insiders: New Win+- and Win+Shift+- Dash Shortcuts

Windows 11 Insiders can now insert an en dash (–) and an em dash (—) with two simple keyboard combos — Win + - for an en dash and Win + Shift + - for an em dash — a small, practical change that removes a long-standing friction point for writers, editors, and anyone who types punctuation frequently.

Background​

Windows has long offered several ways to type typographic dashes — none of them particularly elegant for everyone. Power users have relied on numeric Alt codes (Alt + 0150 for en dash, Alt + 0151 for em dash), many people use the Emoji & Symbols panel, and some editors perform app‑specific auto‑replacements. Laptops, tenkeyless keyboards, and users without a numeric keypad often find those options awkward or slow. The recent Insider additions aim to provide a system-level, discoverable, and consistent input method across apps.
Microsoft exposed the shortcuts in recent Windows Insider preview builds — specifically in Dev Channel 26200.5761 and Beta Channel 26120.5770 (the feature rollout is staged, so the presence of the build does not guarantee immediate availability on every device). The Windows Insider release notes and community reporting confirm the mapping and outline known exceptions.

---

What changed: the shortcuts and the scope​

The exact keystrokes​

• Win + - → inserts an en dash (U+2013).
• Win + Shift + - → inserts an em dash (U+2014).

Because this is implemented at the operating‑system input layer, the insertion is designed to work across most text controls — Notepad, Word, browser text boxes, chat clients, and many third‑party apps — wherever the OS can inject standard Unicode characters. Independent hands‑on tests and tech coverage corroborate the system‑level behavior.

Build and rollout details​

The mapping first appears in the Dev Channel build 26200.5761 and the Beta Channel build 26120.5770. Microsoft uses a controlled feature rollout model for Insider features: the code can be present in the build while a server-side flag gates which devices see the feature. That means it may take time for the shortcuts to appear for all Insiders, and public availability will follow after further validation.

---

How to try it now (Insider route)​

If you want the feature the official way, follow these broad steps:

• Join the Windows Insider Program via Settings → Windows Update → Windows Insider Program.
• Enroll the device in the Dev or Beta channel depending on your tolerance for preview software.
• Update Windows and confirm the build number (WinVer or Settings → About). Look for Dev 26200.5761 or Beta 26120.5770 or a later build that lists the input tweak in the Insider notes.
• Reboot, open a text field, and test Win + - and Win + Shift + -. If it doesn’t work immediately, remember the feature may be server‑toggled and could take time to appear.

These steps are the safest path for users who want to remain on Microsoft‑supported preview builds; however, the staged rollout means you might not see the behavior immediately even after hitting the right build number.

---

A community shortcut: enabling early with ViVeTool (risks and steps)​

Some enthusiasts are enabling the feature early using the community tool ViVeTool, which flips hidden feature flags present in Windows builds. The experimental feature ID observed in community reports is 58422150 (feature name reported as “EnAndEmDash”). Note: enabling server‑gated features via third‑party tooling is inherently unsupported by Microsoft and carries potential stability, security, and update-side effects — treat it as an advanced, at‑your‑own‑risk procedure.
If you choose to proceed despite the warnings, the commonly reported steps are:

• Download ViVeTool and extract it to a folder (for example, C:\ViVeTool).
• Open an elevated Command Prompt (Run as Administrator).
• Change to the ViVeTool directory: cd C:\ViVeTool.
• Execute: vivetool /enable /id:58422150.
• Restart Windows and test Win + - and Win + Shift + -.

Important cautions about this route:

• ViVeTool is a third‑party utility used widely by the community to flip feature flags; it does not add code but disables/enables flags Microsoft places in builds. Using it can make your system behave in ways Microsoft did not intend for your device, and it may affect support eligibility or system stability.
• Always back up critical data before toggling preview flags or installing Insider builds. Avoid using preview or modified systems on production machines.

---

Why this matters: practical benefits​

This is a small change with outsized practical return for a subset of users — particularly writers, editors, journalists, academics, and anyone who types often.

• Flow and speed: A single memorable keystroke avoids interrupting writing flow to open the emoji/symbol picker, use a Character Map, or roll the numeric keypad. That saves seconds that add up over hours of writing.
• Parity with macOS ergonomics: macOS users have relied on Option + - and Option + Shift + - for years; this addition narrows that usability gap and removes one reason typography-focused folks might prefer macOS.
• Better typography by default: When producing correct punctuation becomes less frictioned, people are more likely to use en and em dashes properly instead of substitutes like double hyphens or commas.
• Laptop-friendly: Users on compact keyboards without numeric keypads gain parity with full‑size keyboard users without needing external tools.

---

Accessibility and shortcut conflicts​

The Magnifier exception​

Microsoft explicitly warns that if Magnifier (the accessibility zoom tool) is active, Win + - will continue to perform Magnifier’s zoom‑out action rather than insert an en dash. This preserves existing accessibility shortcuts but creates a direct conflict for users who both rely on Magnifier and want the dash shortcut. IT teams and users relying on accessibility tooling should validate behavior in their setup and consider possible remaps or workflow changes.

Other conflicts​

• Third‑party remappers: Tools such as AutoHotkey, PowerToys Keyboard Manager, vendor-specific keyboard drivers, or enterprise keyboard policies may intercept or override the Win key or the hyphen/minus key. That can block or change the expected insertion behavior. Test with your typical keyboard utilities running.
• Application-level capture: Some apps (e.g., specialized terminal emulators, virtual machines, remote desktop sessions, or Electron apps that capture input) may not accept injected characters the same way. The shortcut’s system‑level implementation increases the chance it will work, but app behavior is still variable.

---

International keyboard layouts and edge cases​

Keyboard layouts differ globally. The - (minus/hyphen) key is not in the same physical place on all keyboards, and in some layouts it requires modifiers. That means the new shortcut maps to the physical key Windows expects in the U.S./UK layout model, and behavior may vary on localized keyboards.

• Users with non‑QWERTY layouts, compact laptop keyboards, or alternative hardware should test the feature in their locale. Some users reported needing to press additional modifiers on certain layouts.

Additionally, remote inputs (RDP) and some virtualized scenarios may not translate the key combination consistently across the client and host. Test any workflow involving remote sessions before deploying broadly.

---

Enterprise and IT considerations​

Small OS-level changes can have outsized operational impacts when scaled across hundreds or thousands of endpoints. IT and security teams should consider:

• Controlled rollout and testing: Treat this like any other preview feature — validate in a pilot ring with representative devices, input utilities, and accessibility configurations. Document behavior and user guidance for employees.
• Group Policy / Intune: When Microsoft moves this to broad release, expect enterprise controls and documentation to follow. Until then, test for any interactions with existing policies that remap or disable the Windows key.
• Kiosk and locked-down environments: Systems that deliberately suppress Windows key behavior for security (kiosk modes, exam computers, certain POS setups) may need policy updates or exception handling.
• Accessibility teams: Coordinate with accessibility owners to reconcile the Magnifier exception and consider alternative workflows for users who depend on Magnifier.

---

Alternatives and workarounds (if you don’t have the shortcut)​

If you can’t or won’t run Insider builds, several practical alternatives remain:

• Emoji & Symbols panel: Win + . (period) or Win + ; opens the panel and exposes punctuation — reliable but slower and mouse-dependent.
• Alt codes: Alt + 0150 and Alt + 0151 — requires a full numeric keypad and Num Lock.
• PowerToys Keyboard Manager: Remap a keystroke like Alt + - to paste U+2013/U+2014. Requires PowerToys and admin permission on some systems.
• AutoHotkey: Create an expansion such as -- → em dash system‑wide. Powerful but adds a third‑party dependency and potential policy or security considerations in locked environments.
• App autoformat: Use app‑specific autocorrect (Word, Outlook, Google Docs) to convert typed patterns into dashes. Works in-app but not globally.

---

The technical detail: Unicode and input layer​

The system inserts standard Unicode characters: the en dash is U+2013 and the em dash is U+2014. Implementing insertion at the OS input layer (rather than a per‑app shortcut) increases the odds that the resulting character will be present in the receiving control as expected. That said, the receiving application still controls how it displays or processes Unicode input (for example, normalized text, conversion rules, or font fallback). When in doubt, test the target application to ensure the dash displays and behaves as expected.

---

Risks, tradeoffs, and things to watch​

• Shortcut collision with accessibility features is the most significant immediate tradeoff; preserving Magnifier behavior prevents regressions for low‑vision users but reduces universality of the new shortcut.
• Server-side gating means build numbers alone are not proof that the feature will be visible — be wary of guides that assume the build is sufficient. Expect staggered visibility.
• Third‑party tooling and remaps may break or change the behavior unpredictably; PowerToys, AutoHotkey, and vendor drivers are common sources of conflict.
• Unsupported toggles: using ViVeTool or similar utilities to flip server‑gated flags carries risk and falls outside Microsoft’s support path. Back up before changing flags, and avoid modifying production devices.
• Internationalization bugs: local keyboard layouts may yield inconsistent key mappings or require different modifier combinations. Test in local contexts before broadizing usage.

Where a claim or detail could change quickly — for example, exact build numbers that ship with the toggle enabled, or Microsoft adding enterprise controls — treat the current information as a snapshot from the Insider cycle and verify against official Windows Insider release notes before taking action in managed environments.

---

Recommendations (for writers, power users, and IT)​

• Writers and editors: adopt the shortcut as soon as it lands on a test device — it’s a safe productivity win that reduces friction and improves typographic quality. For production-critical writing machines, prefer waiting for public release or test in a non‑critical Insider device first.
• Power users: if you are comfortable with Insider builds and understand the staging model, enroll a spare device or VM to experiment. Avoid enabling insider flags with community tools on machines you rely on daily.
• IT and accessibility managers: include the new input behavior in your pilot testing checklist. Validate interactions with Magnifier, keyboard remappers, and remote sessions. Prepare user guidance that documents the Magnifier caveat and an alternative workflow for affected employees.
• Documentation authors and keyboard utility maintainers: update help pages and mappings to avoid accidental conflicts with the OS shortcut once it reaches broader availability.

---

Conclusion​

This small keyboard tweak is exactly the kind of low‑friction usability improvement that quietly makes a real difference for people who type a lot. By adding Win + - and Win + Shift + - to the OS input toolkit, Microsoft reduces the friction for correct typographic punctuation, levels the playing field for laptop users without numeric keypads, and brings Windows closer to parity with long‑standing macOS conveniences. The feature’s immediate limitations — most notably the Magnifier conflict and staged rollout — are important to acknowledge, especially for accessibility and enterprise contexts, but they don’t negate the net benefit for most typists. Insiders can test the change via the Dev/Beta channels and, for advanced users only, via ViVeTool feature toggles; everyone else should expect the shortcut to arrive more broadly as Microsoft widens the rollout after validation.
Ultimately, this is a reminder that sensible, incremental input improvements — not dramatic redesigns — are often the most welcome updates for everyday productivity.

---

Source: BetaNews Microsoft makes it easier for Windows 11 users to type em and en dashes with keyboard shortcuts