Potentially unwanted programs
Investigate a PUP finding by its vendor criteria, exact item, installation context, and recorded action. Decide between supported removal and further review.
A potentially unwanted program finding calls for a decision about a specific item under a security vendor’s criteria. Read the complete alert, determine whether the item was merely downloaded or actually installed, and connect the classification to its behavior. Recognizing the application’s name does not settle that decision.
This investigation applies to desktop Windows and Mac. The PUP glossary explains the term and its relationship to PUA; this article focuses on responding to an actual finding, including software you may rely on. The detecting product and device policy determine the available handling options.
Read the full finding before choosing an action
Record the product, complete detection name, affected path, detection time, and action already taken. Preserve the scan type and whether it completed. A PUP warning about an unopened installer is different from a finding about an installed component that changes browser settings.
| Finding context | What it establishes | Next question |
|---|---|---|
| Download was blocked | The product acted on that download | Is there evidence that an earlier copy was installed or run? |
| Installer file was quarantined | That identified copy was isolated | Which applications or components, if any, were already installed? |
| Installed application or extension was identified | A component on the device met the vendor’s rule | What behavior or distribution practice explains the classification? |
| Handling is incomplete | The requested action did not finish | What supported remediation does the product require? |
| Several paths refer to the same application | The report identifies several objects | Do the entries belong to one installation or separate components? |
Malwarebytes’ detection category includes PUP and PUP.Optional labels. Optional is part of that naming convention, not a verification that the item is harmless. Read the vendor’s explanation for the full label rather than reacting to a single word.
On Windows, Protection History distinguishes security actions and unresolved items. Other products provide their own history. A finding that was already handled does not need the same response as one still awaiting action.
Understand why the vendor flagged it
Malwarebytes’ published criteria describe concerns including deceptive advertising or distribution, unnecessary settings changes, exaggerated findings used to sell software, and difficulty removing it. The vendor also explains that categorization involves judgment and can change as software evolves.
Microsoft uses the term potentially unwanted application and publishes its own classification criteria. Its categories include advertising, bundling, and marketing behavior, with some categories limited to enterprise context. Microsoft’s PUA classification is separate from its malware classification. Do not assume every vendor applies the same boundary or that two different names express the same risk.
Translate the classification into questions about your copy. Was an extra application clearly offered? Did it change an unrelated setting? Does a utility justify its alarming findings? Can it be removed through supported controls? An application can perform a useful advertised function while still raising those concerns.
A personal preference and a vendor detection are different kinds of evidence. You can choose to uninstall software you no longer want without proving it was malicious. Overriding a security detection, however, needs an assessment of the item and the reason it was flagged.
Check the installation context and actual behavior
Compare the alert with recent downloads, applications, browser extensions, and installation choices. Note the publisher and origin shown by supported interfaces, but avoid treating a familiar name, icon, or signature as a complete safety guarantee.
For an illustrative bundle, the application you intended to install and the additional search extension may be separate objects. Determine which one the product flagged and which one produced the unwanted behavior. Removing a downloaded setup file alone does not establish that its installed components were removed.
If the concern involves advertising or changed browsing, use the adware investigation or browser-hijacker investigation. A PUP label may help explain those behaviors, but not every PUP is an advertising application. Keep the scope of the actual finding visible.
For software you did not intend to install
Use the security product’s supported handling and confirm the completed action. For an identified unwanted installed application, Windows uninstall guidance and Apple’s Mac removal guidance explain their supported routes. Some applications have an uninstaller for their associated components; use the route appropriate to that product.
Preserve the report and investigate the identified installation through supported controls. Manually deleting a similarly named system file can affect a different component and leaves the actual finding unresolved. If advertising is the main concern, the adware removal guide covers cleanup around the responsible application, extension, or permission.
AdwCleaner is a focused Windows option when unwanted software remains implicated. Malwarebytes provides desktop scanning on supported Windows and Mac systems. Select a tool around the unresolved question and its platform rather than treating another scan as a mandatory step after every PUP alert.
For software you need or a disputed detection
Keep the identified item isolated while gathering its exact version, source, detection name, and classification explanation. Check whether a supported alternative can meet the immediate need. A business-critical application requires the administrator’s review, particularly when device policy blocks it.
Follow the false-positive evidence process if the rule appears mistaken. Malwarebytes’ reporting guidance illustrates seeking review from the detecting vendor. An online report about a different release or download does not establish that your copy was classified incorrectly.
Restoring or allowing the item is a separate decision with consequences. Malwarebytes’ quarantine documentation distinguishes restoration, allowing future use, and permanent deletion. An exclusion changes inspection behavior; it does not demonstrate safety. Avoid a broad exclusion merely to silence the alert.
Do not infer incident severity from the label alone
The page’s low general risk context is not a guarantee about the item on your device. A bundled component, misleading sales utility, and application associated with additional malicious findings can require different responses. Assess the observed behavior, permissions, completed actions, and any separate evidence of theft or unauthorized access.
If you entered credentials, approved remote access, or paid through a deceptive prompt, address that exposure even if the software finding uses a PUP label. Use the infection diagnostic to prioritize a broader response. Conversely, a blocked unopened installer alone does not prove that its advertised application previously ran.
Verify the result and investigate recurrence
After supported handling or uninstall, check the original behavior and relevant installed components. Retain the report so that an unexpected effect can be compared with what changed. Quarantine explains why leaving a copy isolated and deleting it permanently preserve different recovery options.
If the same finding returns, compare exact paths, event times, actions, and recent installation or update activity. The recurrence could involve another accessible copy, incomplete handling, or software being installed again. Those are questions to investigate rather than a reason to assume a new infection from the detection count.
Seek IT or qualified support for failed remediation, unexplained reinstallations, or a disputed component needed for work. A useful resolution records what met the rule, which action completed, and whether the unwanted behavior or unresolved classification remains.
Official documentation was checked and this article was edited on 6 October 2026. The examples are investigation scenarios; no site-run malware experiment or assessment of a reader’s device is implied.
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.
- Malwarebytes: Potentially unwanted software classification criteria
- Malwarebytes: PUP and PUP.Optional detection category
- Microsoft Learn: Malware and potentially unwanted application criteria
- Microsoft Support: Protection History in Windows Security
- Malwarebytes Help: Manage quarantined items in Windows and Mac
- Malwarebytes Help: Report a false positive
- Microsoft Support: Uninstall apps and programs in Windows
- Apple Support: Uninstall Mac apps and included components