When malware returns after a reboot, the problem is often persistence: an app, scheduled task, service, registry entry, or startup-folder file that launches it again. This checklist explains how to perform a cautious Windows malware persistence check, verify suspicious entries, and decide when to disable, quarantine, or escalate an item without breaking legitimate software.
Overview
Windows provides several normal ways for software to start automatically. Security tools, device drivers, cloud storage clients, update managers, accessibility utilities, and business applications may use startup apps, services, scheduled tasks, or registry keys. Malware can use the same mechanisms, which means an unfamiliar entry is not automatically malicious.
The goal is to identify entries that are both unusual and risky. Look for a combination of warning signs: an unknown publisher, a file running from a temporary or user-profile folder, a misspelled product name, a recently created entry, an unsigned executable, a random-looking filename, or behavior that matches pop-ups, browser redirects, high resource use, or repeated antivirus detections.
Before changing anything, record the entry name, command, file path, publisher, and date observed. If the computer may be part of an active incident, disconnect it from unnecessary networks while preserving access needed for investigation. Do not delete evidence or repeatedly reboot a system that may contain ransomware or an active intruder. For a broader recovery process, see the post-cleanup security checklist and the ransomware incident response checklist.
Checklist by scenario
1. Review ordinary startup apps
- Open Settings, select Apps, then Startup. Review each item and its startup impact where shown.
- Open Task Manager with Ctrl+Shift+Esc, select Startup apps, and compare the list with Settings.
- Right-click an unfamiliar entry and choose Search online only as a starting point. Search results are not proof of safety.
- Use Open file location when available. Note the complete path, filename, publisher, and digital signature before taking action.
Disable an item temporarily rather than deleting it when you are still investigating. A clean reboot can show whether the behavior changes, but do not use this as a substitute for an antivirus scan.
2. Inspect scheduled tasks
Open Task Scheduler and review Task Scheduler Library and relevant subfolders. Pay attention to tasks that run at logon, startup, idle time, or on a recurring trigger. Examine the Actions tab: a task that launches a script interpreter, a file in a temporary directory, or an executable with an unclear name deserves additional verification.
Check the Triggers, Conditions, Settings, and History tabs when available. A legitimate updater can have a frequent schedule, so frequency alone is not evidence of malware. Record the task name and action before disabling it.
For a read-only PowerShell inventory, open PowerShell and run:
Get-ScheduledTask | Select-Object TaskPath,TaskName,State
To inspect a particular task, use its name and path with Get-ScheduledTaskInfo. Avoid running commands that delete tasks until you have confirmed the item is malicious or unwanted and have preserved the details needed for recovery.
3. Find suspicious services
Open Services by searching for it from the Start menu, or run services.msc. Review services set to start automatically, especially those with a vague display name or a binary path under a user profile, temporary folder, or unusual directory. Open the service properties and record its service name, executable path, startup type, and publisher.
A service may be essential even when its display name is unfamiliar, and stopping one can cause loss of network, security, or device functionality. If you need an inventory rather than a change, PowerShell can list service names, states, and start modes:
Get-CimInstance Win32_Service | Select-Object Name,DisplayName,State,StartMode,PathName
Do not stop or disable a suspected service while an incident is being handled by an IT or security team unless that team has approved the action.
4. Check registry run entries and startup folders
Common autostart locations include the current user and all-user Run registry keys, as well as the Startup folders. You can inspect the folders by pressing Win+R and entering shell:startup and shell:common startup. Review shortcuts and scripts for unknown targets.
For a read-only PowerShell review of common Run keys, use:
Get-ItemProperty 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Run'
Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Run'
Registry paths can differ on 32-bit and 64-bit installations, and legitimate applications may use other persistence locations. For a fuller inventory, Microsoft Sysinternals Autoruns can show many autostart locations in one interface. Download utilities only from their official publisher and review entries before using its disable or delete functions.
5. Verify the file before acting
Right-click the executable, open Properties, and inspect Digital Signatures and Details. A valid signature supports authenticity but does not guarantee that the file is safe; a missing signature is a reason to investigate, not automatic proof of malware.
Calculate a hash when comparing the file with a known sample or an incident record. A reputation service such as VirusTotal may help identify detections, but do not upload confidential documents, private scripts, proprietary binaries, or sensitive personal data. A result with few or no detections should be treated as one signal, not a clean bill of health.
Run an updated Microsoft Defender scan, and consider a Defender Offline scan when malware may be active before Windows fully starts. If another reputable antivirus product is installed, avoid running multiple real-time engines together unless the vendors explicitly support that arrangement. If an antivirus alert may be a false positive, follow a documented verification process before restoring a quarantined file; see how to verify an antivirus false positive.
What to double-check
- Path and spelling: Compare the filename and directory with the software vendor's documented installation path. Malware may imitate a trusted name with a minor spelling change.
- Parent process and command arguments: A legitimate executable can be abused with unusual parameters. Record the complete command, not just the filename.
- Timing: Compare the entry's creation or modification time with a new installation, browser extension, update, or the first appearance of suspicious behavior.
- Related entries: Malware may create more than one persistence method. If you find one suspicious task, also review startup apps, services, Run keys, and recently installed programs.
- Backups and restore points: A restore point may help recover from an accidental change, but it is not a guaranteed malware-removal method. Do not restore an infected backup.
- Accounts and credentials: If malware was confirmed, change important passwords from a known-clean device, enable multifactor authentication where available, and review account activity.
For business devices, preserve logs and document every change. Compare the machine with a known-good endpoint or an approved software inventory rather than relying only on personal judgment. The small-business endpoint security policy template can help turn this review into a repeatable process.
Common mistakes
- Deleting an unfamiliar item immediately: This can break Windows, remove evidence, or make later investigation harder. Quarantine or disable only after recording the details and assessing the risk.
- Trusting the name alone: Names such as “Update,” “Service,” or “Security” are easy to imitate. Verify the path, signature, behavior, and reputation.
- Using random cleanup scripts: Unreviewed scripts can remove legitimate tasks or introduce additional code. Prefer built-in Windows tools and established security utilities.
- Ignoring browser and account symptoms: A browser hijacker, stolen session, or unwanted extension may not appear as a classic startup item. Review browser extensions, reset compromised credentials, and scan the device.
- Assuming a scan ended the incident: Malware removal should be followed by updates, password review, backup validation, and monitoring. See the malware-safe backup plan before relying on old backups.
When to revisit
Repeat this Windows malware persistence check after an antivirus detection, unexplained pop-ups or performance changes, installation of untrusted software, recovery from an incident, or a major operating-system or security-tool update. It is also useful during quarterly endpoint reviews and before seasonal planning cycles, when you can compare current entries with a documented baseline.
On the next review, start with the baseline: export or record approved startup apps, scheduled tasks, services, and software paths. Investigate only what is new, changed, unsigned, or inconsistent with the device's role. If symptoms continue, detections return, files are encrypted, or an attacker may have accessed accounts, stop experimenting with manual deletion and involve a qualified incident-response professional or your organization's security team.
Action checklist: update Windows and security definitions; record suspicious entries; run a full scan and, when appropriate, an offline scan; isolate the device if compromise is suspected; preserve evidence; remove or quarantine only after verification; change credentials from a clean device; and schedule a follow-up review. Revisit this workflow whenever Windows menus, security tools, or your organization's approved software inventory changes.