SmartSystemMenu: Adding Hide, Transparency and Always On Top to Every Windows Title Bar Menu

What SmartSystemMenu Actually Fixes in the Windows Window Model

Windows gives every top-level window a system menu, the one that appears when you click the window icon or press Alt+Space. In practice that menu offers Move, Size, Minimize, Maximize and Close, and little else. There is no built-in way to make a window translucent, keep it above others, roll it up to its title bar, or push it to the back. Those gaps are usually filled by separate utilities: one for always-on-top, another for transparency, another for screenshots. SmartSystemMenu's answer is to append its own items to that same menu, so the commands live where the window controls already are. The target user is a Windows power user or developer who keeps many windows open, works with console windows, and wants per-window control without switching tools. The README lists the appended items: Information, Hide, Roll Up, Aero Glass, Always On Top, Change Icon, Change Title, Send To Bottom, Save Screenshot, Open File In Explorer, Drag By Mouse, Click Through, Hide For Alt+Tab, Resize, Move To, Alignment, Transparency, Priority, Clipboard, Dimmer, Buttons, System Tray, Other Windows and Start Program.

How the Hook Architecture Works and Why It Needs Administrator Rights

The mechanism is process injection, not a shell extension. The repository contains two native hook modules, SmartSystemMenuHook.dll for 32-bit processes and SmartSystemMenuHook64.dll for 64-bit processes, plus two executables, SmartSystemMenu.exe and SmartSystemMenu64.exe. According to the README, running SmartSystemMenu.exe also starts SmartSystemMenu64.exe, and the two executables load the hooks into all processes. When the user picks an item from an extended system menu, the hook sends a message back to the executable module, which then performs the action: changing window transparency, resizing the window, and so on. That design explains the UAC prompt. The README states plainly that the program needs elevated privileges, so on a system with UAC enabled you will see a consent dialog at launch. It also explains why the tool can act on windows owned by other users or by services, which a user-level utility could not. The cost is that a fault in the hook affects every process it is loaded into, and the hook DLLs are the files most likely to attract antivirus attention.

Installing SmartSystemMenu and Testing It on a Notepad Window

The README offers four installation paths: a zip from the GitHub releases page, Chocolatey, Scoop and WinGet. Package managers are the least manual option and the easiest to update later.

choco install smartsystemmenu

For Scoop, the README says to add the extras bucket first and then install the package by name.

scoop bucket add extras
scoop install extras/smartsystemmenu

WinGet installs by the exact package identifier given in the README.

winget install --id=AlexanderPro.SmartSystemMenu -e

After installation, run SmartSystemMenu.exe. Expect a UAC dialog: the README says the program requires elevated privileges and that this prompt is normal. Once it is running, open any window and press Alt+Space or click the window icon. The custom items should appear at the bottom of the system menu. A first useful test is the command line interface, which lets you drive a window without touching the menu. The README gives this example, which targets a Notepad window by title, aligns it to the top left, raises its priority and pins it on top, with no GUI shown.

SmartSystemMenu.exe --title "Untitled - Notepad" -a topleft -p high --alwaysontop on --nogui

If nothing happens, the most likely cause is a title mismatch: --title matches the window caption exactly, and the README also provides --titleBegins, --titleEnds and --titleContains for looser matching, plus --handle and --processId for targeting by identity instead of text.

Where SmartSystemMenu Breaks Down

The most concrete limitation is stated in the requirements: OS Windows XP SP3 and later, with .NET Framework 4.0. That is a Windows-only tool, and it is built on a framework that modern .NET applications do not use. The README does not document rollback for any action. If you hide a window or set it click-through and then lose access to it, there is no documented undo command in the README; the recovery path is not described. Click Through in particular makes a window ignore mouse input, and the README does not say how to reverse it from the command line. Hide For Alt+Tab removes a window from the taskbar and Alt+Tab list, which is easy to do and harder to reason about when you forget which window you removed. The hook model is also a failure surface: because the DLLs load into all processes, an application that is sensitive to injected code, or an antivirus product that flags injection, can turn a convenience tool into a support ticket. Finally, the README does not describe behaviour on windows that do not expose a standard system menu, such as some UWP or custom-chrome applications, so treat coverage as uneven rather than universal.

SmartSystemMenu Compared with Microsoft PowerToys and Other Window Tools

Microsoft PowerToys is the obvious alternative, and the topics list on the repository includes powertoys, so the comparison is one the project itself invites. The difference is architectural. PowerToys ships as a set of separate modules with their own settings UI, and its window-management features are configured centrally rather than exposed through each window's system menu. SmartSystemMenu takes the opposite approach: no settings application, no per-feature module, just extra entries in the menu you already use. That makes it faster to reach for a one-off action and worse for discoverability, because nothing tells you the commands exist until you open a system menu. It also means SmartSystemMenu's behaviour is attached to the window rather than to a global configuration, which suits ad hoc work and frustrates anyone who wants a repeatable, documented setup. If you want a curated, Microsoft-maintained suite with a settings surface, PowerToys is the safer default. If you want the action inside the title bar menu and you are willing to accept global hooks, SmartSystemMenu is the more direct tool.

Maintenance, Licence and Upgrade Cost

The repository is not archived, and the last push was on 2026-09-22, two days before this writing, so the project is currently being worked on. The release cadence visible in the release list is uneven: v2.33.1 on 2026-03-20, v2.33.0 on 2026-02-22, and v2.32.1 on 2025-09-20, with a gap of roughly six months between the September 2025 and February 2026 releases. Upgrades through Chocolatey, Scoop or WinGet are the low-friction path, but note that the running process holds the hook DLLs, so an upgrade while SmartSystemMenu.exe is active may require stopping it first; the README does not document the upgrade procedure. The licence is MIT, which permits commercial and private use, modification and redistribution provided the copyright notice and permission notice are included. That is a permissive licence, but it does not remove the operational question of running injected code with elevated privileges, and it offers no warranty. If your organisation has rules about administrator rights or DLL injection, the licence is not the constraint; the deployment model is.

Editorial conclusion

Adopt SmartSystemMenu if you routinely fight with windows that will not stay on top, cannot be resized, or need to be dimmed or hidden for a demo, and you are comfortable running a tool that loads a DLL into every process with elevated rights. Do not adopt it on a locked-down or compliance-sensitive machine where injecting hooks into all processes is not acceptable, and do not expect it to work on Windows 11-style menus or on apps that do not expose a standard system menu. Before rolling it out, run the portable zip on a single machine, check SmartSystemMenu.xml and Language.xml in the extracted folder, and confirm that your antivirus does not quarantine the hook DLLs.

Frequently asked questions

Official sources

1. AlexanderPro/SmartSystemMenu on GitHub
2. Issues
3. License: MIT
4. README
5. Releases