- Mar 29, 2018
- 7,595
I did this to restore defaults on a pc so I could use a program that needed a script (checking for specter/meltdown patches). Everything seemed fine until I could no longer open ConfigureDefender. I don’t know what setting it changed, but it was not changed to the value it was originally set at. I’m a bit wary of Syshardener now. I used the default values plus PowerShell constrained language. I was just surprised that restoring defaults broke CD. I reimaged and just cranked up OSArmor for now.
Do you use only Admin account or do you also have an SUA? As @shmu26 said, you would have to restore defaults in all accounts for SysHardener. Oh well, at least you were able to re-image. I learned it is best not to use certain apps or features if I am uncertain of the consequences.