Something is definitely wrong but, at the moment I have no idea what. I have just had two other reports of a similar situation in AIFP. But, the version of SAMM you are using is almost a year old and in AIFP, this appears to be a recent and sudden problem. I'm suspicious a recent Windows update has changed something that AIFP and SAMM depend upon. (As I noted in an earlier post, SAMM and AIFP use the same code to locate aircraft.) You noted earlier you weren't experiencing such problems with ADE. I don't believe ADE attempts to locate aircraft.
I note the very limited information in the directory tree. Clearly, that's not all of your C: drive - which brings me back to a windows update.
But, I am not experiencing any such problems - and I have all the windows updates for North America.
I'll keep you updated as things (hopefully) progress.
Which they already have. Just now I tried again and with FSX and FSX:SE only, I get the same error message, I didn't get that message as late as this afternoon.
It's late here. I'll investigate further tomorrow. This definitely is not due to a recent change in software, The latest development release of SAMM is nearly 6 months old