Glossary
Terms explained
Plain-language definitions for readers, students, and search. Entries are written for Windows maintenance context around third-party uninstall tools such as HiBit Uninstaller. This site is an independent guide, not the official vendor site. Trademarks belong to their owners.
Tip: open the topics index for a full map of guide sections and articles, or start from the home overview.
Forced uninstall
A forced uninstall is a removal workflow utilities offer when the product’s own uninstall entry fails: the button does nothing, the vendor MSI or setup cache is missing, or the process crashes before completion. The tool attempts to remove files, shortcuts, and registration data tied to that listing.
It is powerful because it can touch many locations quickly; it is risky for the same reason. You should still verify which program row you selected, read confirmation dialogs, and avoid treating forced uninstall as a generic “make PC faster” action.
It is not a full malware remediation workflow. If the software is malicious or persistence is unknown, use isolation, reputable scanners, and documented incident steps first. Deep dive: force uninstall article · boundaries: when to avoid it.
Leftover scan
After a standard uninstall, some paths and keys may remain. A leftover scan (wording varies by product) searches disk and sometimes the registry for names, folders, or patterns associated with the removed application.
The scan produces candidates, not guaranteed junk. Shared DLLs, redistributables, and components used by other programs can appear in the list. Good practice is to review in batches, prefer vendor-scoped paths, and stop when uncertainty is high.
Pair automation with manual checks for startup entries and scheduled tasks. Read leftover scan best practices and the playbooks on the home page.
Uninstall leftovers
Leftovers are artifacts that outlive the main uninstall step: configuration under AppData, cache folders, browser helper files, services, scheduled tasks, firewall rules, or stray registry values.
They are not automatically “safe to delete.” Some entries are shared infrastructure; others are harmless orphans. The goal of cleanup is to remove what clearly belonged to the product version you uninstalled, without breaking unrelated software.
See remove uninstall leftovers for a fuller walkthrough and mental model.
Portable vs installed edition
A portable build is typically distributed as a folder you copy anywhere: USB stick, network share, or desktop folder. It avoids a classic installer that registers the product in Programs and Features the same way a full setup might.
An installed build follows the familiar pattern: setup executable, Start menu integration, and a predictable location administrators and backups expect.
Neither choice changes the need for elevation (UAC) when changing protected areas. Compare trade-offs in portable vs installed and edition notes in the download section.
Windows Registry (careful use)
The Registry stores configuration and registration data for Windows and applications. Uninstallers and cleanup tools may propose deleting keys they believe are orphaned.
Mass deletion or “registry optimizer” behavior is a common source of breakage: applications fail to start, file associations break, or worse. Prefer narrow changes tied to a program you have just removed and whose paths you can explain.
When unsure, skip the key, capture a restore point before deeper experiments, and read the FAQ on safety.
Restore point
A restore point (where System Restore is available and enabled) captures a rollback-friendly snapshot of certain system files and settings before a big change.
It helps when aggressive uninstall or cleanup goes wrong, but it is not a complete backup of your documents, projects, or media. Keep separate backups for data you cannot lose.
Create one before forced uninstall or large leftover batches. More context appears in the home guide playbooks.
Microsoft Store app vs desktop (Win32) app
Store apps (broadly: packaged apps acquired or updated through Microsoft Store mechanisms) are serviced with different APIs and storage layouts than classic Win32 programs installed from .exe / MSI installers.
Removal should usually start with Settings → Apps or Store workflows so dependencies, licenses, and package state stay coherent. Third-party uninstallers may list both families; understand which action each row triggers before you confirm.
Read Store vs desktop uninstall for a longer explanation.
User Account Control (UAC)
UAC prompts appear when a process needs administrative rights to modify protected locations: Program Files, certain registry hives, some services, and global tasks. Uninstall tools often need elevation to finish removal completely.
A portable executable does not magically avoid UAC; it only changes how the program is distributed. If you refuse elevation, uninstalls may look “successful” while files remain locked or half-removed.
On domain-joined or locked-down PCs, policy may block elevation or unknown binaries; follow IT guidance instead of bypassing controls.
Startup entries & scheduled tasks
Startup entries launch code when you sign in: Run keys, Startup folders, and newer Task Manager “Startup” rows. Software often leaves updaters, tray agents, or helper executables there.
Scheduled tasks run on timers or events. Uninstallers sometimes miss them; leftover scans may flag them. Before deletion, confirm the task name and path map to the product you removed, not to Windows or another vendor you still rely on.
These topics appear throughout leftovers article and scan best practices.