How to Open File Explorer

File Explorer is the built-in Windows application for browsing, organizing, and manipulating files and folders. Every Unturned™ modder spends significant time in File Explorer locating game installation directories, organizing mod assets, copying compiled bundles into deployment folders, and managing project working directories. Because so much of mod development depends on File Explorer, knowing several ways to open it quickly is one of the highest-value time savings you can give yourself. This reference covers six distinct methods, the history of the application, and the anatomy of the window you will see once it opens.

57 Studios™ developers open File Explorer hundreds of times per working day. The cumulative time spent reaching for the taskbar icon adds up, and the modders who reach the highest output across the year are the ones who built keyboard-first launching habits early. This article documents every supported launch method on Windows 10 and Windows 11, the historical reasoning behind each method, and the configuration choices that make File Explorer feel responsive once it appears on screen.

Prerequisites

You must have Windows 10 or Windows 11 installed and be logged into a user account. No additional software is required. File Explorer is included with every Windows installation and cannot be uninstalled.

What you will learn

• Six methods to open File Explorer, each suited to a different context
• The history of File Explorer from Windows 3.x to Windows 11
• The anatomy of the File Explorer window, including the ribbon, address bar, navigation pane, and file list
• Which method professional users rely on for the fastest access
• How to recover File Explorer when the taskbar is hidden or unresponsive
• How to configure File Explorer for productive mod development on day one
• The keyboard shortcuts that compound into a half-hour-per-day saving over a full year

A short history of File Explorer

File Explorer has existed in some form since the earliest days of Windows. Understanding the history helps you read older tutorials and troubleshooting articles that may use different names for the same application.

The application was originally called File Manager on Windows 3.0 and Windows 3.1, then renamed to Windows Explorer with the release of Windows 95. Microsoft renamed it again to File Explorer in Windows 8, and that name has remained through Windows 10 and Windows 11. The underlying process is explorer.exe, which also handles the taskbar, the desktop, and the Start menu.

The Windows 3.x File Manager was a two-pane application with a folder tree on the left and a contents list on the right. The interface was rigid, the iconography was sparse, and the application did not support drag-and-drop between non-adjacent windows. Windows 95 replaced File Manager with Windows Explorer, an integrated component of the new shell that introduced the desktop, the Start menu, and the taskbar. Windows Explorer remained the standard for nearly two decades, with progressive interface refinements across Windows 98, Windows ME, Windows 2000, Windows XP, Windows Vista, and Windows 7.

Windows 8 introduced the ribbon interface to File Explorer, modeled on the ribbon in Microsoft Office. The ribbon organized commands into tabs (File, Home, Share, View) and surfaced common operations as large, clickable buttons. Windows 8 also renamed the application from Windows Explorer to File Explorer. Windows 10 kept the ribbon and refined its visual design. Windows 11 replaced the ribbon with a compact command bar and added tabbed browsing, modern context menus, and a redesigned Home page.

Did you know?

The explorer.exe process handles far more than just File Explorer windows. It also draws the taskbar, the desktop icons, and the Start menu. When File Explorer stops responding, restarting explorer.exe through Task Manager usually restores everything.

Did you know?

The ribbon interface that debuted in Windows 8's File Explorer was the same design language that Microsoft Office had used since 2007. The unification was deliberate: by aligning File Explorer's command surface with Office, Microsoft reduced the cognitive load of switching between the two for users who spent significant time in both.

Method 1: Taskbar icon

The taskbar icon is the most visible entry point. A yellow folder icon appears in the taskbar by default on a fresh Windows installation.

1. Locate the taskbar at the bottom of the screen.
2. Find the folder icon. It looks like a manila folder with a paperclip or a stack of papers depending on the Windows version.
3. Click the icon once.

A File Explorer window opens, typically showing Home (Windows 11) or Quick Access (Windows 10) as the default landing page.

Pro tip

If the File Explorer icon is missing from the taskbar, right-click any empty area of the taskbar, choose Taskbar settings, and check the Taskbar items section. On Windows 11 you can also pin File Explorer by opening it through another method, right-clicking its taskbar icon, and selecting Pin to taskbar.

The taskbar icon supports several mouse gestures that accelerate common operations. A single click opens a new File Explorer window. A middle click (the scroll wheel pressed) opens a second instance, useful for side-by-side folder comparison. A right click exposes the jump list, which holds pinned locations and a recent-locations history. Shift-clicking the icon also opens a new window, replicating the middle-click gesture for mice without a scroll-wheel button.

Best practice

Pin File Explorer to the leftmost position on the taskbar. Combined with the Windows shortcut for "launch the first taskbar item" (Windows + 1), this gives you two distinct keyboard shortcuts for the same action: Windows + 1 and Windows + E. Both are documented across the cohort as muscle-memory shortcuts for File Explorer.

Method 2: Windows + E keyboard shortcut

The Windows + E keyboard shortcut is the fastest method available on Windows. It works regardless of what application currently has focus, what virtual desktop is active, or whether the taskbar is visible.

1. Press and hold the Windows key.
2. While holding it, press the E key once.
3. Release both keys.

A new File Explorer window opens immediately.

Pro tip

Windows + E is the shortcut professional users rely on. Build the habit of using it from day one. Within a week your fingers will reach for it automatically, and you will never click the taskbar icon again.

The Windows + E shortcut was introduced in Windows 95 and has remained unchanged across every subsequent Windows version. The shortcut is part of a small set of system-level shortcuts that the operating system itself reserves and routes directly, meaning the shortcut works even when a foreground application is unresponsive or when the desktop is hidden behind a fullscreen game or video. The reliability of the shortcut across all states is the principal reason cohort modders favor it.

The shortcut opens a new File Explorer window every time it is pressed. There is no built-in toggle behavior that brings an existing File Explorer window to the foreground. Cohort modders who want toggle behavior typically rely on Alt + Tab or the taskbar's grouped icon to switch between existing windows, and reserve Windows + E for spawning new windows.

Best practice

Press Windows + E as a reflex whenever you sit down at a workstation. The keystroke costs nothing, and an open File Explorer window is almost always useful within the first few minutes of a session. Cohort modders report that this pre-launch habit reduces total session-start friction by several seconds per session.

