New
#1
What are the risks of Taking Ownership of System32?
Hi guys, I am new around here, but I was hoping you could lend me a hand.
I think I've been stupid.
While trying to fix an issue with a simulator (FSX) that involved adding a .dll file to system 32, a user said in a guide to fix said issue to paste the .dll file into system 32, but to do this, you would need to take ownership of the system 32 folder. Which I did, and the .dll was pasted successfully. However stupidly I didn't do any research until after the CMD/DOS window did the whole ownership process. Then I read in this forum that I should NOT take ownership of system32.
I don't know if I screwed up, and if there is any way to revert it? I mean.. nothing happened, and my system is running fine. Multiple people who also use FSX have done the ownership of system32, and none have reported problems, so.. I'm just a little scared as to what I have possibly done.