@StartUpCommonDir -- internal logic

[CarlD]

How does @StartUpCommonDir identify the folder to which it points? On my system, it points to "C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup", while for another user who is testing my script, it points to "C:\Users\{USERNAME}\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup", even though the other directory also exists on his system. Can someone please explain the built-in logic that leads to these different results? Thanks in advance.

[argumentum]

I don't have your answer.

Exit MsgBox(0, @ScriptDir,  '@StartUpCommonDir: ' & @CR & @StartUpCommonDir & @CR & @CR & '@StartupDir: ' & @CR &  @StartupDir, 30)

but the above code runs fine on every Win10 so far. Would you have more details of the tester's OS ?

[CarlD]

3 minutes ago, argumentum said:

I don't have your answer.

Exit MsgBox(0, @ScriptDir,  '@StartUpCommonDir: ' & @CR & @StartUpCommonDir & @CR & @CR & '@StartupDir: ' & @CR &  @StartupDir, 30)

but the above code runs fine on every Win10 so far. Would you have more details of the tester's OS ?

I'll see if I can get some more details about his OS. And I'm not suggesting that @StartUpCommonDir ever points to a non-existent directory (clearly that would be a problem!) -- although in my tester's system @StartUpDir does not exist, which is why I modified the script to fall back to @StartUpCommonDir in that case. My question really relates to documenting my script. I could say, "If '{systemdrive}:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup' does not exist on your system, the file will be saved to the directory identified by AutoIt's @StartUpCommonDir macro", but that would not provide meaningful information for AutoIt-unaware users. I'd like to document the fallback directory more concretely -- hence my question.