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
ConfigureDefender utility for Windows 10/11
Message
<blockquote data-quote="Andy Ful" data-source="post: 882929" data-attributes="member: 32260"><p>When using the standalone version of ConfigureDefender - it works slightly different from the ConfigureDefender executable included in H_C.</p><p>Standalone CD = wrapper + CD 64-bit + CD 32-bit</p><p></p><p>If one uses CD 64-bit or CD 32-bit without a wrapper (like in H_C), then there is no issue, because it always runs from a single location (one entry in notification area cache).</p><p>The issue is related to the wrapper which runs CD (32-bi or 64-bit) in a random folder (for security reasons).</p><p>When the executable uses notification area in the system tray, then Windows adds new entries if they have different paths - that is a case of standalone CD (random paths are usually different).</p><p>I fixed the issue by removing the ability to add the icon to the notification area for CD 32-bit and CD-64-bit.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 882929, member: 32260"] When using the standalone version of ConfigureDefender - it works slightly different from the ConfigureDefender executable included in H_C. Standalone CD = wrapper + CD 64-bit + CD 32-bit If one uses CD 64-bit or CD 32-bit without a wrapper (like in H_C), then there is no issue, because it always runs from a single location (one entry in notification area cache). The issue is related to the wrapper which runs CD (32-bi or 64-bit) in a random folder (for security reasons). When the executable uses notification area in the system tray, then Windows adds new entries if they have different paths - that is a case of standalone CD (random paths are usually different). I fixed the issue by removing the ability to add the icon to the notification area for CD 32-bit and CD-64-bit. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
