- Joined
- Jul 16, 2014
- Messages
- 8,253 (2.08/day)
- Location
- SE Michigan
System Name | Dumbass |
---|---|
Processor | AMD Ryzen 7800X3D |
Motherboard | ASUS TUF gaming B650 |
Cooling | Artic Liquid Freezer 2 - 420mm |
Memory | G.Skill Sniper 32gb DDR5 6000 |
Video Card(s) | GreenTeam 4070 ti super 16gb |
Storage | Samsung EVO 500gb & 1Tb, 2tb HDD, 500gb WD Black |
Display(s) | 1x Nixeus NX_EDG27, 2x Dell S2440L (16:9) |
Case | Phanteks Enthoo Primo w/8 140mm SP Fans |
Audio Device(s) | onboard (realtek?) - SPKRS:Logitech Z623 200w 2.1 |
Power Supply | Corsair HX1000i |
Mouse | Steeseries Esports Wireless |
Keyboard | Corsair K100 |
Software | windows 10 H |
Benchmark Scores | https://i.imgur.com/aoz3vWY.jpg?2 |
Yes, it would affect security, but I'm talking about doing this to a Windows install that I'm going to scrap which is sitting on a slave drive (or another partition) not the active Windows installation so this isn't an issue.
Ok still not sure what you want to do but, afaik, not all sub-folders, or parent folders, will have the same permission groups, i.e., not all will have TrustedInstaller or CREATOR OWNER attached. The Inheritance setting is per group, meaning, each individual group has an inheritance setting, one setting does not apply to all groups. (I think i said that right, lol)
I suppose, just a thought, that you could effectively, and completely, remove permission from M$, I've never done it, so not sure what happens with windows update but that would be interesting to see.
