Can't edit aircraft config files inside P3D folder

[Midnight Music 252]

I'm new to Windows 10 and just a got new rig with W10 Pro on it. I installed P3D V4.2  as administrator and PMDG as administrator, however when I try to edit the PMDG aircraft configuration file inside the P3D folder, it says I am not allowed and must contact the administrator. (I am the administrator). Now if I drag the file to the desktop I can edit it there, save it and put it back into the P3D folder. What am I doing wrong? Any suggestions will be greatly appreciated.

 

Edited February 23, 2018 by Midnight Music

[Guest JustanotherPilot]

Sounds like you don't have full Admin rights, right click on the cfg file, ->properties ->security. If you have permissions to edit this file there should be a tick next to modify, if not, then edit to get permissions.

Edited February 23, 2018 by JustanotherPilot

[Bob Scott 7,743]

If you installed to the default folder, or to any other folder named Program Files*, I'd suggest you stop now, uninstall, and reinstall P3D to a folder with a different name.  The problems you are seeing are really just the tip of the iceberg when it comes to how Windows exerts a special (and often disruptive) kind of control over files located in a "Program Files*" folder and its subfolders.

Regards

 

[Midnight Music 252]

I do have full administrative rights, but it seems to make no difference, specifically in P3D. Elsewhere, not a problem. The idea of installing P3D V4.2 in a separate folder is intriguing, but so many addons rely on the default LM installation to work properly. I'll keep experimenting.

[bobbyjack 61]

So, I forget what they call it, but W10 has a higher Admin account than the one we all use. It's part of the security system. I think there was a thread here earlier about it. In the meantime. You can Google it. if you are the only one who uses your computer, you might consider turning off UAC. It doesn't really do what you think it does, and often gets in the way.

[Midnight Music 252]

I do have UAC off. I've devised a simple work around method. I drag the aircraft cfg to the desktop, edit it, save it and put it back in the original folder. Works fine that way.