RetroBar: a classic Windows taskbar replacement for Windows 7 through 11

What RetroBar replaces, and who it is for

RetroBar replaces the default Windows taskbar with a classic layout, according to the README. The stated goal is cosmetic and behavioural: the project says it teleports you back in time by replacing your modern Windows taskbar with the classic Windows 95, 98, Me, 2000, XP, or Vista style. That framing matters, because it tells you what the program is not. It is not a full desktop shell, and it does not replace Explorer.

The audience is narrow but well defined. Someone running Windows 10 or 11 who wants a two-row taskbar, a quick launch toolbar, an XP-style collapsible notification area, or a start button that opens the modern start menu. The README lists all of these as features. The classic look is the draw, but the functional list is what keeps people using it: native notification area with balloon notification support, native task list with UWP app support and drag reordering, input language and keyboard layout switcher, and the ability to display the taskbar on any side of the screen, including on Windows 11.

Supported systems are Windows 7 SP1, Windows 8.1, Windows 10, and Windows 11. The README notes that fresh installs of Windows 7 may require additional Windows updates, and points to issue 1319 for details. That is a real caveat rather than a footnote: on a bare Windows 7 machine you may be installing updates before RetroBar will run.

ManagedShell is the reason the task list behaves natively

RetroBar is based on the ManagedShell library, which the README credits for great compatibility and performance. The repository layout supports that description: the solution file RetroBar.sln sits at the top level next to a RetroBar/ project directory, along with Directory.Build.props, an installer.iss Inno Setup script, shader_compile.bat, and shader_invert.hlsl.

The practical consequence of building on ManagedShell is that the task list and notification area are not a mock-up. The README describes a native task list with UWP app support and drag reordering, and a native notification area with balloon notification support. A taskbar that merely drew icons would break on modern packaged apps and on notification balloons. The architecture here keeps those pieces working while the visual layer changes.

The two shader files at the repository root hint at how the visual layer is produced. A compiled HLSL shader and a batch file to build it suggest that some effects, likely the Vista-style window thumbnails the README mentions, are rendered through a shader rather than assembled from static images. The README does not document this pipeline, so treat it as an inference from the file names rather than a stated design.

Themes are XAML ResourceDictionary files. The README says to view the included example themes in RetroBar/Themes when creating a new one, and that community theme files can be installed through RetroBar Properties > Advanced. Custom themes and custom languages are both supported, and both can be placed manually under %localappdata%\RetroBar in a Themes or Languages directory.

Installing RetroBar and getting to the settings

The README does not print an install command, because RetroBar ships as a Windows application rather than a package. What it does state is the requirement: the Microsoft .NET Desktop Runtime. With the RetroBar installer, the README says this runtime is automatically downloaded and installed if necessary. With the portable version, you are prompted to download it on first launch. That difference is the main decision before you start.

Grab the release from the project's releases page and run the installer, or take the portable build and expect the runtime prompt on first launch. The README gives no command-line step for either path.

After it runs, the taskbar is replaced with the classic layout. To change the theme or the taskbar behaviour, open RetroBar Properties. The README places third-party theme installation under RetroBar Properties > Advanced.

RetroBar Properties > Advanced

%localappdata%\RetroBar
Themes
Languages

Manual installation means creating the Themes or Languages directory under %localappdata%\RetroBar and placing valid .xaml files there. The README specifies .xaml for both. If you use Open-Shell Menu, the README recommends two settings for compatibility: Controls > Windows Key opens > Open-Shell Menu, and Menu Look > Align start menu to working area. Those are the only two adjustments it names.

Where RetroBar stops being the right tool

The README is honest about one dependency and silent about several others. The honest part is Windows 7: fresh installs may need additional Windows updates before RetroBar works. The silent parts are the ones worth thinking about before you commit.

RetroBar replaces the taskbar, which means it is a shell component running alongside Windows Explorer. The README does not describe a rollback procedure, an uninstall section, or what happens if the application crashes while the taskbar is replaced. There is no documented safe mode, no documented recovery path, and no statement about what the desktop looks like if RetroBar fails to start. That is not an accusation, it is an absence: the README does not document rollback.

There is also no documented policy on Windows feature updates. The project supports Windows 7 SP1 through Windows 11, a span of four major Windows versions, and the README does not say how quickly a new Windows build is tested or what breaks when Microsoft changes shell behaviour. If you run an Insider build, you are outside anything the README addresses.

Finally, the README does not discuss multi-user machines, group policy, or managed environments. Installing a shell replacement on a corporate laptop is a different proposition from installing it on a personal desktop, and the README offers no guidance either way. That silence is itself the answer for managed devices.

The alternative that is not a taskbar replacement

The obvious comparison is Open-Shell, which the README itself addresses in a dedicated section for Open-Shell Menu users. The difference in approach is scope. Open-Shell replaces the start menu and leaves the taskbar alone, which is why the README's advice is about coexistence settings rather than conflict. RetroBar replaces the taskbar and leaves the start menu alone: the README states that the start button opens the modern start menu.

That means the two are complementary rather than competing, and the README treats them that way. If your complaint is the start menu, Open-Shell is the smaller intervention. If your complaint is the taskbar layout, the notification area, or the absence of a quick launch toolbar, RetroBar is the piece that addresses it. Running both is a documented configuration, with the two settings the README recommends.

The other alternative is doing nothing. Windows 11 removed the ability to move the taskbar to the top or sides, and RetroBar restores it, along with multiple rows and a resizable taskbar. If none of those specific behaviours matter to you and you only want a different colour scheme, a theme for the existing taskbar is a smaller change than a shell replacement.

Themes, languages, and what the licence covers

RetroBar is Apache-2.0. The repository carries a LICENSE file and a DistLicense.txt, which is the file distributed alongside binaries. Apache-2.0 permits commercial use and modification, and it includes a patent grant. It does not, on its own, settle the question of redistributing a modified build that includes community theme files downloaded from elsewhere. Those themes come from third parties, the README points to DeviantArt and a Discord theme-repository channel, and their licences are not stated in the README. If you plan to redistribute a themed build, that is the gap to close first.

The bundled themes are numerous. The README lists System (Classic, XP, and Vista), Watercolor, Windows 95-98, Windows Me, Windows 2000, a long Windows XP set including Classic, Blue, Olive Green, Silver, Royale, Royale Noir, Embedded Style and Zune Style, plus Windows Longhorn Aero and Vista Aero, Basic and Classic. Custom themes use the XAML ResourceDictionary format, and the README directs you to the included example themes in RetroBar/Themes as a starting point.

Language support is broad, with the README listing around forty locales from Arabic through Welsh. Custom languages follow the same pattern as themes: valid .xaml files in a Languages directory under %localappdata%\RetroBar.

Upgrade cost is low by design. Releases are versioned and the last push was on 2026-08-02, with v1.22.122 in August 2026, v1.21.32 in October 2025, and v1.20.37 in May 2025. The gaps between those releases are months, not weeks. A user who installs the portable build and keeps custom themes in %localappdata%\RetroBar does not lose them on upgrade, because the README places them outside the application directory.

Editorial conclusion

RetroBar suits people who want the classic taskbar layout and accept that a third-party shell component runs alongside Explorer. It is the wrong choice for anyone who needs Microsoft-supported shell behaviour, or who runs a locked-down machine where installing a .NET desktop runtime and a shell replacement is not permitted. Before adopting it, check the requirements section for your Windows version, confirm whether you need the installer or the portable build, and read the Open-Shell Menu compatibility notes if you use that start menu.

Frequently asked questions

Official sources

1. Official README
2. Project repository
3. Release notes