Starting Office 365 apps?

[vefatica]

Although I have ExecWait=No, TCC waits when I execute

"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.

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.

 

[Joe Caverly]

I do not have Office 365 apps, only Office 2007.

If you are on a system that has access to the Linux file command, it should tell you what type of a file it is.

You could also copy winword.exe to a system that has the Linux file command, to see what type of a file it is.

Joe

 

[vefatica]

Of "C:\Program Files\WindowsApps\Microsoft.Office.Desktop.Word_16040.10827.20138.0_x86__8wekyb3d8bbwe\Office16\winword.exe", file says

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.

 

[AnrDaemon]

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.