Starting Office 365 apps?

#1
Although I have ExecWait=No, TCC waits when I execute
Code:
"C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Word_16040.10827.20138.0_x86__8wekyb3d8bbwe\Office16\winword.exe"
CMD does not wait.

@EXETYPE gives 0 (unknown) for that file. DUMPBIN says it's subsystem GUI, and though there are some security restrictions in that directory tree, I can, with a plugin, open that file's properties dialog (so I wonder why @EXETYPE fails).

And (unrelated) if I just issue "winword", I get this.
Code:
v:\> winword
TCC: (Sys) The file cannot be accessed by the system.
 "C:\Users\vefatica\AppData\Local\Microsoft\WindowsApps\winword.EXE"
"START winword" works OK.
 
#3
Of "C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Word_16040.10827.20138.0_x86__8wekyb3d8bbwe\Office16\winword.exe", file says
Code:
WINWORD.EXE: PE32 executable (GUI) Intel 80386, for MS Windows
Once it was copied elsewhere, @EXETYPE said the same thing (6). But, as I said before, when it's in place, @EXETYPE fails and TCC waits after executing it.
 
Aug 23, 2010
285
2
#4
Can you check if an application it starting exports main or winmain ?
If it exports both, that probably explains your behavior.
An application exporting main expects to be started in console.