AFKSecurity

Local substrate cybersecurity agent · Available
1.1.3 Current version · 8 November 2026

The installed version is shown under About in the software, and these notes appear in its Updates tab.

Releases

1.1.3 8 November 2026 Recommended

A trial now ends on its date, AFKSecurity keeps only the latest downloaded installer, and uninstalling removes its folders from every user account.

Fixed

  • The 14-day trial now ends on its date. The safety margin meant to protect paying customers during an outage of our server also applied to the trial, so a trial could last longer if the server was blocked. The margin now applies to paid licences only.
  • Each update kept the installer it downloaded, and none was ever removed. Before downloading a new version, AFKSecurity now removes the installers left by earlier updates: only the latest one remains.
  • Uninstalling now removes AFKSecurity's folders from every user account on the computer (window data, downloaded installers, diagnostic notes), not only from the account that uninstalls.

1.1.2 3 November 2026

Uninstalling now removes the protection service completely and checks that it is gone. AFKSecurity also tells you when an update is available, at most once a day, and states how long it receives security updates.

Security

  • Uninstalling now checks that the protection service has really been removed from Windows. Previously, if the removal failed, a system service could stay registered while its program was deleted, which another program could later take over. If Windows cannot finish the removal at once, the service is disabled and you are asked to restart.
  • Uninstalling also lifts any network isolation in progress, releases any program AFKSecurity had frozen, and erases the protection's settings and data. The journal stays your choice, as before.

Added

  • A Windows notification when an update is available, at most once every 24 hours. Nothing is installed without your click: AFKSecurity only reads a short signed file to find out.
  • The About tab now shows how long security updates are provided (AFKSecurity 1.x: free until at least September 2031) and how to report a vulnerability.

Changed

  • The licence agreement, terms of sale and privacy policy installed with the software describe the support period, the daily update check, and who can stop the protection.

1.1.1 24 October 2026

Fewer interruptions: a Windows notification now only appears for a strong alert, Microsoft Defender's library is no longer mistaken for a keylogger, and the last alert stays visible in the window until you open it.

Changed

  • AFKSecurity now only shows a Windows notification, or reopens its window, when a hypothesis reaches 80 %. Between 60 % and 80 % the alert is written to the journal and shown in the window, without interrupting you. A program frozen and waiting for your answer is always notified, whatever the level.
  • When a hypothesis has been raised, a line under it now says when and how high, until you click it. The click shows the matching journal line. Previously the bar only showed the current moment, so an alert could be gone by the time you opened the window.

Fixed

  • Libraries loaded from a temporary or shared folder had their signature checked under a path Windows cannot open, so they were all treated as unsigned. Microsoft Defender's library could be reported as a keylogger and raise the credential theft hypothesis. Signatures are now checked on the ordinary path.
  • A program writing many files while another part of AFKSecurity had already noticed it (for example an AI assistant that had written to the clipboard) could raise the ransomware hypothesis even though nothing was renamed or lost. Such a remark now only counts once files have actually been lost.

1.1.0 23 October 2026

Fewer false alerts: your being away is no longer counted as evidence of an attack, and a program's history no longer leaks into another program's verdict.

Fixed

  • A program writing many files while you were away (for example an AI assistant working on its own) could push the ransomware indicator up, even though nothing was renamed or lost. Your absence counted as a second, independent clue. It now still weighs on the assessment, but it can no longer turn a single clue into a coincidence on its own.
  • When AFKSecurity reused a slot of its internal memory for a new program, the slot kept the links of what it held before. This could list unrelated programs as sources of a hypothesis (for example under Exfiltration). A reused slot now starts with no links.

1.0.9 23 October 2026

AFKSecurity no longer mistakes Microsoft Defender for an attack and never tries to freeze your antivirus. An alert now shows a Windows notification even when the window is closed, and a Microsoft signature now settles who a program is, never what it is allowed to do.

Security

  • A Microsoft signature, or being shipped with Windows, now only settles who a program is. Until now it exempted the program from being reported as unusual, whatever it did. It is now judged on its behaviour like any other program: a Microsoft program that runs an encoded command in a hidden window while you are away is still reported.
  • Windows tools that attackers misuse to run their code (certutil, mshta, rundll32, regsvr32, msbuild and others, MITRE ATT&CK T1218) never get any trust from their signature or their location.
  • New: DLL side-loading (T1574.002). A Microsoft-signed program copied into a download or temporary folder that loads, from its own folder, a library Microsoft did not sign is now reported.
  • AFKSecurity now reads the Windows catalog signatures that most programs shipped with Windows use, without going online.

Added

  • When an alert starts and the AFKSecurity window is closed, AFKSecurity reopens it in the notification area and shows a Windows notification. At most one per hypothesis every 30 minutes.

Fixed

  • Microsoft Defender scanning many files (for example during an antivirus test) could be reported as encrypting them, and AFKSecurity tried to freeze it. Defender's components are now recognised by their Microsoft signature and their location, never by their name alone. And AFKSecurity never tries to freeze a process that Windows protects, which is how your antivirus runs.
  • A tool chain started by a known, signed program you use every day (for example an AI assistant that opens a hidden command prompt and then PowerShell) is no longer reported because of the chain itself. Whatever that chain does to your files, your network or your startup programs is still judged like anything else.
  • The reasons listed under a hypothesis no longer include what holds it back, such as a program being part of your usual activity.

1.0.8 22 October 2026

Windows' own maintenance programs no longer push the exfiltration and credential theft hypotheses to 100 % on a healthy computer, and Microsoft Defender's library is no longer reported as a hook.

Fixed

  • Programs that ship with Windows, such as WmiApSrv.exe, cleanmgr.exe or DismHost.exe, could be reported as unusual during Windows maintenance. They are signed through Windows catalogs, which the last check before reporting did not read, so they counted as unknown programs and pushed the exfiltration and credential theft hypotheses up to 100 %, in red, on a healthy computer. They are now recognized by where Windows installs them. Windows tools that attackers can misuse, such as PowerShell, are still judged.
  • Microsoft Defender's library (MpOav.dll) could again be reported as a hook after a long session: the product lost track of where it had found it, and could no longer check its signature. It now keeps that information.

1.0.7 21 October 2026

AFKSecurity now installs and uninstalls cleanly on Windows 11 with Smart App Control turned on, and uninstalling no longer leaves anything running. Still on 1.0.5: download the installer from the download page, choose Stop protection in the menu of the AFKSecurity icon next to the clock, then run the installer. It starts the protection again.

Fixed

  • On Windows 11 with Smart App Control turned on, Windows could block the installer ("An Application Control policy has blocked this file", error 4551) or the uninstaller. Only the downloaded file was signed; the setup program it unpacks and the uninstaller were not. Every part of the installer and of the uninstaller is now signed.
  • Uninstalling now closes the AFKSecurity window in the notification area first. Until now it kept running after the uninstall, and its file could not be removed.
  • Uninstalling now waits until the protection service has actually stopped before removing it, instead of a fixed three seconds. On a busy computer the service could stay behind until the next restart, and it cannot be ended from the Task Manager, by design.

If a previous version left something behind on your computer, restarting Windows removes it. If anything remains after a restart, write to support@afksecurity.online.

1.0.6 15 October 2026

Only Windows itself, or the AFKSecurity window, can now stop the protection. AFKSecurity no longer mistakes its own installer for an attack, and the log keeps the lines that explain an incident even when the computer is switched off by force. Updating from 1.0.5: choose Stop protection in the menu of the AFKSecurity icon next to the clock before installing, because 1.0.5 may still mistake this installer for an attack. The installer starts the protection again.

Security

  • Until 1.0.5, any program running in your session could switch the protection off through an internal stop signal, without administrator rights. Only Windows itself can send that signal now.
  • An administrator account can no longer stop, pause, reconfigure or delete the protection service from the command line or from the Services console (sc stop, net stop, sc config, sc delete). Scripts that turn off security software before encrypting files often do exactly that. The off button in the AFKSecurity window works as before, and so do updates and uninstalling. An administrator who is determined to stop the service can still do it, but a generic script cannot.

Added

  • Every requested stop is written to the log as it happens, with how it was asked for: by Windows, by the window, or because Windows was shutting down. At the next start, the log and the Status tab say how long the computer went without protection (a normal Windows shutdown is not reported). A stop that came neither from the window nor from a shutdown is shown as a warning. Until now, a stop from the Services console left the log silent, and that silence looked the same as a computer that was switched off.

