locked them for everyone. I wish your program would do that instead.
My program actually does that on the repair file permissions.
I found out what is happening.
In v2.11 the repair program only asks for 1 privilege
'Call BeginSetPrivilege
Call LoadPrivilege(SE_DEBUG_NAME)
What I did in v2.2.0 is I add more so the program would have access to more things that normally it wouldnt, just like my reg backup does.
'Call BeginSetPrivilege
Call LoadPrivilege(SE_DEBUG_NAME)
Call LoadPrivilege(SE_TAKE_OWNERSHIP_NAME)
Call LoadPrivilege(SE_RESTORE_NAME)
Call LoadPrivilege(SE_BACKUP_NAME)
So the new backup privilege is letting the program have access to folders that are normally blocked (Because backup programs still need to back those up). And every cmd.exe window the program creates gets the same access. So when it hits (for example)
"C:\Users\Shane\Local Settings" (This is normally denied)
If you look at the permissions for that folder you will see everyone is set to deny. Well the program gets allowed with the backup privilege. So the repair wmi window gets to look in there and then gets into a loop and why you see the problem.
Having the program be able to access more folders and settings is a good thing and can help repairs work better on machines, the key here is for me to change the repair wmi so that it skips those locations in the user profiles
So your machine is ok, it was a new change I made and the side effect I didnt see happening
Shane