Hard_Configurator - Windows Hardening Configurator

security123 said:
I guess upgrade from latest beta is fine?
Click to expand...
Yes, the stable version 6.0.0.0 will contain some updated executables, and the extended certificate valid to June 2021. But this stable version will be functionally similar to beta 5.1.1.1.
 
  • Like
  • Thanks
Reactions: Tiny, simmerskool, mkoundo and 6 others
Latest H_C beta use outdated Autoruns: 13.82.0.0 from February 13, 2018
while it already exist 13.96

Fixes since that release:
13.90
Autoruns now includes Runonce*\Depend entries, adds GPO logon and logoff locations, and fixes a bug in WMI path parsing.
13.95
This Autoruns updates adds support for redirected user Shell folders.
For 13.96 no changelog exist yet

Same also for FullEventLogView: 1.26 is included but latest one is 1.52
 
  • Like
  • +Reputation
Reactions: plat, silversurfer, Protomartyr and 4 others
security123 said:
Latest H_C beta use outdated Autoruns: 13.82.0.0 from February 13, 2018
while it already exist 13.96

Fixes since that release:
13.90
Autoruns now includes Runonce*\Depend entries, adds GPO logon and logoff locations, and fixes a bug in WMI path parsing.
13.95
This Autoruns updates adds support for redirected user Shell folders.
For 13.96 no changelog exist yet

Same also for FullEventLogView: 1.26 is included but latest one is 1.52
Click to expand...
I rarely change Autoruns version because the H_C has a special module that works with the older version and may work or not with the new version. The new features are not important for H_C, because the legal applications do no use as many autorun keys as malware. The newest FullEventLogView has some bugs and does not filter properly all events required by H_C. But I plan to update these tools this year.
 
  • Like
  • +Reputation
  • Thanks
Reactions: simmerskool, South Park, mkoundo and 7 others
shmu26 said:
Hi Andy, I installed Windows 7 yesterday, and then H_C 5.0.0.0.
I put it at recommended settings.
There are items that I pinned to the regular Windows 7 start menu. Those shortcuts are all blocked. Whitelisting them doesn't work. Even my shortcut to H_C is blocked...
Click to expand...
Did you log OFF the account?
 
  • Like
Reactions: Protomartyr, harlan4096 and shmu26
Capture.PNG
 
  • Like
Reactions: simmerskool, Protomartyr, oldschool and 2 others
Andy Ful said:
Thanks. Could you please use <Tools> <Restore Windows Defaults> to remove SRP and next run H_C again?
Click to expand...
I restored windows default, rebooted, ran H_C, logged off, and now it's the same as before. When I click on the H_C shortcut that I pinned to the Win7 start menu, I get "This program is blocked by group policy"
 
  • Like
Reactions: simmerskool, Protomartyr, oldschool and 2 others
shmu26 said:
I restored windows default, rebooted, ran H_C, logged off, and now it's the same as before. When I click on the H_C shortcut that I pinned to the Windows 7 start menu, I get "This program is blocked by group policy"
Click to expand...
Do the standard shortcuts (made by H_C) work well?
You can whitelist the nonstandard shortcut locations by using:
<Whitelist By Path> <Add Path*Wildcards> and paste the full path of the shortcut.
Other whitelisting methods will always whitelist the target application which can be run by the shortcut, but the shortcut will not be whitelisted.
 
Last edited:
  • Like
Reactions: simmerskool, Protomartyr, oldschool and 2 others
Andy Ful said:
Do the standard shortcuts (made by H_C) work well?
You can whitelist the nonstandard shortcut locations by using:
<Whitelist By Path> <Add Path*Wildcards> and paste the full path of the shortcut.
Other whitelisting methods will always whitelist the target application which can be run by the shortcut, but the shortcut will not be whitelisted.
Click to expand...
Thanks, that works :)
 
  • Like
Reactions: South Park, simmerskool, Back3 and 6 others

You may also like...