Security tools

RKill

Understand RKill as a cleanup preparation helper, its older compatibility listing, process-termination log, and why a separate antivirus scan must follow.

Purpose
Cleanup preparation
Vendor
BleepingComputer
License model
free
Platforms
Windows
Testing status
Editorially researched

Documentation research is not a measure of detection or cleanup effectiveness.

RKill is a Windows cleanup preparation helper developed at BleepingComputer. Its stated purpose is to stop known interfering malware processes so ordinary security software has a chance to run. RKill does not delete malware files. A completed run is therefore a preparation event, not a completed removal or an all-clear.

This is a narrower and less routine choice than starting a supported antivirus scan. If your security software opens and scans normally, begin with its normal workflow. Consider RKill only when a specific investigation identifies interference and the product’s compatibility and use are appropriate.

Check the age of the published evidence

The publisher’s download page, checked on 6 October 2026, lists version 2.9.1.0 and a last-update date of 15 November 2018. Its Windows list ends at Windows 10. The older list is not evidence of verified Windows 11 support, current architecture coverage, or compatibility with every modern security configuration.

The linked author introduction was started by Lawrence Abrams in 2010 and contains historical updates. We use the author’s explanation of scope, not replies from other forum participants as current product specifications. Check current publisher guidance and obtain qualified help when the older documentation does not resolve your setup.

Use the publisher’s own download route when a supported workflow calls for the tool. Do not substitute a similarly named package from an advertisement or an unofficial bundle. This site links to the publisher; it does not distribute RKill binaries.

What it attempts to change

BleepingComputer describes process termination, correction of executable associations, and repair of policies that interfere with certain tools. It also documents a log of terminated processes. These actions can help an investigator understand what happened, but the helper does not supply the later scanner’s removal work.

SituationAppropriate decisionWhat not to infer
Antivirus opens normallyUse the supported scan workflow firstRKill must precede every scan
A security app is blockedInvestigate the cause and compatibilityMalware is the only possible cause
RKill reports terminated processesPreserve the record and run supported scanningThe files were removed
A legitimate app closesRecord the effect and investigate the entryEvery terminated process was malicious
Symptoms recur after cleanupReview scanner results and persistenceRepeat RKill indefinitely

Save ordinary work before any process-termination step. Unexpectedly closing applications can interrupt their current tasks. On a managed computer, a blocked security interface or restricted executable may reflect an administrator’s policy; use the responsible support process rather than overriding it.

Prepare the follow-up scan in advance

Establish which trusted scanner you will use and how you will obtain its current version or updates. Do that planning before a preparation step so success does not leave you wondering what to run next. Our Windows scan guide explains scope, findings, and follow-up records.

The publisher specifically says to scan immediately after RKill and not reboot between RKill and that follow-up scan, because automatically starting malware processes can return. Distinguish that instruction from a restart the antivirus later requests as part of its own supported remediation. The antivirus’s result and action record remain the relevant evidence of cleanup.

If interference continues, do not cycle through renamed downloads, forced changes, and reboots without a coherent diagnosis. Preserve the error, the log, and the sequence of actions for qualified support. If ransomware or account theft is suspected, follow the incident’s recovery priorities rather than treating process termination as sufficient containment.

Read the log without treating it as a verdict

Record whether the utility completed, what it reported, and whether the intended scanner subsequently opened. An empty termination list does not prove there is no malware. A list of terminated processes does not show that every infection component was found or removed.

The author’s introduction discusses the possibility of false positives in process termination. If a legitimate program stopped, investigate its identity and role; do not assume its files should be deleted. Use the false-positive guide when a separate security product raises an alert. An alert on a downloaded tool is a reason to verify provenance and obtain vendor guidance, not an automatic instruction to disable antivirus protection.

Keep logs local until you understand whether they reveal private paths or system details. This article does not ask you to upload files or submit samples.

Confirm recovery through the security product

Check the follow-up scanner’s completed and unresolved actions, then revisit the original symptom. Verify the active protection arrangement through Microsoft’s Windows Security settings guidance. A successful preparation helper cannot establish that ongoing protection is enabled.

For an updated portable Microsoft scan option, read Microsoft Safety Scanner. Malwarebytes describes a separate scanner and protection product family; neither is interchangeable with RKill’s narrow preparation role.

This profile received a documentation and editorial pass on 6 October 2026. We have not run RKill, verified its current Windows compatibility, or measured effectiveness. See the methodology for the research criteria.

Reasons to consider it

  • A narrow preparation role when interfering processes prevent supported cleanup
  • Produces a record of process termination

Limitations to understand

  • Does not delete malware files or provide quarantine
  • Published release and operating-system details are old

Sources & documentation

Sources checked on 6 Oct 2026. Documentation research does not establish independent testing.

MalwareCleanupTools

Guides based on official documentation. About our content · Corrections policy

No affiliate links are included in this build. Read our disclosure.