This is happening repeatedly using Windows 10 Pro and while at the moment it's only affecting games installations (that I know of) it perturbs me that I don't understand how it's happening.
Three times now when installing Skyrim from Steam, the directories are created such that they are undeletable and when I try to see their access information in the Security tab of their Properties I get an error telling me I don't have read access to allow me to see this info; and even more oddly a .EXE created dynamically during a Morrowind modification job had the same problem and couldn't be executed, the game didn't come from Steam and none if this installtion's directories had suffered.
Clearly these file system objects have been created with incorrect ownership but on the face of it they're simply 'userland' processes that are creating them, there's nothing involved that I can see as being a 'system' process which would account for it: I don't see ant DRM reasons why Steam would do this, for example.
The only way I have found to fix things is to boot to a Recovery Console and use TAKEOWN /F .. /A.
Can anyone shed some light on what's going on or maybe something I can do within Windows itself using some admin tool I'm not aware of to avoid the need to reboot to recovery to do so?
Cheers
Three times now when installing Skyrim from Steam, the directories are created such that they are undeletable and when I try to see their access information in the Security tab of their Properties I get an error telling me I don't have read access to allow me to see this info; and even more oddly a .EXE created dynamically during a Morrowind modification job had the same problem and couldn't be executed, the game didn't come from Steam and none if this installtion's directories had suffered.
Clearly these file system objects have been created with incorrect ownership but on the face of it they're simply 'userland' processes that are creating them, there's nothing involved that I can see as being a 'system' process which would account for it: I don't see ant DRM reasons why Steam would do this, for example.
The only way I have found to fix things is to boot to a Recovery Console and use TAKEOWN /F .. /A.
Can anyone shed some light on what's going on or maybe something I can do within Windows itself using some admin tool I'm not aware of to avoid the need to reboot to recovery to do so?
Cheers