I am curious what spoiled
@LightWave's system. Actually, I do not know which Windows policy could do something like that. Hard_Configurator does not touch system files - all files in C:\Windows, C:\Program Files, C:\Program Files (x86) are whitelisted and this cannot be changed from Hard_Configurator. First, I thought that maybe Startup Sentinel blocked something, but I never heard about such problem, too.
The only (rare) possibilities could be related to:
* blocking Windows Script Host, if some hardware driver needed a script to load;
* SRP blocking something in the hardware directory in the User Space (Intel, AMD, etc.) that was needed to load the driver.
If so, Widows Script Host should be enabled or in the second case, the hardware directory should be whitelisted by path (whitelisting by hash may be not sufficient after software update).
Thanks
@LightWave for your help, I will add a warning in the installation guide, to make system restore point before running Hard_Configurator.