Thanks. I'm not sure how that path ended up protected. One for me to try and figure out. Worked out last night that running the FSUIPC MSFS shortcut as admin seemed to pull it all together. At least now the .ini file exists and can be read. I'll stick to doing that, for now, until I can figure out what windows is doing. I have a standalone m.2 drive for MSFS. FSUIPC is installed in top-level directory there which shouldn't be protected like that. Now the .ini exists, and is being read even when I start up normally, I could just leave it and not get logs. I've had a few add-on crashes, though, which I think the .log file may help me narrow down. Thanks for your reply.