Cybersecurity

Unwanted software keeps appearing? Find the source before changing controls.

A website notification, a browser extension and an installed app need different responses. Identify what is actually happening, then address the source and the relevant controls.

16 October 2026  •  7 min read

Man pausing at a library computer with a neutral software dialog on the monitor

Reduce risk without breaking needed software

For Windows and Mac computers you own or are authorised to manage. Prevention, unwanted-app cleanup and an active malware incident are different tasks. A managed app returning may be an intended deployment; check with the responsible IT team before removing it.

Step 1 of 8

In this guide
  1. 01Identify and stop source
  2. 02App or browser
  3. 03Protection and staff controls
  4. 04Verify and get help

Identify the app or alert and who manages the device

An unfamiliar name alone is not proof of malware.

Record the exact app, browser notification, extension or security detection and when it appeared. Note the publisher/source shown by the genuine OS or browser, recent downloads and whether the computer is managed by work/school. Keep a screenshot free of passwords and private information if it will be shared.

Check the genuine installed-app list rather than click a website’s “scan result”. Windows 11 uses Settings, Apps, Installed apps; Mac applications and their supported uninstall instructions depend on the publisher. A visible browser alert is not proof an app was installed, while an installed app may include needed drivers or work-managed tools.

If there is a real security detection, encrypted files, unknown remote access or suspected account compromise, use the malware response guide and responsible IT/security contact. Do not keep opening a suspicious installer to reproduce the problem or assume deleting one icon removes an infection.

Keep the actual app/alert type, source and authority clear before choosing removal or prevention.

Stop the unwanted source and review install choices

Pause before accepting an extra app or unexpected prompt.

Cancel an unrequested install or elevation prompt when you can do so safely. Download only the intended product from its genuine publisher, official store or approved workplace portal. A sponsored download button, browser warning or search advert is not the publisher’s verification of a package.

Read installation choices instead of repeatedly accepting Next. Decline optional bundled apps, search changes or browser extensions you do not need. Keep legitimate app data and sign-in access intact; do not buy a “cleaner” offered by a pop-up to remove another unwanted program.

If the app returns after an update, record which updater, browser account or managed deployment coincides with it. Ask the owner/IT to confirm the expected software source. Do not delete updater folders, scheduled jobs or workplace agents by guesswork. Microsoft’s unwanted-software guidance supports genuine sources and deliberate app decisions.

Two adults discussing a neutral software dialog at a library computer

Keep the intended source and any declined extras recorded. Do not confuse cancelling a prompt with removing an installed app.

Remove only confirmed unwanted apps through supported methods

Preserve app data and leave managed or uncertain components alone.

Confirm the app is unwanted, you have authority to remove it and any needed data/licence/installer is preserved. On Windows, use the specific app’s Uninstall entry in Installed apps and its genuine prompts. On Mac, follow the developer’s uninstaller or supported removal method. Do not manually delete unfamiliar system or Library files.

Use the software removal guide for the preservation and verification steps. Removing a shortcut, disabling startup or blocking a download is different from uninstalling a program. Security quarantine/remediation also has its own supported workflow; do not restore a detected file merely to uninstall it.

Stop if removal is blocked, the publisher is unclear, protection reports an infection or it repeatedly returns. Keep the exact message and let IT/security assess persistence, management or account sync. Do not use a force-removal tool from an unknown site or assume a clean scan proves every unwanted behaviour is gone.

Keep the specific removal result and data preservation clear. Recurrence needs investigation, not broader blind deletion.

More checks5 detailed checks

Separate browser notifications, extensions and apps

A frightening browser alert may be a site permission.

Check the browser’s own settings for the exact source of an unwanted notification or extension. In Edge, Microsoft documents blocking notifications for individual websites and managing extensions. Open settings from the real browser menu rather than use a button inside the alert.

Revoke an unwanted site’s notification permission or remove a confirmed unwanted extension you are authorised to change. Preserve essential password-manager, accessibility and work-managed extensions. A site notification, browser pop-up and installed desktop program are different; changing notification permission does not uninstall malware.

Google’s Chrome unwanted-software guidance explains persistent search/extension changes. Check the specific app, sync or policy source if settings return. Do not reset every browser profile, delete saved data or remove management as a first response. Use the matching browser’s current controls.

Keep the exact site/extension change. A quieter browser is useful but does not certify the whole computer is safe.

Review supported device and browser protection

Keep the protections appropriate to this device and policy.

In the genuine Windows Security app, App & browser control includes supported reputation-based protection and, on eligible systems, Smart App Control. Microsoft’s current guidance explains available features. Check the actual device and organisation policy; do not assume every Windows version or third-party protection setup shows the same controls.