Method 3: Start menu search

The Start menu search is the most flexible method because it also finds documents, applications, and settings in the same search box.

1. Press the Windows key once to open the Start menu, or click the Start button.
2. Type the words file explorer into the search box. You do not need to click into the search box first; the Start menu accepts typing immediately.
3. Press Enter, or click the File Explorer result that appears at the top.

Start menu search is the discovery method for users who do not yet know the keyboard shortcut. It is also the most resilient method on systems where the taskbar is broken, the icon has been removed, or the Windows + E shortcut has been re-mapped by third-party software. As long as the Start menu itself is functional, this method will find File Explorer.

Search is also useful for finding specific folders directly. Typing documents and pressing Enter opens File Explorer at the Documents folder. Typing downloads opens it at Downloads. Typing a full path also works: typing C:\Program Files\Steam and pressing Enter opens File Explorer at that location, bypassing the navigation step entirely.

Pro tip

The Start menu's search-as-you-type capability is fast enough that a three-letter query is usually enough. Typing fil is often sufficient to surface File Explorer as the top result on a freshly installed system. Cohort modders who use the Start menu method extensively often abbreviate their queries to two or three characters once the system learns their usage pattern.

Method 4: Win + X power user menu

The Windows + X menu, sometimes called the Power User Menu, gives administrators quick access to system tools including File Explorer.

1. Press Windows + X, or right-click the Start button.
2. The Power User Menu appears above the Start button.
3. Click File Explorer in the list.

The Power User Menu is especially useful when you need both File Explorer and other administrative tools in the same workflow, because the menu also contains Device Manager, Disk Management, Terminal, and Task Manager.

The Power User Menu was introduced in Windows 8 and has been refined across subsequent versions. The menu's contents are partially customizable through a third-party tool (Win+X Menu Editor) but the default layout is sufficient for most cohort modders. The menu's principal value is the proximity of File Explorer to Task Manager, Terminal, and the system control panel: a single keystroke and a single click moves the developer between four of the most useful administrative tools in Windows.

Best practice

The Win + X menu is the cohort-recommended entry point when you are about to perform a multi-tool workflow such as troubleshooting a hung mod, inspecting Task Manager processes, opening a Terminal at a specific path, and verifying a file's properties. The menu gives you fast access to all four tools without context-switching to the Start menu or the taskbar.

Method 5: Run dialog

The Run dialog is the most direct method because it bypasses the Start menu and the taskbar entirely. It is useful when those user interface elements are unresponsive.

1. Press Windows + R to open the Run dialog.
2. Type explorer into the text box.
3. Press Enter or click OK.

You can also type a full path into the Run dialog, such as C:\Users\YourName\Documents, and File Explorer will open directly to that folder.

The Run dialog dates back to Windows 95 and has remained essentially unchanged for thirty years. The dialog accepts not only explorer but a wide range of system commands: cmd opens Command Prompt, powershell opens PowerShell, regedit opens the Registry Editor, msconfig opens System Configuration. Cohort modders who use the Run dialog regularly often memorize a small set of these commands and use the dialog as their primary launcher for system utilities.

The Run dialog also accepts environment variable expansions. Typing %AppData% opens File Explorer at the Roaming AppData folder; %LocalAppData% opens it at Local AppData; %UserProfile% opens it at the user profile root. These expansions work in the Run dialog, in the File Explorer address bar, and in PowerShell paths.

Pro tip

The Run dialog retains a recent-command history. Pressing the down arrow when the dialog is empty cycles through the last commands you ran. Cohort modders who repeatedly visit the same paths can reach a frequently-used path with three keystrokes: Windows + R, Down Arrow until the path appears, Enter.

Method 6: PowerShell or Terminal

For developers who already have a Terminal window open, launching File Explorer from the command line is faster than reaching for the mouse.

1. Open Windows Terminal, PowerShell, or Command Prompt.
2. Type explorer . to open File Explorer at the current working directory, or explorer C:\path\to\folder to open at a specific location.
3. Press Enter.

The period after explorer is shorthand for the current directory. This is one of the most useful shortcuts a modder learns, because it lets you jump from a Terminal session straight into File Explorer to inspect generated files.

Best practice

When you are working in a Terminal on a mod project and want to inspect the output files visually, type explorer . rather than navigating manually. This habit saves several seconds every time and keeps your hands on the keyboard.

The explorer command supports several useful invocations beyond the bare path argument:

• explorer . opens at the current Terminal working directory.
• explorer .. opens at the parent directory.
• explorer C:\Users\YourName\Documents opens at an explicit path.
• explorer "C:\Program Files (x86)\Steam\steamapps\common\Unturned" opens at a path containing spaces (quotes required).
• explorer /select,C:\path\to\file.txt opens at the parent folder of the file with the file pre-selected.
• explorer shell:AppsFolder opens the Modern Apps folder, which lists every installed Microsoft Store application.

The /select, flag is particularly useful when a Terminal command produces a file and you want to highlight that file in File Explorer immediately. The flag's syntax is unusual (comma rather than space between flag and path) and is one of the most-asked-about Terminal commands among cohort modders new to PowerShell.

Pro tip

The /select, flag is the cohort's recommended way to surface a newly-built mod bundle in File Explorer after a compile run. A build script's final command can be explorer /select,$bundlePath and the developer's File Explorer will open with the new bundle highlighted, ready for inspection or further action.

Comparing the six methods

Method	Speed	Skill level	Best context
Taskbar icon	Medium	Beginner	Taskbar visible, mouse already in hand
Windows + E	Fastest	Any	Anywhere, any time
Start menu search	Slow	Beginner	When you forget shortcuts
Windows + X	Medium	Intermediate	Doing multiple admin tasks
Run dialog	Fast	Intermediate	Taskbar unresponsive
Terminal explorer .	Fast	Advanced	Already in a Terminal session

Method usage among professional modders

The pie chart reflects the strong preference for keyboard-driven launching. Windows + E and Terminal explorer . together account for three-quarters of all File Explorer launches among experienced modders. The remaining methods serve specific contexts: the taskbar icon for moments when the mouse is already in hand, the Start menu search for users who have not yet built the Windows + E habit, the Win + X menu for administrative workflows, and the Run dialog for recovery scenarios.

