Make Windows work the way you do

ExplorerPatcher is a free, open-source Windows customization utility that changes how selected parts of the Windows shell behave. It can restore familiar taskbar, Start menu, File Explorer, system tray, Alt+Tab, and other interface options that Microsoft removed, replaced, or restricted. It is designed for people who want to keep modern Windows while regaining control over everyday desktop workflows.

ExplorerPatcher can adjust a wide range of Windows shell components, including taskbar appearance and behavior, taskbar labels and button grouping, the Start menu style and position, File Explorer context menus and command interfaces, Alt+Tab window switching, system tray icons and flyouts, multi-monitor taskbar behavior, and selected Control Panel and Settings redirects. Available options depend on the installed Windows version, build, and ExplorerPatcher release.

No. ExplorerPatcher is an independent open-source project and is not developed, maintained, endorsed, or distributed by Microsoft. It modifies parts of the Windows shell, but it is not an official Windows component. Microsoft can change internal Windows behavior through updates, which may affect ExplorerPatcher compatibility.

ExplorerPatcher was created by Valentin-Gabriel Radu, also known as valinet. It began as a focused way to restore useful Windows interface behavior that was removed or changed in newer releases, then expanded into a broader shell-customization utility covering the taskbar, Start menu, File Explorer, Alt+Tab, the system tray, and other desktop components. Development, source code, issue tracking, and release notes are publicly available on GitHub.

ExplorerPatcher is an independent open-source software project, not a large commercial company or a general-purpose download platform. The project is centered on one application: ExplorerPatcher. Its purpose is to give Windows users more control over the interface while keeping development transparent and publicly reviewable.

Yes. ExplorerPatcher is free to download and use. The project is released under the GPL-2.0 open-source license, so its source code can be inspected, modified, and redistributed under the terms of that license. There is no paid edition, subscription, premium feature tier, or required account.

ExplorerPatcher is open source, and its code, releases, development history, and issue reports are publicly available. Official installers are published through the valinet/ExplorerPatcher GitHub repository. However, ExplorerPatcher modifies Windows shell behavior at a system level, so it has more access than a simple visual theme. For the lowest risk, download only original release files, review the release notes first, use the stable release on everyday computers, avoid unofficial repackaged installers, and keep a recovery option available on critical systems.

ExplorerPatcher should be downloaded from the original release assets published through the official valinet/ExplorerPatcher GitHub Releases page. The download buttons on this site link directly to those original files. Avoid third-party installers that repackage the application, add download managers, bundle other software, or modify the executable.

Most Windows computers with Intel or AMD processors should use ep_setup.exe. Windows devices with an ARM64 processor should use ep_setup_arm64.exe. ARM64 devices include newer PCs powered by supported Snapdragon processors. You can check the system architecture under Settings, System, About, System type.

ExplorerPatcher is primarily used to customize Windows 11 and selected Windows 10 configurations. Exact compatibility depends on the Windows edition, build number, installed updates, processor architecture, and ExplorerPatcher version. Some features rely on Windows components that may change or be removed in later builds, so the release notes for the current version should always be checked before installation, especially after a major Windows feature update or on a Windows Insider build.

ExplorerPatcher can restore or reproduce many Windows 10-style taskbar behaviors on supported Windows 11 builds, such as taskbar button labels, never-combine behavior, smaller taskbar icons, alternative positioning, a different Start button style, improved secondary-monitor behavior, and familiar context-menu commands. Microsoft periodically removes or changes legacy components, so the exact taskbar implementations available can vary between Windows builds.

No. ExplorerPatcher does not install a separate desktop environment or replace Windows with another shell. It works with the existing Windows Explorer process and modifies selected interface components and behaviors, so you keep the underlying Windows desktop while changing the parts that are inefficient or unfamiliar. It is also not a theme pack, wallpaper collection, icon pack, or visual skin.

ExplorerPatcher is an open-source desktop utility and does not require an account, profile, cloud workspace, or subscription. Its source code is publicly available for inspection. Update checks may require an internet connection to retrieve current release information from GitHub, but the core customization features operate locally on the Windows computer.

Stable releases are recommended for most users and normal daily use, and have progressed beyond the earliest testing stage. Pre-release versions provide earlier access to new features, compatibility changes, and fixes for recent Windows updates, but they may also contain incomplete behavior or regressions. Pre-release builds are more appropriate for advanced users who can diagnose shell problems, restore a previous version, and submit useful bug reports.

Yes. ExplorerPatcher depends on Windows shell components that Microsoft can modify through cumulative updates, security updates, and major feature releases. After a Windows update, some features may stop working, behave differently, or require a newer ExplorerPatcher release. This does not necessarily indicate permanent damage; compatibility is often restored through an ExplorerPatcher update. Before a major Windows update, check recent release notes, update ExplorerPatcher when a compatible release is available, and keep uninstall and recovery options available.

ExplorerPatcher includes update controls in its Properties interface. Depending on the configuration, it can check for a newer version, notify you when an update is available, download and install an update, restart File Explorer after updating, enable or disable update checks, and opt in to pre-release versions. Updates are distributed through the project GitHub release infrastructure, and keeping ExplorerPatcher current is particularly important after Windows updates.

ExplorerPatcher can be removed through ExplorerPatcher Properties, Installed apps in Windows Settings, Programs and Features in Control Panel, the installer uninstall command, or an installer file renamed to ep_uninstall.exe. File Explorer may restart during removal. After uninstallation, Windows returns to its standard shell, although some settings controlled directly by Windows may need to be adjusted separately.

First, avoid installing additional shell-modification tools, since multiple utilities changing the same components make diagnosis harder. Then restart File Explorer or the computer, install the latest compatible ExplorerPatcher release, review the release notes for your Windows build, disable other taskbar and shell customization tools, reset ExplorerPatcher settings if the Properties interface is accessible, and uninstall ExplorerPatcher if Windows Explorer remains unstable. A useful bug report should include the Windows version and build number, ExplorerPatcher version, processor architecture, relevant settings, and exact steps to reproduce the problem.