Potentially unwanted-app blocking, browser download warnings and malware protection have different scopes. A blocked or quarantined detection may need a supported action; it is not automatically the same as removal. Keep current updates and configured protection enabled. Do not turn off protection or create an exclusion because a wanted download is blocked; verify the exact file and warning with IT/publisher.

On Mac, retain the supported app-security controls and use genuine App Store/developer sources. Apple’s safe-opening guidance describes signature/notarisation checks; these reduce risk without promising every signed app is suitable or harmless. A background/login item can be legitimate; turning it off does not uninstall the app or establish whether it is malicious.

If a protection control is unavailable or managed, ask the responsible IT team about the supported option. Do not reset Windows merely to expose a feature or switch it off to experiment; availability and re-enabling conditions can differ.

Keep supported protection and its scope understood. Do not treat one setting, signature or clean result as a guarantee.

Use account and business controls as layers

Approved software needs a practical request and update path.

Agree who manages the device and which software sources are approved. Use appropriate everyday account permissions while retaining a tested authorised administrator/recovery route. Microsoft recommends limiting administrators in its account guidance. Standard-user use reduces unnecessary elevation but is not a complete policy preventing every per-user app or download.

For staff devices, define needed applications, an approved request/install process, update ownership and how an unexpected block is reported. Web filtering and browser controls address parts of the download path; execution/application controls address a different layer. Do not assume filtering every risky site guarantees that no unwanted app can run.

Responsible IT can assess suitable supported controls, first inventorying required apps and testing policy impact. Microsoft’s application-control planning guidance includes audit/testing and support needs. This is not a one-click policy to apply blindly: a poorly planned rule can block legitimate work. Our web-filtering support can be part of reviewing the appropriate layers, with scope and limitations agreed.

Keep required apps, ownership, recovery and a support route working while controls are tested. No single layer guarantees prevention.

Verify behaviour without a dangerous test download

Check the intended work and the original unwanted behaviour.

Reopen the normal app/browser and check whether the original unwanted alert, extension change or app returns. Confirm the needed legitimate app, accessibility functions and work process still operate. Use harmless ordinary tasks, not a malware sample, cracked installer or deliberately unsafe website to test protection.

Review genuine protection history/status and any relevant IT test result within the agreed scope. Record the specific source/removal/permission/policy change and whether the behaviour recurs after a normal reopen or restart. Do not approve a new unexpected prompt to see what happens.

If the original behaviour has stopped and needed work remains available, retain the verified setup and stop changing settings. If it returns, keep the timing and exact evidence for assessment. Absence of a pop-up or one clean scan does not prove all accounts and devices are uncompromised.

Keep the verified normal behaviour and supported controls. Recurring or suspicious activity needs the recorded evidence, not more blind removals.

Back to the symptom checker

When should you get help with unwanted software?

Escalate persistence, compromise or policy questions safely.

Get help when apps/extensions repeatedly return, the source or management is unknown, removal is blocked, protection reports an infection or a business policy could interrupt required work. Include the exact app/site/extension, OS/browser, detection/error and changes already tried.

Our malware and unwanted-software support can help assess the observed behaviour and a suitable response. For suspected compromise, prioritise containment and legitimate account/security support rather than treat it only as an installation preference.

Use an agreed private support channel and share only necessary evidence. Do not provide passwords, MFA codes, remote-access codes from unsolicited callers or full private browsing records as a first report. No tool or filtering plan can promise to stop every unwanted program.

Keep the device, legitimate access and useful evidence intact while the appropriate security or policy response is agreed.

Book IT support

Frequently asked questions

Does a website virus alert prove software was installed?

No. A web page or notification can imitate an alert. Check the genuine app/browser/security source and avoid its phone number, download or remote-access request.

Will a standard account prevent every unwanted app?

No. Appropriate account permissions are one layer. Download, per-user app, browser and execution controls have different scopes; shared or business devices need an agreed tested plan.

Is blocking a download the same as removing an installed app?

No. Prevention, blocking, quarantine and uninstall/remediation are different actions. Use the genuine supported tool and verify the actual result.

Why does an app or extension keep returning?

A bundled updater, browser sync, managed deployment or malicious persistence may be involved. Record the timing/source and investigate rather than delete random scheduled jobs or management tools.

Should I disable protection to install a blocked program?

Do not bypass protection as a routine install step. Verify the genuine source, package and exact warning with the publisher or responsible IT team.

More practical IT guides

View all guides

Share this guide