Tabbed Console starts here

[2018-06-29: Important Note: As announced in the release notes for Windows 10 Insider build 17704, Sets and Tabs will NOT ship in the next mainstream release of Windows (codenamed RS5). Please read the first bullet under the heading "General changes, improvements, and fixes for PC" for more details.]


[2018-04-16: Updated to better reflect "Sets" terminology]

For quite a while now, the most up-voted open item in our Windows Console UserVoice has been an ask for Console to support multiple tabbed pages.

In Windows 10 Insider build 17618, the first taste of the new "Sets" feature built by the Windows Shell team (thanks all!) has arrived. Sets allow users to group multiple apps together, and switch between them using "tabs" in the title-bar. You can read more about tab sets in the Windows 10 Insiders build 17618 announcement post.

The new "Sets" UX is being applied liberally to many Windows apps and tools, including File Explorer, and … in our case … Windows Console! 🙂

So what does the Sets-enabled Console look like?

In the screenshot below, you can see that the PowerShell Console has one tab in the title-bar, indicating that this set contains one member app! To the right of this tab, is a + button that you can click to create a new tab (alternatively, you can create a new tab by hitting WIN + CTRL + T).

Here are a few keyboard shortcuts you can try out:

  • Ctrl + Win + Tab – switch to next tab
  • Ctrl + Win + Shift + Tab – switch to previous tab
  • Ctrl + Win + T – open a new tab
  • Ctrl + Win + W – close current tab.


  1. The Tabbed Console feature is very new and not yet finished!
  2. Currently, when you hit the new tab button (or hit WIN + CTRL + T), you'll see a "new tab" page
  3. We're working with the Shell Tabs team to populate the new tab page with useful links in future builds and we'd love to hear your thoughts & suggestions
  4. Please, submit Tabbed Console feedback via the Windows 10 Feedback Hub app (Desktop Environment --> Sets*) which will routed your feedback directly to the Shell team!
  5. Please DO NOT file tabbed Console bugs on the Console team's GitHub issues page

Thanks in advance for your support & feedback! We look forward to hearing from you!

Comments (7)

  1. David Noble says:

    Finally: A reason to install a Windows 10 Insiders build!

  2. Fernando Madruga says:

    Why the WIN key? What are Ctrl+Tab and Ctrl+Shift+Tab being used for? Seems overkill 3 and 4 keys combos when 1 less is more common (Win is mostly a dead key anyway, unless you’re using Win+R or similar global hotkeys)…

    1. The Windows key is FARRR from a dead key. It’s used in MANY systemwide shortcuts:

      1. Chris Riggs says:

        The point is:
        Why the WIN key? What are Ctrl+Tab and Ctrl+Shift+Tab being used for? Seems overkill 3 and 4 keys combos when 1 less is more common

        1. The Windows key is reserved for system-wide chords, for example, Win + V uses the new system-wide Cloud Clipboard pasting mechanism.

          Most CTRL or ALT chords are app-centric (although ALT + TAB is a special-case system-wide chord for a LONG time).

          1. Hardistones says:

            “App-centric”? Any app in the foreground should own whatever key combinations are pressed. It does not need the Win key. I hope you hear your own contradiction.

          2. That’s never been the case. Some key chords are system-reserved and are handled by the OS, not the app (e.g. CTRL + ALT + DEL).

Skip to main content