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: 770870" data-attributes="member: 32260"><p>Did I really write "This image is wrapped and uses unwrapped imaged"????<img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite124" alt=":love:" title="Love :love:" loading="lazy" data-shortname=":love:" /></p><p>It is simple. Developers can hide one or more applications inside another program (wrapper). In the case of the <span style="color: rgb(41, 105, 176)"><strong>wrapped procexp.exe</strong></span>, it contains two applications for 32-bit and 64-bit versions of Windows. If you are using 32-bit Windows, then only 32-bit application will be extracted into Temp folder and executed. If you are using 64-bit Windows, then 64-bit application will be extracted into Temp folder and executed. Sysinternals suite usually has two Process Explorer applications:</p><ol> <li data-xf-list-type="ol">procexp.exe - wrapped (can be run both on 32-bit and 64-bit Windows).</li> <li data-xf-list-type="ol">procexp64.exe - unwrapped for 64-bit Windows only.</li> </ol><p>------------------------------------------------------------------------------------------------------------------------------------------------------------------------</p><p>In Hard_Configurator the Autoruns program is used only for:</p><ol> <li data-xf-list-type="ol"><strong><span style="color: rgb(184, 49, 47)">Whitelisting</span></strong> applications and scripts from the <span style="color: rgb(184, 49, 47)"><strong>Userspace</strong></span> which can start with Windows.</li> <li data-xf-list-type="ol"><strong><span style="color: rgb(0, 168, 133)">Viewing</span></strong> scripts from <strong><span style="color: rgb(0, 168, 133)">all locations</span></strong>, which can start with Windows.</li> </ol><p>The second can be useful when the user wants to block the scripts completely in all locations, for example by blocking script interpreters or when <Disable Win. Script Host> = ON .</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 770870, member: 32260"] Did I really write "This image is wrapped and uses unwrapped imaged"????:love: It is simple. Developers can hide one or more applications inside another program (wrapper). In the case of the [COLOR=rgb(41, 105, 176)][B]wrapped procexp.exe[/B][/COLOR], it contains two applications for 32-bit and 64-bit versions of Windows. If you are using 32-bit Windows, then only 32-bit application will be extracted into Temp folder and executed. If you are using 64-bit Windows, then 64-bit application will be extracted into Temp folder and executed. Sysinternals suite usually has two Process Explorer applications: [LIST=1] [*]procexp.exe - wrapped (can be run both on 32-bit and 64-bit Windows). [*]procexp64.exe - unwrapped for 64-bit Windows only. [/LIST] ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ In Hard_Configurator the Autoruns program is used only for: [LIST=1] [*][B][COLOR=rgb(184, 49, 47)]Whitelisting[/COLOR][/B] applications and scripts from the [COLOR=rgb(184, 49, 47)][B]Userspace[/B][/COLOR] which can start with Windows. [*][B][COLOR=rgb(0, 168, 133)]Viewing[/COLOR][/B] scripts from [B][COLOR=rgb(0, 168, 133)]all locations[/COLOR][/B], which can start with Windows. [/LIST] The second can be useful when the user wants to block the scripts completely in all locations, for example by blocking script interpreters or when <Disable Win. Script Host> = ON . [/QUOTE]
Insert quotes…
Verification
Post reply
Top