Over the past cyber decades, I've always been wary of "in-app" updating for security products, but I've used AppCheck's home dashboard "Update" or it's About AppCheck "Check" without issue for over a year now rather than running the setup over an existing install. I'll continue to run update setups over my GlassWire and SpyShelter installs, though there's no choice in the latter AFAIK. CheckMal's devotion to updating and improving its powerful and IMHO unequaled stand-alone product is to be lauded. Especially in light of the fact that AppCheck's most important and effective protection features are... free. Anyhow, here's the update log for 3.1.31.2: Interesting about that Chrome thing; if I used it I would probably care. Update changelogs and histories can be found at Chackmal's arcane URL: https://www.checkmal.com/notice/read/362/ and its less-specific https://www.checkmal.com/notice// Cheers.
Yes, and they also have a YouTube channel where they showcase AppCheck being able to block the newest ransomware samples, not a lot of security vendors do this nowadays. I also wonder why they removed Chrome from the anti-exploit feature, and I wonder if now ALL Chromium browsers aren't protected anymore? I would however like to get the old GUI back for the AppCheck Free version, from what I understood, the AppCheck Pro version still has the old GUI.
Thanks for posting this update. I have a machine that I can't seem bring Defender back to life due to "org policies" being set...that I never set!
Nineteen bullet points. One big graphic. Read all about it here: https://www.checkmal.com/notice/read/362/
Version 3.1.33.8 (22. Aug. 2023. 01:20 UTC) Fixed a mouse event bug in the Shelter and Automatic backup option. Adjusted the width of MD5 and SubType columns in the Detection Log and Quarantine. Fixed a bug that prevented deleting history files when auto backing up to a specific filename. Fixed an issue where certain files located on network drives could not be opened. ※ This version does not support automatic updates in the free version of AppCheck. Source: https://www.checkmal.com/notice/read/362/
Nasty technical details: Version 3.1.34.2 (18. Oct. 2023. 01:30 UTC) Improved an issue that caused applications to run slower after installing AppCheck. Fixed an error when saving certain applications. Enhanced AppCheck self-protection.
Nasty technical details: Version 3.1.35.1 (20. Dec. 2023. 01:00 UTC) Fixed a security vulnerability issue.
v3.1.36.2 (13. Feb. 2024) h t t p s://w w w.checkmal.com/download/appcheckv3.0/AppCheckSetup.exe h t t p s://w w w.checkmal.com/notice/read/362/
A rather extensive update. Product development and transparent support is a priority over there at CheckMal. Version 3.1.36.2 (13. Feb. 2024. 05:00 UTC) Improved Ransom Guard rollback. Improved Ghost detection. Improved Smart detection. Enhanced AppCheck self-protection. Deleted the AppCheck cleaner DB from the AppCheck install/update file. Fixed a delay in sending faxes due to a network drive name lookup issue. Fixed an issue with IPv6 addresses not being displayed in the "SMB Allow/Block List - Blocked Address List" option. Improved various automatic backup options. Added a confirmation prompt when deleting items added to automatic backup, exception setting, and the SMB allow/block list. Fixed an issue with event logs being logged related to unchanged automatic backup and the SMB allow/block list option. (CMS) Fixed an issue that prevented AppCheck full screen from displaying properly in dual monitor environments. Fixed the wording of the license information. Fixed an alignment issue with the wording displayed in the SMB allow/block list. (Japanese) Fixed the link to purchase page in the license expiration window. Improved password requirements for password lock settings. Fixed an issue where unlocking from full screen would dismiss the maximize screen. Fixed an issue where some option settings could be changed after enable password lock. Fixed an issue that allowed searching with invalid time period settings for detection logs, quarantine, and event logs. Fixed an issue that prevented policy synchronization when turning off the "Alert when execution is blocked" policy. (CMS)
Yeah, I've noticed it a few days ago, but forgot to post it here. Any idea why they removed the Cleaner from version 2?
v3.1.36.2, AppCheckS.exe creates a "allow UDP incoming" rule in Windows Firewall by itself. Why such an "improvement"? There was no such behavior in the previous v3.1.35.1.
I'm not seeing an inbound appchecks.exe under application package in my Windows Firewall. (Or outbound, for that matter.) For the past 30 days, appchecks.exe shows nada UDP in my network log. This includes the previous and new versions and during the update process. What is the inbound rule name? Local UDP port? Have you logged a remote IP? I'm on Win10. You? I'm wanting to look into this further. Thanks. Yeah. We'll get right on that!
Thanks. That's unfortunate for you. In the meantime, I checked two other WIn10 systems I run, one AppCheck Pro one Free and no UDP for appchecks.exe. As well for appcheck.exe and appcheckupdate.exe. I can block the service it I want to as demonstrated in this composite screenshot. But I don't block it. GlassWire traffic data for the record. And my actual Windows Firewall showing inbound rules (outbound is the same). I'm just gonna leave it that I'm glad it's not happening over here and otherwise have lost interest in this. Cheers.
BTW, does this newest version still have the new GUI similar to AppCheck Pro? I prefer the old GUI, it looked way better. Probably because it was not so good? I never understood what it exactly did. But now I'm just guessing.
You probably mean that AppCheck can't use DirectStorage and not that AppCheck disable it instead? DS works better with Win 11 anyway (I am still on 10 tho). Not that I am currently using AppCheck. I have Kaspersky Free. On Win 11 one can run the "fsutil bypassIo state c:\" to check if the AV drivers support it. Like in this topic: https://forums.malwarebytes.com/topic/285061-malwarebytes-bypassio-support/ Btw, not supporting the bypassIo doesn't mean DS is completely disabled but not working on its max capabilities. Maybe if AppCheck doesn't support bypassIo one can ask the developer to add support in the next releases?
I mean that AppCheck doesn't support bypassIo and as a result directstorage not supported due to their driver. I believe if windows find an incompatible driver it disables it globally.