Fixed

  • Updating from 1.0.4 to 1.0.5 could freeze the AFKSecurity installer, report it as encrypting files and stealing passwords, and cut the computer's network until the next restart. The installer of another program from the same publisher was also frozen. AFKSecurity now recognises programs signed by its own publisher, and the unpacked installer they launch, and no longer treats them as an attack. The log says when this happens. Windows tools that attackers can misuse are never trusted this way, and an unsigned copy of AFKSecurity trusts nobody.
  • When the computer was switched off by force, the last minutes of the log could be missing, and those were often the lines that explained what had happened. The 1.0.5 notes said a power cut would lose no line, and that was wrong: Windows can hold back what was written. Lines that explain an incident are now written to the disk at once, and routine lines within a minute.
  • Uninstalling now also removes the window's cache folder (%LOCALAPPDATA%\com.afksecurity.console, about 30 MB). It only held the chosen language and the last tab you opened.

1.0.5 4 October 2026

An optional password for exceptions, a warning when the vault has been tampered with, no more slowdown when a program keeps reopening the microphone or the camera, and no more network connections from the protection service.

Added

  • An optional password for exceptions, in Settings. Once it is set, granting an exception needs it, and so does ticking Don't ask me again for this program. Someone sitting at your computer, or a program driving the window, can no longer tell AFKSecurity to leave a program alone. Removing an exception never needs it. The password itself is never stored: only a slow, salted fingerprint of it, kept in the vault. Each wrong attempt is written to the log, and after three in a row the wait between attempts grows.
  • If you forget the password, the licence key of that computer replaces it. Available since 15 October 2026, after an update of our licence server, from the next daily check. Details: Why does the software ask me for a password?
  • If the vault where AFKSecurity keeps its settings is erased, modified, replaced, or put back from an older copy, AFKSecurity says so at the next start: a red banner in the window, a Windows notification and a line in the log.

Changed

  • The protection service no longer opens any network connection. To check who published a program, it used to let Windows fetch certificate revocation lists over port 80, which a firewall could show as many short connections in a row. It now reads only the answers Windows already keeps in its cache. Details: What AFKSecurity connects to and writes.
  • The report reads more calmly, in all seven languages. Hypotheses say what is possible instead of stating it as fact, words such as keylogger only appear when something of the kind was actually seen, and an internal check of the network cut rule stays in the log instead of the report.
  • During bursts of activity the log is written in one go, with the file kept open, instead of being opened and closed for every line. Nothing is held back in memory: a power cut still loses no line.
  • The installer now uses English when Windows is set to a language it does not offer. It used French.
  • After Release this machine's seat, the licence key is cleared from the screen.

Fixed

  • The protection service could slow down over a few hours when a program took the microphone, the webcam or the screen again every few seconds: each time added a new entry and a new line in the log. The same program on the same device now counts once, and the log mentions it once each time you leave or come back, with a reminder at most once an hour.
  • Components signed by Microsoft are no longer reported as suspicious: Microsoft Defender's own library and its definition updates, and the Edge updater opening a firewall port.
  • Three antivirus products (Huorong, Rising, then Microsoft Defender) flagged the 1.0.4 installer. The cause was on our side: the translation table, full of security terms, was stored as plain text inside the programs. It is now compressed, and 1.0.5 is not flagged.

1.0.4 2 October 2026

Decoy files explained and removable, a folder of your choice for exports, and the licence time remaining on the licence screen.

Changed

  • Decoy files are now placed only in your own folders: the root of Documents, the root of Pictures and the root of your user folder. Earlier versions could put some inside another application's folder, in Documents or in AppData. Those files are removed when 1.0.4 starts.
  • Settings has a new Decoy files section: what they are for, where each one is, and a button to remove them or put them back. Removing them is written to the log, so it cannot go unnoticed.
  • Saving the report, the log, the MITRE table or the incident file now asks you for a folder, instead of always using Documents.
  • The licence screen now has two lines: the days of use left without contacting the server (35 at most, the only number shown until now), and the licence time remaining, with its end or renewal date. The second line is filled in after the next daily licence check.
  • The window's display component (Microsoft WebView2) now starts with its background network services turned off: component updates, crash reports, translation and the other services a browser runs on its own. AFKSecurity's own connections are unchanged: the daily licence check, and the update check when you ask for it. Details: What AFKSecurity connects to and writes.
  • The report, the MITRE table and the incident file are now written in the language of the window. They were in French only.
  • Several messages in the window were reworded to be clearer. The Portuguese, Chinese and Japanese translations now use the same terms throughout.

Fixed

  • In Settings, the list of programs you can grant an exception to kept changing on its own and was hard to select from. It now lists every running program in alphabetical order, and only changes when you open the page or click Refresh the list. It is also shown in the window's colours instead of white.
  • Uninstalling now removes the decoy files too. Earlier versions left them behind.

1.0.3 24 September 2026

The whole interface now speaks your language, including the Proof tab, which still showed some text in French.

Fixed

  • The MITRE ATT&CK table in the Proof tab described what each sensor sees in French only. It is now translated into all seven languages.
  • Some journal lines and incident replays (new devices, files replaced in a protected folder, withdrawn permissions, trusted programs) showed a technical key instead of a sentence. They now read normally.
  • In German, Spanish, Portuguese, Chinese and Japanese, a few texts still used the old word for sensor. The wording is now the same everywhere.

1.0.2 23 September 2026

Stable memory over long uptimes, a simple status tab, and a Windows notification when AFKSecurity is waiting for your answer.

Fixed

  • The service's memory grew steadily for as long as the computer stayed on. Two sensors that read the Windows event log (firewall and startup entries) left part of each reading open, and Windows kept it in memory. Every reading is now closed, and memory stays flat. Detection is unchanged.
  • The sensors do less work on each cycle: several checks that ran many times per second no longer allocate memory to do it.

Added

  • A Status tab, now the first one: whether protection is active, and what, if anything, needs your attention. The detailed view is one click away.
  • When AFKSecurity asks whether an activity is yours, Windows shows a notification. Clicking it opens the window with the question.
  • Each section of the Report tab shows its first entries, with a Show more button for the rest.

Changed

  • “Don't ask me again for this program” is ticked by default when you answer “it's me”. The program is then remembered until you remove it in Settings, under Programs you allowed.
  • The interface says sensor where it used to say organ.

1.0.1 22 September 2026

Fewer false alarms and lower resource use on busy computers. AFKSecurity recognises trusted programs from the start and freezes a program only when files have actually been lost.

Changed

  • A program is frozen only when a real loss is detected: files renamed to an extension it never read, files overwritten in place, or one of your folders being emptied. A high rate of file writes is no longer enough on its own.
  • Web browsers, code editors, Windows and OneDrive are recognised as trusted programs from the first second. Recognition requires both the program name and a verified publisher signature. Their activity is still recorded in the journal, but they are not frozen. Windows tools commonly misused by attackers, such as PowerShell and the command prompt, are not included.
  • For the first three minutes after startup, AFKSecurity observes and records without freezing programs or cutting the network, unless files are actually being lost.

Fixed

  • Answering “it's me” now applies to the program for the whole session, including after it restarts.
  • On computers running several hundred programs, the substrate could run out of energy and remain in its critical state. Its energy budget now scales with the size of the machine.
  • The window refreshes fifteen times per second, and its drawing pauses while it is hidden.
  • The Host panel shows the processor and memory used by the AFKSecurity service.

1.0.0 18 September 2026 First release

First public release. A local security agent that watches how Windows behaves, freezes what has no business running, and writes a sealed journal you can read yourself.

What it does

  • Watches system behaviour with no signature database: files and decoys, persistence, devices, network, processes and windows, browser extensions.
  • Freezes a program and contains it through Windows firewall rules when two separate sensors agree that something is wrong, never on one alone.
  • Keeps a local journal sealed line by line with a SHA-256 chain, so that a missing line can be detected.
  • Writes a weekly AFK report: a summary of what it saw while you were away.
  • Publishes its MITRE ATT&CK mapping, including the techniques it does not cover.
  • Ships its bench folder: the test protocol, the dated measurements and the ledger of known limits, so you can replay them on your machine.
  • Speaks seven languages.

Licensing

  • 14-day trial, complete, no payment method and no account.
  • Online activation, then a daily check. The body of each request holds two fields: a fingerprint of the machine, and sometimes the licence key.
  • The licence is tied to the hardware, not to the installed system: reinstalling Windows finds it again on its own.
  • It keeps working offline for weeks at a time.
  • When a subscription or a trial ends, the software does not stop. It switches to witness mode: it keeps observing and reporting, and stops acting.

Updates

  • Nothing is downloaded or installed without you asking. What comes down is checked twice before it runs: its fingerprint against a manifest signed by the publisher, then its code signature against the copy already installed.
  • No version older than the one installed is ever accepted.

How to read this page

  • Added : something the software did not do before.
  • Changed : something it now does differently.
  • Fixed : something that was wrong.
  • Security : a fix that closes a hole. Install it the same day.

Versions are numbered major.minor.patch.

Share: Facebook · X · Reddit · LinkedIn