![]() |
|
|
|
#1
|
|||
|
|||
|
Imagine an app running with admin though or elevated, and it checks permission to write its data in c:\windows\system32. If it fails access check then it writes to the user profile folder. Such a driver would start to change behavior of normally not possible scenarios. A small point maybe but some apps are coded this way.
The only thing I can think of is that the ownership and ACL changes both need to be recursively applied and hence dangerously destructive. But strange Win7 can access it. TrustedInstaller has always been enough for me unless an app was doing some special permission hacks. Especially surprising for command prompt as explorer has it's own special settings. |
|
#2
|
|||
|
|||
|
hmm... indeed that particular scenario would get broken.
About C:\Program Files\WindowsApps get a VM and try it for yourself, you will be surprised how nasty windows is with regard to some of the sub-folders in this location. iirc. with System/TrustedInstaller permissions you at least can create new files but no chance modifying existing once. I think windows 10 is using here some additional flags/attributes to protect these locations. |
| The Following User Says Thank You to DavidXanatos For This Useful Post: | ||
chants (02-23-2020) | ||
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Driver Signing on x64 Windows | _MAX_ | x64 OS | 7 | 10-22-2012 15:47 |
| WDF (Windows Driver Foundation) | vodu | General Discussion | 2 | 06-29-2005 06:06 |
| Help - Windows Device Driver Programming | psychedelic_fur | General Discussion | 7 | 06-29-2004 22:27 |
| Windows 2000 Device Driver Book + Inside Windows 2000 at FTP | dynio | General Discussion | 16 | 09-19-2003 23:21 |