Ask
46
@layer_shift_lu ·

How do I get the classic full right-click menu back on Windows 11 25H2, and cleanly undo it later? Workaround

Follow-on from the slow-menu thread. I want the old single full menu as the default on a build 26200 machine, not the two-step one. I know there's a registry key doing the rounds, but before I run it on machines I support I want three things answered:

  1. what exactly is the key, and does it still do anything on current builds?
  2. how do I revert it cleanly if an update or an app misbehaves afterwards?
  3. is there a way to get the same result without touching the registry at all?

Context: I maintain a handful of machines for family who are three hours away, so "can I talk someone through putting it back over the phone" matters far more to me than whether it looks tidy.

11 answers Share
Report

Answering anonymously — a moderator will review it first.

  • @monitor_riser_mo · 2h ago · 3 replies

    The key lives in your own user hive, which is what makes it low risk — nothing machine-wide changes and other accounts on the same PC are unaffected.

    Apply, in a normal command prompt:

    reg add "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}\InprocServer32" /f /ve
    

    That creates the CLSID key with an InprocServer32 subkey whose (Default) value is present but empty. The empty value is the entire trick — if (Default) is simply unset rather than set-to-empty, nothing happens and you'll swear the key doesn't work.

    Then restart the shell so it re-reads:

    taskkill /f /im explorer.exe
    start explorer
    

    Revert:

    reg delete "HKCU\Software\Classes\CLSID\{86ca1aa0-34aa-4e8b-a509-50c905bae2a2}" /f
    

    …and restart Explorer again. Two commands each way, both per-user, both phone-friendly.

    38
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @syncthing_soup · 2h ago

      Signing out and back in works instead of killing explorer, if you'd rather not have the taskbar vanish mid-call with a relative.

      6
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @semver_sid · 2h ago

      Two things trip people up on this constantly: a stray space in front of the opening brace when the GUID is pasted, and putting it under HKLM instead of HKCU. If it didn't take, open regedit and read the key name character by character before you go looking for exotic explanations.

      10
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @obsolete_by_now · 2h ago · 3 replies

    Heads up before you bother: this got removed in 24H2. The key does nothing on current builds.

    26
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @crypt_cass · 2h ago

      Not quite, and the distinction matters for someone deciding whether to try it.

      The reports are mixed rather than settled. Plenty of people are running it on 26200 right now, and the write-ups calling it deprecated are describing "this stopped working for some people on newer builds", not "Microsoft deleted the code path". What is unambiguously true, and is the thing worth telling the person asking: it was never a supported setting, so nobody owes you a working key after the next feature update.

      So: try it, it takes ten seconds and it's your own hive. If the menu doesn't change after an Explorer restart, you have your answer for your build and you delete the key again.

      19
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
    • @obsolete_by_now · 2h ago

      Fair correction — I was going off a single article. Just ran it on my own 26200 box and it does take, so I'll stop repeating that.

      5
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @crypt_cass · 2h ago

    Zero-registry answer, and the one I'd actually deploy to family: hold Shift while right-clicking, or press Shift+F10 with something selected. You get the full menu immediately.

    It's an extra key instead of an extra click, and there is nothing to undo when something behaves strangely in six months. For machines you support remotely and can't easily poke at, that trade is worth a lot more than it looks on paper — the failure mode of a habit is "they forget", and the failure mode of a registry hack is a phone call where you're dictating a GUID.

    21
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @node_red_ned · 2h ago

    There are third-party shell customisers and alternative file managers that will give you a normal menu without registry surgery, and some of them are genuinely nice.

    I'd still be conservative about what you install into explorer.exe on machines you support at a distance. Anything that loads into the shell can also take the shell down with it, and "my desktop keeps flickering and I can't open anything" is a far worse support call than "the menu has two steps". For relatives: Shift first, registry key second, extra software a distant third.

    14
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
  • @otis_haverford · 2h ago · 2 replies

    One thing to know before you standardise on the hack. The reported plan for the redesigned menu explicitly includes built-in controls to show, hide and reorder entries, with the stated intent of making registry edits unnecessary for this.

    That has not shipped, it isn't in an Insider build as far as anyone has demonstrated, and what's circulating is coverage of a private demo rather than a changelog entry — so don't wait for it. But it does mean the hack has a shelf life, and the day it stops being needed nothing will announce itself. Keep your revert command somewhere you'll find it.

    12
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report
    • @thea_mandel · 2h ago

      Save both commands in a text file on the machine itself, on the desktop, named something obvious. Future you, on the phone with your mother, will not remember that GUID.

      5
      Share
      Reply

      Answering anonymously — a moderator will review it first.

      Report
  • @thea_mandel · 6h ago

    Small operational thing: export the CLSID branch before you change anything (regedit, right-click the key, Export) so a revert is a double-click even if you fat-finger the delete command later.

    And re-check after the next feature update. If a future build ignores the key, the symptom is simply that the menu is back to two steps — no error, no log entry, nothing to alert you. If someone rings you saying "the menu changed again", that's what it is.

    8
    Share
    Reply

    Answering anonymously — a moderator will review it first.

    Report