From Hard_Configurator Tools
- Dec 23, 2014
It has never been for Windows 10 only. As you can see in the help files it is for Windows Vista, 7, and 8+.H_C is for Win 10 only ?
because I'm on Win 11
Ok it is an another french NAS forum which someone said me that...It has never been for Windows 10 only. As you can see in the help files it is for Windows Vista, 7, and 8+.
Please read the "What_is_new.txt" (it is displayed after installing H_C) for changelog details.
There is no difference in how the H_C works on Windows 10 and 11.
Why ask on forums? Are the H_C website info, H_C help files and manual as bad?Ok it is an another french NAS forum which someone said me that...
No, I ask on NAS forum why I don't access at my NAS. And, I have "disable SMB" on "???" H_C settings. And when I was found that, I said that, why. And someone, say me that H_C its only create for Win 10 and that the reason why I demand it there.
I put on ON1 and the issue is resolve.
Yes it is resolve. Because I have put on ON1 and only SMB 2 and 3 are active...Is your NAS problem solved?
If you can see "????" setting then it is a non-standard setting that was not set by the H_C. The H_C just read it from the registry but could not recognize it as the standard one. The H_C Recommended Settings do not change the SMB settings.
You have three options in H_C related to SMB. Start from SMB123 and restart the computer if NAS works then OK. If not then use SMB1 setting. If both do not work then use the OFF setting. If NAS does not work with the OFF setting then the issue is not related to the H_C.
Anyway, you can also Switch OFF the H_C protection (it is simple), restart the computer, and see if NAS works or not. If not, then you have a problem that can be solved on NAS forums.
All SMB protocols can be vulnerable in some way, but SMB 1.0 is the most attacked. Anyway, If your NAS uses SMB 2&3, then these protocols must be enabled.Yes it is resolve. Because I have put on ON1 and only SMB 2 and 3 are active...
Because SMB 1.0 is bad for the ransomware risk...
Do you think that that feature will require a fresh install even in the final version? I doubt that many people will take advantage of it if it requires a fresh install.I have just finished a quick test of Smart App Control on Windows 11 (Insider). It is much more useful than I thought.
After downloading 30 fresh applications from Softpedia it gave slightly fewer false positives compared to Norton 360, Windows SmartScreen, or Defender ASR prevalence rule.
I compiled a fresh & unsigned version of ConfigureDefender to see what will happen:
View attachment 267619
In my test, the digitally signed applications were installed & run without issues (except for two events). A few installations were blocked (some were partially blocked).:
View attachment 267621
The cons (for some people) can be that the blocked installer or application cannot be allowed/whitelisted/excluded by the user. It can be only submitted to Microsoft as a false positive in the Smart App Control category. For now, Smart App Control cannot be temporarily turned off.
It would be interesting to test Defender + Smart App Control in Malware Hub.
It is early-stage in Insider, so everything is possible. The current version is not practical.Do you think that that feature will require a fresh install even in the final version? I doubt that many people will take advantage of it if it requires a fresh install.
I see in the article below:
it mentions to include psm1 as a designated file type when using SRP to enforce PowerShell CLM, but in the H_C file types I don't see that one: