Some users may share a Mission Planner config.xml between machines or other users as a quick way to move quick-view / display settings. However, config.xml also contains <logdirectory> — an absolute path tied to the original user (e.g. C:\Users\<oldUser>\OneDrive\Documents\Mission Planner\logs).
On the new PC, that path often can’t be accessed — it points to another user’s folder, or to another user’s OneDrive. MP then fails to create .tlog for the session. A message box does pop up, but it only says something like “log creation failed” without naming the real cause. The underlying UnauthorizedAccessException and the offending path are not shown, so the operator has no clue where to look.
Suggested fix
In the log-creation path (around MainV2.cs Directory.CreateDirectory(Settings.Instance.LogDir)), include the actual exception message and the resolved path in the dialog, plus a one-liner like “Please check the Log Directory setting under Config → Planner tab.”
Even just surfacing ex.Message and the path, with a pointer to the right settings page, would save users a lot of guesswork.