Portable productivity launcher & Windows control center
Bahasa Indonesia · User Guide · Changelog · Security
Windows Shortcut Control is a portable Windows launcher and control center built as a single .cmd file with embedded PowerShell/WPF code.
It provides one interface for personal shortcuts, common Windows administrative tools, live system information, backup/recovery, startup behavior, System Tray integration, global search, and keyboard-driven navigation.
No installer or external runtime package is required on a normal Windows 10/11 desktop installation. Windows 7 is also supported when the required PowerShell and .NET components are available.
| Platform | Status | Notes |
|---|---|---|
| Windows 11 | ✅ Supported | Primary modern Windows target |
| Windows 10 | ✅ Supported | Supported |
| Windows 7 SP1 | ✅ Tested | Requires Windows PowerShell 5.1 and compatible .NET/WPF components |
| Windows Server | Some desktop/WPF features may depend on installed GUI components |
Windows 7 does not ship with Windows PowerShell 5.1 by default. If required, install Windows Management Framework 5.1 before running the application.
There are three easy ways to get Windows Shortcut Control on your PC.
This is the simplest method and does not require Git.
- Open the latest release.
- Under Assets, download:
Windows_Shortcut_Control.cmd
- Save the file to a permanent folder, for example:
C:\Tools\Windows-Shortcut-Control\
- Double-click
Windows_Shortcut_Control.cmd.
If Windows blocks the downloaded file, right-click it → Properties → enable Unblock if that option is shown → Apply.
You can also unblock it from PowerShell:
Unblock-File -Path "C:\Tools\Windows-Shortcut-Control\Windows_Shortcut_Control.cmd"No Git installation is required.
- Open the repository:
https://github.com/baska-pro/windows-shortcut-control - Click Code.
- Choose Download ZIP.
- Extract the ZIP.
- Open the extracted folder.
- Run:
Windows_Shortcut_Control.cmd
This method also downloads the documentation, screenshots, changelog, and other repository files.
Use this method if you want to keep a local copy that can easily be updated later.
Open Command Prompt, PowerShell, or Windows Terminal and run:
git clone https://github.com/baska-pro/windows-shortcut-control.git
cd windows-shortcut-controlThen run:
Windows_Shortcut_Control.cmdOr from PowerShell:
.\Windows_Shortcut_Control.cmdTo update an existing clone later:
git pullIf Git is not installed, use the Release or Download ZIP method instead.
Windows Shortcut Control is a portable application, so there is no traditional installer.
Recommended setup:
- Put
Windows_Shortcut_Control.cmdin a permanent folder. - Run the file.
- Complete or skip the built-in first-run guide.
- Add or import your shortcuts.
- Open Settings if you want to:
- run the app automatically at Windows sign-in;
- start directly in the System Tray;
- configure the Close button behavior;
- enable the global hotkey;
- choose Indonesian or English;
- create a backup.
Example recommended location:
C:\Tools\Windows-Shortcut-Control\
Right-click Windows_Shortcut_Control.cmd → Send to → Desktop (create shortcut).
Startup can be enabled directly from the application's Settings page.
If startup is enabled, keep the .cmd file in the same location. Moving or renaming the file afterward can break the saved startup path.
- Modern WPF desktop interface
- Portable single-file distribution
- Dashboard with pinned, favorite, and recently used shortcuts
- Shortcut types:
- Folder
- File
- Application
- URL
- PowerShell command
- Drag & drop files/folders to create shortcuts
- Grid, list, and compact shortcut views
- Search and filtering
- Global Search
- Command Palette
- Built-in Windows Tools
- Live System Info and resource monitoring
- System Tray support
- Run at Windows sign-in
- Configurable Close button behavior
- Global hotkey
- JSON import/export
- Full configuration backup/restore
- Last Known Good recovery
- Self Diagnostics
- Single-instance activation
- Indonesian and English UI
Dashboard — pinned shortcuts, favorites, recent items, and quick access.
|
Shortcut Manager |
Windows Tools |
|
Settings |
Built-in Guide |
More visual assets are available in assets/screenshots/.
Windows Shortcut Control includes quick access to commonly used Windows tools such as:
| Category | Tools |
|---|---|
| File & Folder | File Explorer, Downloads, Desktop, Documents, Recycle Bin |
| System | Task Manager, Control Panel, Windows Settings, System Information, Resource Monitor |
| Management | Services, Task Scheduler, Device Manager, Disk Management, Event Viewer, Registry Editor |
| Network | Network Connections |
| Terminal | PowerShell, Command Prompt |
| Data & Recovery | Import/export, full backup/restore, Last Known Good, reset, diagnostics, Registry data |
Availability of individual Windows Tools depends on the Windows version. Some tools or Settings pages available on Windows 10/11 may not exist on Windows 7.
- Windows 10 or Windows 11 desktop
- Windows PowerShell 5.1 or newer
- WPF/.NET components included with normal Windows desktop installations
- Windows 7 SP1
- Windows PowerShell 5.1
- Windows Management Framework 5.1 when PowerShell 5.1 is not already installed
- Compatible .NET Framework/WPF components
Administrator privileges are not required for normal use. Some Windows administrative actions or user-created shortcuts may require elevation.
The
.cmdlauncher startspowershell.exewithExecutionPolicy Bypassfor the embedded application code. Review the source before running software downloaded from the Internet.
Application settings and shortcut data are stored per-user in the Windows Registry:
HKEY_CURRENT_USER\Software\LaviControlCenter
The application can also export:
Shortcut backup → *.json
Full configuration → *.wsc.json
The source does not include telemetry or automatic outbound API requests. URLs and commands are executed only when launched by the user or by a configured shortcut.
See Privacy for details.
| Shortcut | Action |
|---|---|
Ctrl + K |
Open Command Palette |
Ctrl + N |
Add shortcut |
Ctrl + F |
Focus Global Search |
Ctrl + Shift + F |
Open Shortcuts and focus shortcut search |
Ctrl + E |
Export shortcuts |
Ctrl + I |
Import shortcuts |
Ctrl + B |
Full configuration backup |
Ctrl + Shift + B |
Restore full configuration |
Ctrl + Shift + D |
Self Diagnostics |
Ctrl + Shift + A |
About |
Ctrl + Shift + T |
Minimize to System Tray |
Ctrl + , |
Settings |
Alt + 1 |
Dashboard |
Alt + 2 |
Shortcuts |
Alt + 3 |
Windows Tools |
Alt + 4 |
System Info |
Alt + 5 |
Settings |
F1 |
User Guide |
F5 |
Refresh |
Ctrl + Alt + Space |
Global hotkey, when enabled |
The project intentionally remains a single-file portable application:
Windows_Shortcut_Control.cmd
│
├── CMD bootstrap
│ └── launches Windows PowerShell hidden
│
└── Embedded PowerShell
├── WPF user interface
├── Registry-backed storage
├── shortcut engine
├── Windows Tools
├── System Tray / global hotkey
├── background system monitoring
├── backup / restore
└── diagnostics
More details: Architecture
This application can:
- launch applications and files;
- open URLs;
- execute user-defined PowerShell commands;
- start selected items with administrator privileges;
- open Windows administration tools;
- write per-user settings to the Registry;
- register itself in the current user's Windows startup settings when requested.
Only import configuration files from sources you trust.
See SECURITY.md.
Current public version:
3.2.1
The project is actively maintained and has been tested on Windows 7 SP1 as well as modern Windows versions.
Use GitHub Issues for:
- reproducible bugs;
- compatibility problems;
- feature requests;
- UI/UX suggestions.
For Windows 7 compatibility reports, include:
- Windows 7 edition and architecture;
- confirmation that SP1 is installed;
- PowerShell version (
$PSVersionTable.PSVersion); - any relevant Self Diagnostics output.
Please do not post passwords, tokens, private paths, personal backup files, or other sensitive information in a public issue.
Copyright © 2026 Lathif Baska.
This repository currently uses an All Rights Reserved license to match the copyright notice inside the application.
See LICENSE.
If the project is later intended to become permissive open source, the license and the copyright notice inside the application should be changed together.
Lathif Baska
- GitHub: @baska-pro
- Location: Indonesia
