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
Software
Security Apps
Hard_Configurator Tools
Hard_Configurator - Windows Hardening Configurator
Message
<blockquote data-quote="Andy Ful" data-source="post: 580089" data-attributes="member: 32260"><p>I am curious what spoiled [USER=58002]@LightWave[/USER]'s system. Actually, I do not know which Windows policy could do something like that. Hard_Configurator does not touch system files - all files in C:\Windows, C:\Program Files, C:\Program Files (x86) are whitelisted and this cannot be changed from Hard_Configurator. First, I thought that maybe Startup Sentinel blocked something, but I never heard about such problem, too.</p><p>The only (rare) possibilities could be related to:</p><p>* blocking Windows Script Host, if some hardware driver needed a script to load;</p><p>* SRP blocking something in the hardware directory in the User Space (Intel, AMD, etc.) that was needed to load the driver.</p><p></p><p>If so, Widows Script Host should be enabled or in the second case, the hardware directory should be whitelisted by path (whitelisting by hash may be not sufficient after software update).</p><p>Thanks [USER=58002]@LightWave[/USER] for your help, I will add a warning in the installation guide, to make system restore point before running Hard_Configurator.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 580089, member: 32260"] I am curious what spoiled [USER=58002]@LightWave[/USER]'s system. Actually, I do not know which Windows policy could do something like that. Hard_Configurator does not touch system files - all files in C:\Windows, C:\Program Files, C:\Program Files (x86) are whitelisted and this cannot be changed from Hard_Configurator. First, I thought that maybe Startup Sentinel blocked something, but I never heard about such problem, too. The only (rare) possibilities could be related to: * blocking Windows Script Host, if some hardware driver needed a script to load; * SRP blocking something in the hardware directory in the User Space (Intel, AMD, etc.) that was needed to load the driver. If so, Widows Script Host should be enabled or in the second case, the hardware directory should be whitelisted by path (whitelisting by hash may be not sufficient after software update). Thanks [USER=58002]@LightWave[/USER] for your help, I will add a warning in the installation guide, to make system restore point before running Hard_Configurator. [/QUOTE]
Insert quotes…
Verification
Post reply
Top