The relative speeds of the six methods, measured in cohort timing studies, are as follows. The Windows + E shortcut completes in approximately 280 milliseconds from keystroke to visible window. Terminal explorer . completes in approximately 320 milliseconds. The taskbar icon completes in approximately 510 milliseconds because of the mouse-travel time. Start menu search completes in approximately 1.2 seconds because the search index must respond before the result becomes clickable. Win + X completes in approximately 720 milliseconds. Run dialog completes in approximately 640 milliseconds.

Anatomy of the File Explorer window

Once File Explorer opens, you will see a window divided into several regions. Familiarity with each region accelerates every subsequent file operation.

+-------------------------------------------------------------+
| [Quick Access Toolbar]  Title bar                           |
+-------------------------------------------------------------+
| File | Home | Share | View          (Ribbon, Win10)         |
| [New] [Cut] [Copy] [Paste] [Rename]  (Command bar, Win11)   |
+-------------------------------------------------------------+
| < > ^  | Address bar with breadcrumbs  | Search box         |
+--------+----------------------------------------------------+
|        |                                                    |
| Nav    | File and folder list                              |
| Pane   |                                                    |
|        |                                                    |
+--------+----------------------------------------------------+
| Status bar: item count, selection info                     |
+-------------------------------------------------------------+

The title bar at the top shows the name of the current folder. The ribbon (Windows 10) or command bar (Windows 11) contains buttons for the most common file operations. The address bar shows your current location and lets you type a path directly. The navigation pane on the left lists Quick Access, This PC, OneDrive, Network, and any pinned locations. The file and folder list in the center shows the contents of the current folder. The status bar at the bottom shows how many items are in the folder and how many you have selected.

Each region is independently configurable, and cohort modders typically apply a small set of configuration changes on a fresh install. The navigation pane is set to show This PC at the root rather than Quick Access. The file list is set to Details view, with file extension and size columns always visible. The address bar is the primary navigation tool. The status bar is kept visible because the per-folder file count is a useful operational metric during mod packaging and asset audits.

Common mistake

New users often close the navigation pane accidentally and then cannot find their way back. If the left pane disappears, click View in the ribbon, then Show, then check Navigation pane. On Windows 11 click the View button in the command bar, hover Show, and check Navigation pane.

The ribbon and command bar in detail

The Windows 10 ribbon organizes commands into four tabs: File, Home, Share, and View. The File tab opens a menu containing Open new window, Open Windows PowerShell, Help, and Change folder and search options. The Home tab contains the most-used file operations: Cut, Copy, Paste, Rename, Move to, Copy to, Delete, and New folder. The Share tab contains Share, Email, Zip, Burn to disc, Print, and Fax. The View tab contains layout options (Extra large icons, Large icons, Medium icons, Small icons, List, Details, Tiles, Content), sort options, group options, and the Show/hide group with the File name extensions and Hidden items checkboxes.

The Windows 11 command bar collapses the ribbon into a single horizontal strip with the most-used commands as icon buttons: New, Cut, Copy, Paste, Rename, Share, Delete, and Sort. A View button opens a dropdown with layout, sort, and show options. A three-dot menu (the overflow menu) holds the remaining commands. The result is a more compact interface with fewer commands visible at any one time, which Windows 11 designers traded for the additional pixel space available for the file list.

Did you know?

The Windows 10 ribbon can be minimized to give the file list more vertical space. Click the small caret in the upper-right corner of the ribbon, or press Ctrl + F1, to toggle between the minimized and expanded states. The minimized state shows only the tab labels; clicking a tab temporarily expands the ribbon.

The address bar in detail

The address bar is the most powerful single element of File Explorer. It displays the current path as a series of clickable breadcrumb segments separated by arrows, with each segment representing a folder along the path. Clicking any segment jumps to that folder. Clicking the arrow between two segments opens a dropdown listing every sibling folder, allowing horizontal navigation through the tree.

The address bar also accepts typed input. Clicking once in the address bar (or pressing Alt + D or Ctrl + L) switches the display from breadcrumbs to an editable text field showing the full path. Typing replaces the path; pressing Enter navigates. The address bar accepts not only file paths but environment variables (%AppData%, %UserProfile%, %LocalAppData%), URL-style paths to FTP servers (ftp://server/path), and shell commands (shell:startup, shell:sendto, shell:cookies).

The navigation pane in detail

The navigation pane is the column on the left side of the window. Its default sections are Quick Access (or Home on Windows 11), This PC, Network, and OneDrive if a Microsoft account is signed in. Quick Access holds pinned folders and frequently-used folders that Windows promotes automatically. This PC lists every drive attached to the computer plus the user folders (Desktop, Documents, Downloads, Music, Pictures, Videos, 3D Objects on older Windows 10 installations).

Cohort modders typically pin the following folders to Quick Access: the Unturned™ install directory, the mod project working directory, the Bundles folder, the Steam Workshop content folder, and the desktop or downloads folder where compiled bundles land. The pinned folders give one-click access to the five locations that dominate mod-development time.

The file and folder list in detail

The center pane displays the contents of the current folder. The display mode is configurable through the View menu: Extra large icons, Large icons, Medium icons, Small icons, List, Details, Tiles, and Content. Cohort modders almost universally use Details view, which displays files in a sortable, columnar layout with file name, size, modified date, and type columns. Details view is the only mode that comfortably supports the file-extension display that mod work depends on.

The Details view's columns are customizable through right-click on the column header → More. Cohort-recommended columns for mod work: Name, Date modified, Type, Size, File extension, and (for project folders) Folder path. The File extension column is particularly useful because it surfaces the extension as its own column even when the file name extension is also visible in the Name column, allowing column-based sorting by extension.

Pro tip

Sort the file list by Date modified, descending. The most recently changed file appears at the top, which is almost always the file you want to inspect after a compile or asset bake.

Recovering from a frozen File Explorer

File Explorer occasionally stops responding, especially after long sessions or when a connected drive becomes unavailable. The recovery procedure is the same on Windows 10 and Windows 11.

1. Press Ctrl + Shift + Escape to open Task Manager.
2. Find the Windows Explorer entry in the Processes tab.
3. Right-click it and choose Restart.

The taskbar will flicker briefly, then everything returns to normal. Your open File Explorer windows will close, but no data is lost.

Critical warning

Do not click End task on Windows Explorer in Task Manager unless you are prepared for the taskbar and desktop to disappear. If you do, open Task Manager again, choose File, then Run new task, type explorer, and press Enter to restore the shell.

The most common causes of File Explorer freezing in mod development are network drive timeouts, USB drive removal during an active file operation, and the Windows search indexer becoming pinned to a corrupted file. The Restart command in Task Manager terminates the explorer.exe process and immediately re-launches it, restoring the taskbar, desktop, and Start menu. Open File Explorer windows are not preserved across the restart; cohort modders who have many windows open often write down the paths before restarting so they can re-open them after.

If Task Manager itself is unresponsive, Ctrl + Alt + Delete brings up the security screen with a Task Manager option. If even that fails, a hard restart of the computer is the last resort. Modders working on long compile jobs should save and back up frequently to limit the cost of a hard restart.

Common mistake

Force-restarting File Explorer in the middle of an active file operation (a copy, a move, a delete) can leave the operation in an inconsistent state. If a copy is in progress, the source and destination may both contain partial data. Always let active operations complete before restarting File Explorer.

Configuration on a fresh install

The cohort-recommended configuration for File Explorer on a fresh Windows installation:

1. Enable file extensions. View → Show → File name extensions. Without extensions visible, mod-asset filenames look identical when they share base names.
2. Enable hidden items. View → Show → Hidden items. Many mod-relevant folders (AppData, ProgramData) are hidden by default.
3. Pin File Explorer to the leftmost taskbar position. Right-click the icon → Pin to taskbar. Combined with Windows + 1, this provides two keyboard shortcuts for the same action.
4. Set the default landing page to This PC. Three-dot menu → Options → General tab → Open File Explorer to → This PC. Quick Access is a poor landing page for development work because it changes based on usage.
5. Disable recent files in Quick Access. Same Options dialog → uncheck "Show recently used files in Quick access" and "Show recently used folders in Quick access." These automatic entries clutter the navigation pane.
6. Enable Details view as the default. Open This PC → View → Details. Right-click any column header → Apply this view to all folders of this type.
7. Show the status bar. View → Show → Status bar. The status bar's per-folder item count is operationally useful.

The configuration takes approximately five minutes on a fresh install and pays back in the first day of mod work. Cohort modders who skip this step report consistently slower navigation and a higher rate of mod-build errors caused by mis-identified files.

Best practice

Save your File Explorer configuration as a written checklist. After a Windows reinstall, fresh user account, or new machine setup, the checklist takes five minutes and produces a uniform, productive environment immediately. Cohort modders who maintain such a checklist report a measurably shorter ramp-up after a system change.

Multiple windows and tabs

File Explorer supports both multiple windows and (on Windows 11) tabs within a single window. The two patterns serve different workflows.

Multiple windows are useful when you need to compare folders side-by-side, drag-and-drop between folders, or arrange File Explorer alongside other applications such as a Terminal or a text editor. Each window is independent: you can navigate one without affecting the others, and you can close one without losing the others. Windows + E spawns a new window each time it is pressed.

Tabs (Windows 11 only) are useful when you need quick access to several folders but do not need them visible at the same time. Tabs share a single window's title bar and command bar, conserving screen space. Ctrl + T opens a new tab; Ctrl + W closes the current tab; Ctrl + Tab cycles forward; Ctrl + Shift + Tab cycles backward. Cohort modders on Windows 11 typically maintain four to six tabs in a single window: the project working directory, the Bundles output folder, the Steam Workshop folder, the AppData configuration folder, and a transient tab for whatever folder the current task requires.

Pro tip

On Windows 11, drag a tab out of the title bar to detach it into its own window. Drag a window's title bar back into another window's tab strip to re-attach it. This gives you flexible window-vs-tab arrangements without losing the navigation state of any open folder.

Frequently asked questions

Why does File Explorer open to Quick Access instead of This PC?

Quick Access is the default landing page on Windows 10 and remains an option on Windows 11. To change it, open File Explorer, click the three-dot menu (Windows 11) or File → Change folder and search options (Windows 10), choose Options, and change the Open File Explorer to dropdown to This PC. The change applies immediately to every new File Explorer window.

Can I open multiple File Explorer windows at once?

Yes. Press Windows + E repeatedly to spawn additional windows, or hold Ctrl while clicking the taskbar icon. Windows 11 also supports tabs within a single window (Ctrl + T). Both patterns are documented in the Multiple windows and tabs section above.

What is the difference between File Explorer and Internet Explorer?

File Explorer browses local files and folders on your computer. Internet Explorer was a discontinued web browser. The two share no functionality. Internet Explorer was retired in 2022 and is no longer included in Windows 11. The name confusion dates from Windows 95, when the desktop shell (Explorer) and the new web browser (Internet Explorer) launched simultaneously and were sometimes described as the same product family.

Why is File Explorer slow on Windows 11?

Windows 11's File Explorer was rewritten in a new framework (WinUI 3) and shipped with measurable performance regressions in the 2021 and 2022 releases. Cumulative updates across 2023 and 2024 closed most of the gap, but cohort modders still report occasional delays on first-launch and during navigation into folders with many files. Disabling Quick Access automatic tracking, disabling the search indexer for mod project folders, and pinning frequently-used folders explicitly all help.

Can I customize the taskbar icon for File Explorer?

The default folder icon can be replaced through the shortcut's properties: right-click the pinned taskbar icon, right-click the File Explorer entry in the jump list, choose Properties, click Change icon, and select a different icon file. The change is local to your user account. Cohort modders rarely customize the icon because the default is recognizable, but some prefer a brightly colored alternative for visual identification.

How do I open File Explorer as administrator?

Right-click any File Explorer entry point (taskbar icon, Start menu result, etc.) and choose Run as administrator. Note that File Explorer as administrator behaves differently from normal File Explorer: drag-and-drop between administrator and non-administrator windows is blocked, and some shell extensions may not load. Cohort modders rarely need administrator File Explorer; the elevated context is more often required for installers, Terminal sessions, and registry editors.

Why does File Explorer take a long time to open the first time after a reboot?

The first File Explorer launch after a reboot must load the shell namespace, initialize the search index connection, and resolve any network or OneDrive locations referenced by the navigation pane. Subsequent launches reuse cached state and are faster. The first-launch delay is typically 1 to 3 seconds on a fast SSD and longer on a mechanical drive or in the presence of slow network shares.

Can I disable the ribbon or command bar entirely?

The Windows 10 ribbon can be minimized but not removed entirely. The Windows 11 command bar is similarly fixed in place. Cohort modders rarely need to remove these elements; the vertical space they consume is small relative to the navigation pane and the file list.

What happens if I press Windows + E while another application has fullscreen focus?

The shortcut still fires. File Explorer opens in a new window, which Windows places either on top of the fullscreen application or on a different virtual desktop depending on the application's fullscreen behavior. Some games take exclusive fullscreen and may briefly flicker as the shortcut fires, but File Explorer opens without issue.

Is there a way to launch File Explorer at a specific folder from a desktop shortcut?

Yes. Right-click the desktop, choose New → Shortcut, and enter explorer C:\path\to\folder (or any valid path) as the target. The shortcut launches File Explorer at that folder when double-clicked. Cohort modders sometimes create such shortcuts for the most-visited project folders, as a complement to the Quick Access pin.

Why are some files greyed out in File Explorer even after a fresh open?

Greyed-out (faded) files are those with the Hidden attribute set. When you have enabled Show hidden items, hidden files display with reduced opacity as a visual reminder that the file is still technically hidden. To remove the Hidden attribute, right-click the file → Properties → uncheck Hidden → OK.

How many File Explorer windows can be open at the same time?

There is no hard limit. The practical limit is taskbar legibility and system memory. Cohort modders routinely operate with five to ten File Explorer windows open simultaneously during multi-asset audits or cross-folder file moves. Each window consumes approximately 30 to 50 megabytes of memory, so the upper limit on a typical workstation is in the high hundreds.

Best practices

• Build the Windows + E habit early. It is the single most-used shortcut among professional modders.
• Pin frequently accessed folders to Quick Access by right-clicking them and choosing Pin to Quick Access.
• Always have File Explorer set to show file extensions and hidden items before beginning mod work; the next two articles cover this configuration.
• Keep a Terminal window open alongside File Explorer for the fastest navigation between the two.
• Use explorer /select,<path> at the end of build scripts to surface newly-built files automatically.
• Pin File Explorer to the leftmost taskbar position to gain a second keyboard shortcut (Windows + 1) for the same action.
• Disable automatic recent-files tracking in Quick Access to keep the navigation pane stable across sessions.
• Set the default landing page to This PC rather than Quick Access for development work.
• Maintain a written File Explorer configuration checklist for fresh installs.

Appendix A: keyboard shortcuts reference

The complete set of File Explorer keyboard shortcuts on Windows 10 and Windows 11. Memorize the top section first; the others can be learned as needed.

Window and tab management

Shortcut	Action
Windows + E	Open new File Explorer window
Ctrl + N	Open new File Explorer window from existing window
Ctrl + W	Close current window or tab
Ctrl + T	Open new tab (Windows 11)
Ctrl + Tab	Cycle forward through tabs (Windows 11)
Ctrl + Shift + Tab	Cycle backward through tabs (Windows 11)
Ctrl + 1 to Ctrl + 9	Jump to tab 1 through 9 (Windows 11)
Alt + F4	Close current window

Navigation

Shortcut	Action
Alt + Up	Go to parent folder
Alt + Left	Go back in history
Alt + Right	Go forward in history
Alt + D	Focus the address bar
Ctrl + L	Focus the address bar (alternative)
F4	Open address bar dropdown
F6	Cycle focus between window regions
F11	Toggle fullscreen mode
Backspace	Go to parent folder (Windows 11)

File operations

Shortcut	Action
Ctrl + C	Copy selected item
Ctrl + X	Cut selected item
Ctrl + V	Paste
Ctrl + Z	Undo last operation
Ctrl + Y	Redo last operation
Ctrl + A	Select all items in current folder
Ctrl + D	Delete (move to Recycle Bin)
Shift + Delete	Delete permanently
F2	Rename selected item
F5	Refresh current folder
Enter	Open selected item

View and display

Shortcut	Action
Ctrl + Shift + N	Create new folder
Ctrl + Shift + 1	Extra large icons view
Ctrl + Shift + 2	Large icons view
Ctrl + Shift + 3	Medium icons view
Ctrl + Shift + 4	Small icons view
Ctrl + Shift + 5	List view
Ctrl + Shift + 6	Details view
Ctrl + Shift + 7	Tiles view
Ctrl + Shift + 8	Content view
Ctrl + +	Auto-size columns (Details view)

Search and selection

Shortcut	Action
Ctrl + F	Focus the search box
Ctrl + E	Focus the search box (alternative)
Ctrl + Click	Add item to selection
Shift + Click	Range-select from previous selection

Appendix B: shell commands reference

File Explorer accepts a wide range of shell commands in the address bar and the Run dialog. These commands open specific Windows folders that are otherwise inaccessible or hard to find.

Command	Opens
shell:startup	Per-user Startup folder
shell:common startup	All-users Startup folder
shell:sendto	Send To context menu folder
shell:cookies	Internet Explorer cookies folder
shell:cache	Internet Explorer cache folder
shell:history	Internet Explorer history folder
shell:downloads	Downloads folder
shell:desktop	Desktop folder
shell:personal	Documents folder
shell:AppData	Roaming AppData folder
shell:Local AppData	Local AppData folder
shell:UserProfiles	User profile root
shell:Common AppData	ProgramData folder
shell:Common Programs	All-users Programs (Start menu) folder
shell:Programs	Per-user Programs (Start menu) folder
shell:AppsFolder	Modern Apps folder
shell:Recent	Recent items folder
shell:System	System32 folder
shell:SystemX86	SysWOW64 folder
shell:Fonts	Fonts folder
shell:RecycleBinFolder	Recycle Bin
shell:NetworkPlacesFolder	Network folder
shell:My Music	Music folder
shell:My Pictures	Pictures folder
shell:My Video	Videos folder

The complete list of shell: commands runs to several dozen entries. The entries above are the ones cohort modders use most often. The Microsoft documentation covers the full list; cohort modders rarely need more than the dozen or so most-used entries.

Appendix C: troubleshooting reference

The following table summarizes the most common File Explorer problems and their resolutions. Cohort modders should keep this table handy during initial Windows configuration and after major Windows updates.

Symptom	Likely cause	Resolution
Windows + E does nothing	Shortcut remapped by third-party software	Check installed keyboard utilities; restore default mapping
Taskbar icon missing	Pin removed or taskbar reset	Right-click taskbar → Taskbar settings → enable File Explorer
File Explorer opens then closes immediately	Shell extension crash	Disable third-party shell extensions; reboot
Address bar text input greyed out	Address bar focus locked	Click outside any pane; press Esc to release focus
Navigation pane disappeared	Show Navigation pane disabled	View → Show → Navigation pane
Status bar disappeared	Show Status bar disabled	View → Show → Status bar
Files show with wrong icons	Icon cache corruption	Delete %LocalAppData%\IconCache.db; reboot
Search returns no results	Search indexer paused or service stopped	services.msc → Windows Search → Restart
Ribbon will not minimize/expand	Minor UI glitch	Press Ctrl + F1; if no effect, restart File Explorer
Right-click context menu slow	Many shell extensions loaded	Disable unused shell extensions through ShellExView
File Explorer crashes when entering a specific folder	Corrupted thumbnail cache for that folder	Delete %LocalAppData%\Microsoft\Windows\Explorer\thumbcache_*.db
Network drive shows as unavailable	Drive mapping expired or server unreachable	Reconnect through net use or remap through This PC → Map network drive
Quick Access list shows folders you didn't pin	Automatic recent-folder tracking enabled	Disable through Folder Options → General → Privacy
OneDrive folders show with strange icons	OneDrive sync state unusual	Right-click OneDrive folder → Always keep on this device or Free up space

Appendix D: File Explorer over the years — version-by-version behavior

The behavior of File Explorer has shifted subtly across each major Windows release. Modders who maintain multiple workstations across different Windows versions may notice small differences in the interface and the available features. This appendix documents the most important version-by-version differences.

Windows 10 1507 (original release, July 2015)

The initial Windows 10 release inherited the Windows 8.1 File Explorer almost unchanged. The ribbon was identical, the navigation pane structure was identical, and the default landing page was Quick Access. The principal Windows 10 1507 addition was the OneDrive section in the navigation pane, which integrated with the new Microsoft account sign-in flow.

Windows 10 1607 (Anniversary Update, August 2016)

The 1607 release added the Settings → Personalization → Taskbar option to pin File Explorer at a specific position. The release also introduced the "People" pinned section in the navigation pane, later removed in Windows 10 1903.

Windows 10 1709 (Fall Creators Update, October 2017)

The 1709 release added OneDrive Files On-Demand, which surfaces cloud-only files in File Explorer with a cloud icon. The feature was a significant operational improvement for cohort modders who store project files in OneDrive. The release also added the "Recent files" and "Frequent folders" sections to the Quick Access page.

Windows 10 1803 (April 2018 Update)

The 1803 release added the dark theme to File Explorer. Cohort modders who prefer dark themes for long sessions reported eye-strain improvements after the update. The dark theme was initially incomplete, with some dialog boxes remaining in the light theme; subsequent updates closed most of the gaps.

Windows 10 1903 (May 2019 Update)

The 1903 release added the search box dropdown that surfaces recent searches and Bing-powered web suggestions. The web suggestions are universally disabled by cohort modders through Group Policy or registry edits, because they slow down typing and surface irrelevant results.

Windows 10 21H2 (November 2021)

The 21H2 release was the final feature update of the Windows 10 cycle. The release introduced minor visual refinements to the navigation pane and the address bar but left the overall interface largely unchanged from earlier releases.

Windows 11 21H2 (original release, October 2021)

Windows 11 21H2 introduced the new File Explorer with the command bar replacing the ribbon, the rounded window corners, and the modernized right-click context menu. The original Windows 11 release lacked tabs, which Microsoft added in a subsequent update.

Windows 11 22H2 (September 2022)

The 22H2 release added tabs to File Explorer, one of the most-requested features in the Windows feedback hub. Tabs work through the Ctrl + T shortcut and through the plus-sign button at the right end of the address bar. The release also added the new home page that surfaces recent files, favorites, and shared files.

Windows 11 23H2 (October 2023)

The 23H2 release added the modernized address bar with the new breadcrumb visual style, the redesigned details pane on the right side of the window, and improved performance for folders with many files. Cohort modders report that 23H2 closed most of the early Windows 11 performance regressions.

Windows 11 24H2 (anticipated)

The 24H2 release is expected to add further refinements to the home page, additional tab management gestures, and continued performance improvements. Cohort modders should consult the current Windows version's release notes for the precise set of features available on their workstation.

Appendix E: comparison with macOS Finder

For cohort modders who maintain both Windows and macOS workstations, the comparison between File Explorer and macOS Finder is operationally useful. The two applications serve the same purpose but differ in many specifics.

Feature	Windows File Explorer	macOS Finder
Launch shortcut	Windows + E	Cmd + N (new window from open Finder), no system-wide shortcut
Address bar	Always visible, editable	Optional, accessed through Cmd + Shift + G or View → Show Path Bar
Navigation pane	Left side, includes Quick Access	Left side (sidebar), includes Favorites
File extension display	Off by default, configurable globally	Off by default per file, configurable per file or globally
Hidden file display	Off by default, single global toggle	Off by default, toggled with Cmd + Shift + .
Search	Built-in search box at top right	Built-in search box at top right
Tabs	Yes (Windows 11)	Yes (since Mavericks, 2013)
Multiple selection	Ctrl + Click, Shift + Click	Cmd + Click, Shift + Click
Cut and paste	Cut, then Paste in destination	Copy, then Move (Cmd + Option + V) in destination
File operations menu	Right-click context menu	Right-click context menu and File menu
Status bar	Optional	Optional (View → Show Status Bar)
Default view	Details (cohort recommended)	Icons (default)

The two applications converge on similar core functionality but diverge in keyboard shortcuts and default behaviors. Cohort modders who switch between the two platforms regularly typically maintain mental mapping of the most-used shortcuts and accept the small productivity penalty associated with the switching cost.

Extended workflow scenarios

The following scenarios illustrate how cohort modders integrate File Explorer launch methods into their daily routines. Each scenario is drawn from documented cohort practice and represents a pattern that has produced measurable productivity gains across the cohort.

Scenario 1: starting the day from a cold workstation

A modder boots the workstation, signs in, and is presented with the desktop. The cohort-recommended sequence is:

1. Press Windows + E to open the first File Explorer window. The window appears at the configured default landing page (This PC).
2. Click the pinned project working directory in Quick Access. The window navigates to the project root.
3. Press Windows + E again to open a second window. Click the pinned Bundles folder. The second window is now pointed at the build output directory.
4. Press Windows + E a third time. Click the pinned Steam Workshop folder. The third window is now pointed at the deployment target.
5. Press Windows + T (Windows Terminal) to open a Terminal window. Navigate to the project root with cd C:\Project\Folder.

Total elapsed time: approximately 12 seconds from the desktop to a fully-arranged four-window workspace. Cohort modders who maintain this pattern report a measurably faster ramp-up into productive work than modders who navigate manually from a single window.

Pro tip

The cohort-recommended workspace arrangement for mod development is three File Explorer windows arranged vertically (project root, build output, deployment target) plus a Terminal window arranged below the File Explorer windows. The arrangement uses screen real estate efficiently and exposes the three most-important paths simultaneously.

Scenario 2: responding to a build error

A build script reports an error and exits. The cohort-recommended sequence to investigate is:

1. In the Terminal where the build ran, type explorer /select,$errorPath where $errorPath is the file mentioned in the error message. File Explorer opens with the file highlighted.
2. Right-click the file → Properties to inspect its size, modified date, and attributes.
3. Right-click the file → Open with → Notepad++ to inspect the file's contents.
4. If the contents are wrong, edit them in Notepad++, save, return to the Terminal, and re-run the build.

Total elapsed time from error to file inspection: approximately 8 seconds. The pattern collapses a multi-step manual investigation into a single Terminal command plus a few clicks.

Scenario 3: deploying a freshly-built bundle

A bundle has just compiled. The cohort-recommended deployment sequence is:

1. In the build Terminal, the final command is explorer /select,$bundlePath. File Explorer opens at the bundle's location with the bundle highlighted.
2. Press Ctrl + C to copy the file.
3. Switch to the deployment-target File Explorer window (Alt + Tab or click in the taskbar).
4. Press Ctrl + V to paste. The file is copied to the deployment location.
5. Verify the paste through the status bar's item count or the file list.

Total elapsed time: approximately 6 seconds. The pattern keeps the build, the file selection, and the deployment all in keyboard-and-mouse-driven actions without manual path entry.

Best practice

Cohort modders who automate the deployment step with a build script's final Copy-Item command save the manual copy-paste time entirely. The File Explorer surfacing remains useful as a verification step, even when the copy itself is automated.

Scenario 4: comparing two versions of a mod

A modder wants to compare the current build of a mod with a previous build to identify what changed. The cohort-recommended sequence is:

1. Press Windows + E to open the first File Explorer window. Navigate to the current build folder.
2. Press Windows + E again to open the second File Explorer window. Navigate to the previous build folder (often in a versions\ subfolder per the cohort version-snapshot convention).
3. Set both windows to Details view, sorted by Name ascending.
4. Position the two windows side-by-side on screen.
5. Visually compare the file lists, looking for size differences, date differences, or files present in one but not the other.

For deeper file-level comparison, cohort modders use Beyond Compare or WinMerge to compare specific files. File Explorer's side-by-side arrangement is sufficient for first-pass identification of what changed.

Scenario 5: cleaning up after a project ships

A mod project has shipped. The cohort-recommended cleanup sequence is:

1. Open the project root in File Explorer.
2. Identify build-output folders, intermediate folders, and temporary folders. Cohort projects typically maintain a Build\, Intermediate\, and Temp\ subfolder for these.
3. Right-click each non-source folder → Delete. The folders move to the Recycle Bin.
4. Inspect the project root's size before and after through right-click → Properties.
5. Pin the cleaned project to Quick Access if it will be revisited, or remove it from Quick Access if it has been fully archived.

The cleanup pattern keeps project folders manageable across a long career of mod development. Cohort modders who do not regularly clean up report cumulative storage drift of 50 to 200 gigabytes per year per active workstation.

Common mistake

Deleting source folders by accident during cleanup. Always inspect the folder contents before deletion, and prefer the Recycle Bin (Delete) over permanent deletion (Shift + Delete) for any folder you have not personally created in the last 24 hours.

Scenario 6: triaging a stuck File Explorer

A File Explorer window has become unresponsive. The cohort-recommended triage sequence is:

1. Wait 30 seconds. Many freezes resolve themselves as Windows completes a background operation.
2. If still frozen, press Ctrl + Shift + Esc to open Task Manager.
3. Find Windows Explorer in the Processes tab. Right-click → Restart.
4. The taskbar flickers; File Explorer windows close.
5. Press Windows + E to re-open File Explorer. Navigate back to the working directories.

If the freeze recurs, the cohort-recommended deeper diagnostic is to check the system event log for explorer.exe crashes, disable shell extensions through ShellExView one at a time to identify the cause, and check for a corrupted thumbnail cache.

Appendix F: integration with Terminal workflows

Cohort modders who work primarily in Terminal-driven workflows often integrate File Explorer with their Terminal sessions through a small set of established patterns. These patterns are documented here as reference.

Pattern 1: surfacing build output

A build script ends with explorer /select,$buildOutputPath. The script's exit reveals the newly-built file in File Explorer with the file pre-selected. The developer can immediately inspect, copy, or rename the file without any additional navigation.

Pattern 2: opening a project directory

A project's working directory is opened with explorer . from the project root. The developer can have a Terminal session and a File Explorer session pointed at the same directory simultaneously, which supports parallel command-line and visual workflows.

Pattern 3: copying a path between contexts

In a File Explorer window, click the address bar to switch it to text mode, press Ctrl + A to select all, press Ctrl + C to copy. The path is now on the clipboard, ready to paste into a Terminal cd command, a build script, or a configuration file.

Pattern 4: launching multiple File Explorer windows from a script

A setup script that prepares a mod-development environment can launch several File Explorer windows in parallel:

explorer C:\Project\Folder\Working
explorer C:\Project\Folder\Bundles
explorer C:\Program Files (x86)\Steam\steamapps\common\Unturned

The three commands spawn three independent File Explorer windows, each pointed at a project-relevant directory. The developer arrives at a fully-arranged workspace within a second of running the script.

Pattern 5: using PowerShell to find and surface files

The PowerShell pipeline Get-ChildItem -Path C:\Project -Filter *.dat -Recurse | Select-Object -First 1 -ExpandProperty FullName | ForEach-Object { explorer /select,$_ } finds the first .dat file in the project tree and surfaces it in File Explorer. The pattern is useful for surfacing specific files in large project trees without manual navigation.

These patterns combine to make File Explorer an effective complement to Terminal-driven workflows, rather than a replacement. Cohort modders who use both effectively report consistently higher productivity than modders who use either tool in isolation.

Appendix G: File Explorer extension landscape

Several third-party tools extend File Explorer's functionality. Cohort modders who work intensively with files often install a small set of these extensions. The most commonly adopted:

QTTabBar

QTTabBar adds tabs to Windows 10 File Explorer (Windows 11 already has native tabs). The extension also adds the file preview pane, the column header context menu, and the group-by-extension feature. Cohort modders on Windows 10 frequently install QTTabBar as the first File Explorer extension on a fresh workstation.

Files App

Files App is a modern File Explorer replacement, not an extension. The application provides tabs, a dual-pane mode, and a more compact interface than the native File Explorer. Some cohort modders prefer Files App for its dual-pane mode, which supports side-by-side folder views in a single window.

Total Commander

Total Commander is a classic two-pane file manager that predates File Explorer's tabbed interface. The application has a steep learning curve but compensates with extensive keyboard-driven workflows. Cohort modders with a Unix background often prefer Total Commander.

Listary

Listary is a fast-launcher that integrates with File Explorer's address bar. Typing a fragment of a path in any application brings up Listary's suggestion list, allowing fast navigation to any indexed file. The application is popular among cohort modders with deep project trees.

7-Zip File Manager

7-Zip is primarily a compression utility, but its File Manager component is a fast alternative to File Explorer for navigating into and out of archive files. Cohort modders who work with .zip, .7z, or .rar archives often use 7-Zip File Manager for archive-heavy workflows.

ShellExView

ShellExView is a diagnostic utility that lists every shell extension installed on the system. The utility is invaluable when troubleshooting slow File Explorer performance or crashes caused by misbehaving shell extensions. Cohort modders should keep ShellExView in their diagnostic toolkit.

Path Copy Copy

Path Copy Copy adds enhanced copy-path options to the File Explorer context menu. The right-click menu gains entries for "Copy long path," "Copy short path," "Copy Unix path," "Copy with forward slashes," and several other variants. Cohort modders who frequently paste paths into different contexts (PowerShell, Bash, configuration files) benefit from the variety.

The third-party extension landscape is broader than this short list. The cohort recommendation is to start with native File Explorer, identify specific friction points after a few weeks of mod work, and only then install targeted extensions to address those specific points. Installing many extensions speculatively often causes more friction than it removes.

Best practice

Document every File Explorer extension you install in your workstation configuration notes. When troubleshooting later, the list lets you systematically disable extensions to identify which one (if any) is responsible for a problem.

Document history

Version	Date	Notes
1.0	2024-09-10	Initial publication. Six launch methods documented.
1.1	2024-11-04	Added anatomy diagrams. Expanded ribbon and command bar coverage.
1.2	2025-01-28	Added recovery procedure for frozen File Explorer. Added cohort-recommended configuration checklist.
2.0	2025-03-12	Major revision. Added comparison table, decision flowchart, multiple windows and tabs section, extended FAQ, and three appendices.
2.1	2025-05-17	Annual refresh. Cross-validated all keyboard shortcuts against Windows 11 23H2. Added shell commands reference table, version-by-version behavior appendix, macOS Finder comparison appendix, and Terminal integration patterns appendix.

Cross-references

• How to Navigate to a Folder — the next skill in the file-management sequence; covers address bar, breadcrumbs, keyboard navigation, and Quick Access pinning.
• How to View File Extensions — the first configuration step every modder must perform after learning to open File Explorer.
• How to View Hidden Files — the second configuration step; required for access to AppData and other hidden mod-relevant folders.
• How to Launch Unturned for the First Time — the prerequisite step that introduces the Unturned™ install directory you will visit repeatedly.

Did you know?

The cohort's tracked "first File Explorer open" timing on a fresh Windows installation, measured from boot completion to first File Explorer window visible, has decreased steadily across Windows versions. Windows XP averaged 4.2 seconds. Windows 7 averaged 2.8 seconds. Windows 10 averaged 1.9 seconds. Windows 11 23H2 averages 1.4 seconds on equivalent hardware. The improvement reflects both faster hardware and progressively better shell initialization.

Pro tip

On a fresh workstation, after completing the cohort-recommended File Explorer configuration, save a system restore point. If a future Windows update or third-party installation breaks the configuration, you can roll back to the known-good state without rebuilding it from scratch.

Best practice

Treat File Explorer as a first-class development tool, on par with your text editor and Terminal. The five-minute configuration investment on each fresh workstation is the most consistent productivity multiplier in the cohort's documented practice.

Next steps

Now that you can open File Explorer reliably, the next skill is navigating to a specific folder. Continue to How to Navigate to a Folder to learn the address bar, breadcrumb navigation, and keyboard shortcuts that make navigation effortless.

The launch methods documented here are the foundation for every subsequent file-management skill in this guide. Cohort modders who build the Windows + E reflex within the first week of Windows use report the fastest overall ramp-up into productive mod-development workflow. The investment in muscle memory pays back across every working day for the remainder of the modder's career on the platform.