Windows security and malware cleanup
Choose a Windows cleanup path by checking support status, the active antivirus, recorded findings, browser symptoms, and recovery needs.
Windows cleanup starts with the device’s actual protection and the problem you observed. Identify the Windows version, security provider, and relevant findings before choosing a scan, browser correction, or recovery operation. A slow application, alarming web page, or disabled Defender notification alone does not establish an infection.
This guide connects the Windows checks to the site’s detailed procedures. It covers desktop Windows, with current Windows 11 terminology where needed. Work and school devices may have administrator-controlled security; their configuration and incident response belong with that administrator.
Choose the situation before changing the device
If the issue is slowness without a security finding, start with resource and startup diagnosis or high-CPU investigation. Those guides separate ordinary workloads from evidence that warrants security assessment.
Write down what happened, when it began, and whether you opened a download, changed a permission, or approved remote access. Preserve the exact security finding if one exists. The same visible symptom can require very different action depending on that context.
| Situation | First useful check | Follow-up route |
|---|---|---|
| One website shows a frightening warning | Whether it is page content or a real security finding | Pop-up investigation |
| Searches or startup pages changed | The affected browser setting and its controller | Browser-hijacker removal |
| Windows reports protection is off | The intended antivirus provider and current status | Disabled Defender investigation |
| A scanner reports a suspicious item | Its path, classification, and completed or pending action | Windows scanning |
| Files are encrypted or unauthorized access is continuing | Urgency, affected data, and available trusted help | Infection diagnostic |
For credible active theft, remote control, or encrypted files, prioritize the diagnostic’s incident response rather than experimenting with cleaner settings. An ordinary cleanup workflow cannot undo information already stolen. If the problem is a crash or failed update without malware evidence, supported Windows troubleshooting may be the appropriate path.
Check support and update status
Record the edition and version shown by Windows before following a version-specific procedure. A supported operating system and a current antivirus are separate requirements: detection updates help recognize threats, while operating-system patches address vulnerabilities in Windows itself.
Ordinary Windows 10 support ended on 14 October 2025. If you remain on Windows 10, check the applicable Extended Security Updates arrangement, enrollment, and coverage or plan a supported migration. Do not assume that an antivirus still updating means the operating system receives all necessary fixes. Windows 11 also needs the applicable version’s updates and support checks.
Use Windows Update through Settings and inspect whether updates completed or need a restart. For Defender, Microsoft distinguishes security intelligence, engine, and platform updates. If another antivirus provides protection, inspect its own update status. Record failed updates for support instead of repeatedly disabling protection to make them proceed.
Find the antivirus Windows is actually using
Open Windows Security from Start. In its Settings, use Manage providers to inspect the registered antivirus, firewall, and web-protection providers. Microsoft documents these categories separately; an antivirus name is not a summary of every security function.
If a third-party antivirus is installed and active, Defender Antivirus may be inactive as part of that configuration. Verify that the provider you intended is running and current. Installing another product can change provider registration, so repeat this check after adding or removing security software.
Microsoft Defender Antivirus is the built-in Windows antivirus. The separate Microsoft 365 Defender app and enterprise products use related names but do not make every feature interchangeable. Use the profile for those distinctions and the disabled Defender guide if the actual provider state is unclear.
On a managed device, a policy restriction is a reason to involve IT. For a personal device with unexpected restrictions, preserve the displayed message and installation history for investigation. Forced service changes, broad exclusions, or registry edits can obscure the cause and reduce protection.
Match scanning to the evidence
When the provider is current, choose a scan around the unresolved question. A specific download may warrant a targeted scan; broader unresolved findings can justify wider inspection. Windows Security’s scan guidance and the Windows scan article explain the available options and how to read their scope.
Save the scan type, completion state, detection name, affected item, and requested action. Protection History distinguishes recorded actions from items still needing attention. A blocked download does not prove that an installed application was removed; a clean result does not inspect every browser permission or establish that an online account is secure.
Microsoft Defender Offline is a conditional option, especially when Defender requests it or the investigation warrants scanning outside normal Windows. Its current requirements include supported hardware, Defender as primary antivirus, administrator rights, current updates, and an enabled recovery environment. ARM Windows devices are excluded from this feature. Follow the scan guide’s restart and BitLocker preparation rather than interpreting a restart as proof that the scan completed.
Handle unwanted applications and browser changes together
If the evidence points to an unwanted installed application, use Windows’ supported uninstall route. Record the application and result. Manually deleting a setup file or similarly named system file does not establish that the installation was removed.
Browser permissions and extensions may need separate handling. Use the Windows adware removal guide for advertising software and the Chrome guide for Chrome-specific controls. AdwCleaner fits focused unwanted-software tasks; Malwarebytes can provide broader scanning. Choose around the remaining evidence and active provider, rather than making every tool mandatory.
After recorded cleanup and any required restart, check the original behavior on trusted pages. If an extension, application, or finding returns, retain its exact identity and timing. Recurrence after an update, sign-in, or reinstall is a lead to investigate, not a diagnosis by itself.
Know when recovery needs a wider plan
For unresolved compromise or a device whose integrity cannot be established, review Microsoft’s recovery options with IT or qualified support. Resetting, restoring, and clean installation have different consequences. The malware-specific guidance describes scanning first and considering a clean installation when the problem continues; it is not a reason to erase a device after one advertising message.
Before a destructive recovery choice, establish which personal data is needed, which backup predates the incident, and how legitimate applications will be restored. Preserve essential incident records separately. Recovery can remove files, applications, and settings; restoring an old installer or unwanted component can recreate the problem. Keep BitLocker recovery access available privately when relevant.
Device recovery does not revoke an exposed account session or resolve fraudulent payments. Use the account recovery guide from a trusted device for password, session, and recovery-setting checks. The post-cleanup recovery guide keeps device verification and restoration tasks separate. After the local issue is resolved, use the safer browsing routine to review downloads, permissions, and updates.
Official documentation was checked and this guide was edited on 6 October 2026. These are documented investigation and recovery paths, not results of a site-run Windows infection test.
Sources & documentation
Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.
- Microsoft: Virus and threat protection in Windows Security
- Microsoft Support: Windows Security settings and providers
- Microsoft Support: Windows 10 end of support and ESU options
- Microsoft Learn: Security intelligence, engine, and platform updates
- Microsoft Support: Protection History in Windows Security
- Microsoft Learn: Microsoft Defender Offline requirements and scans
- Microsoft Support: Uninstall apps and programs in Windows
- Microsoft Support: Windows recovery choices and data-loss consequences
- Microsoft Support: Find your BitLocker recovery key