The (A) and (B) are not Hard_Configurator options, but two groups of cases when SmartScreen (in Windows Explorer) will fail. Hard_Configurator (Run As SmartScreen utility) covers only the (A) group. The (B) group is related to special kind of EXE launchers (runas.exe, AdvancedRun, RunAsSystem.exe). The Launcher executable can be checked by SmartScreen but the launched application cannot.
Sorry for not being explicit enough. What I meant by (A) and (B) are these options from Hard Configurator manual under "Run As SmartScreen" section:
"
(A) Keep the 'Administrator' setting when SRP are activated. If so, the users can safely:
1. Run programs (with a mouse click or pressing ENTER button) which have been already installed in the System Space or put on the Whitelist.
2. Open the media files, documents, and other file types, which are not on the 'Designated File Types' list.
3. Safely install new programs from the User Space, using 'Run As SmartScreen' option in Explorer context menu (only EXE and MSI files). This option additionally forces the file to ask for execution with Administrative Rights.
(B) Advanced users can apply the below settings with Default Deny SRP :
Apply recommended settings, and next change <Run As SmartScreen> --> 'Standard User', <Hide 'Run As Administrator> --> 'OFF', as an alternative solution. Then, 'Run By SmartScreen' + SRP can serve as a second opinion scanner for executables located in the User Space. Files with
dangerous extensions are blocked, but media, documents, photos, etc. are allowed.
In the (A) solution files (EXE and MSI) are checked by SmartScreen, and blocked when recognized as not safe, but allowed to execute with Administrative
Rights, when recognized as safe.
In the (B) solution files (EXE, MSI, JSE, VBE) are checked by SmartScreen, and blocked (never executed in the User Space). Other files supported by
SmartScreen filter (BAT, CMD, COM, CPL, DLL, OCX, PIF, SCR) are blocked by SRP (included in ‘Designated File Types’ list). Documents, photos,
media files, and generally, files with not dangerous extensions, are allowed to open. One has to use 'Run as administrator' option in Explorer context menu
to run the EXE and MSI files. ‘Run By SmartScreen’ does not block extensions supported by SmartScreen filter (BAT, CMD, COM, CPL, DLL, EXE, JSE, MSI, OCX, PIF, SCR and VBE), but blocks other dangerous extensions independently of SRP: ADP, ADE, BAS, CHM, CRT, HLP, HTA, INF, INS,
ISP, JAR, JS, MDB, MDE, MSC, MSP, MST, PCD, PS1, REG, SCT, SHS, VB, VBS, WS, WSC, WSF, WSH."
So, to confirm, I think you said there is no way for me to configure Windows settings/registry to simulate the above settings, right? This is a special custom utility that is part of Hard Configurator, right?
This is the way how SRP Designated File Types list + Default Security Level = Disallowed, work for BAT, CMD, CPL, MSC files.
The user can Run as administrator those files when;
- BAT, CMD, CPL, MSC extensions are removed from DFT list.
or
- SRP Default Security Level is not set to Disallowed
The second is adopted in Hard_Configurator recommended settings (Default Security Level is set to Basic User).
In your settings, the BAT and CMD extensions can be safely removed from DFT list, because CMD host is under extended protection when Default Security Level = Dissallowed. So, they will be still blocked as standard user, but allowed to Run as administrator. That is not true for CPL and MSC files, because there are no extended SRP protections for them.
If I have "Default Security Level = Dissallowed" AND if I leave BAT and CMD on the DFT list, would any windows or software upgrades run into any issues?
(I prefer leaving them in DFT if it does not hurt - only because other guides seem to be suggesting such setup, and I don't feel confident enough in this area; so would prefer more protections settings to be ON for now
IF it does not cause instability)
Thank you, again!