Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Security
Security Statistics and Reports
Security vs. Ransomware: 34 Solutions in the Advanced Threat Protection Test
Message
<blockquote data-quote="ForgottenSeer 95367" data-source="post: 1000350"><p>Blocking these processes on the basis that they are Microsoft digitally signed will result in a "black screen system":</p><ul> <li data-xf-list-type="ul">system (ntoskernel.exe)</li> <li data-xf-list-type="ul">smss.exe</li> <li data-xf-list-type="ul">winnit.exe</li> <li data-xf-list-type="ul">services.exe</li> <li data-xf-list-type="ul">csrss.exe</li> </ul><p>[ATTACH=full]268747[/ATTACH]</p><p></p><p>Whatever you are using to block processes might not apply its block rules early enough in the system boot sequence to quash processes such as smss.exe, csrss.exe and services.exe. (NOTE: winlogon.exe is not digitally signed). Consequently, a partially bootable system might still happen even if you are blocking critical Windows processes that are signed.</p><p></p><p>Additionally, if you test in a virtual machine, you might get unexpected results whereby system boots despite blocking critical Microsoft signed processes.</p><p></p><p>In your testing, you can try a single "catch-all" block rule that will block everything unsigned and unsigned:</p><p></p><p>block= *</p></blockquote><p></p>
[QUOTE="ForgottenSeer 95367, post: 1000350"] Blocking these processes on the basis that they are Microsoft digitally signed will result in a "black screen system": [LIST] [*]system (ntoskernel.exe) [*]smss.exe [*]winnit.exe [*]services.exe [*]csrss.exe [/LIST] [ATTACH type="full" alt="1661432896574.png"]268747[/ATTACH] Whatever you are using to block processes might not apply its block rules early enough in the system boot sequence to quash processes such as smss.exe, csrss.exe and services.exe. (NOTE: winlogon.exe is not digitally signed). Consequently, a partially bootable system might still happen even if you are blocking critical Windows processes that are signed. Additionally, if you test in a virtual machine, you might get unexpected results whereby system boots despite blocking critical Microsoft signed processes. In your testing, you can try a single "catch-all" block rule that will block everything unsigned and unsigned: block= * [/QUOTE]
Insert quotes…
Verification
Post reply
Top