You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For those looking for a capsblock.exe (binary release), this executable should be available in the release package generated and published in this project's releases page. Releases are stored inside a capsblock-portable.zip archive, along with other helpful support scripts.
There is no executable in the archive. What's up?
There are most likely two scenarios why an executable is missing from the downloaded archive:
The systems security software automatically removes unauthorized executables from archives (due to policy/configuration).
Due to the nature of this application and its use of Window's low-level keyboard hook (WH_KEYBOARD_LL), there may be a higher chance of a false-positive detection from security software. In such a state, the executable is most likely automatically removed or quarantined.
When a release is made through GitHub's actions, the resulting package is then manually scanned by Microsoft Defender to see if a false-positive detection exists. In the event that there is an issue, a submission is made to Microsoft Security Intelligence's group for analysis/approval.
If a new release results in a false-positive detection, it may take a few days for security definitions to update/propagate. Users are recommended to wait/retry until definition updates are available.
The text was updated successfully, but these errors were encountered:
For those looking for a
capsblock.exe
(binary release), this executable should be available in the release package generated and published in this project's releases page. Releases are stored inside acapsblock-portable.zip
archive, along with other helpful support scripts.There is no executable in the archive. What's up?
There are most likely two scenarios why an executable is missing from the downloaded archive:
WH_KEYBOARD_LL
), there may be a higher chance of a false-positive detection from security software. In such a state, the executable is most likely automatically removed or quarantined.When a release is made through GitHub's actions, the resulting package is then manually scanned by Microsoft Defender to see if a false-positive detection exists. In the event that there is an issue, a submission is made to Microsoft Security Intelligence's group for analysis/approval.
If a new release results in a false-positive detection, it may take a few days for security definitions to update/propagate. Users are recommended to wait/retry until definition updates are available.
The text was updated successfully, but these errors were encountered: