START /elevated and PcaSvc?

[vefatica]

In general, "START /elevated program" does not cause the Program Compatibility Assistand Service to start.

And "START [tcc]" does not cause PcaSvc to start.

But "START /elevated [tcc]" does cause PcaSvc to start.

Does anyone know what's going on there?

 

[rconn]

But "START /elevated [tcc]" does cause PcaSvc to start.

Not reproducible here.

 

[vefatica]

Not reproducible here.

Hmmm! I'm not doing anything very tricky.

v:\> sc query pcasvc & start /elevated & delay 5 & sc query pcasvc

SERVICE_NAME: pcasvc
        TYPE               : 30  WIN32
        STATE              : 1  STOPPED
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

SERVICE_NAME: pcasvc
        TYPE               : 30  WIN32
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0

 

[rconn]

START & TCC don't (and can't) start a service on their own. This is a question for Microsoft.

 

[vefatica]

START & TCC don't (and can't) start a service on their own. This is a question for Microsoft.

I was thinking something in, or not in, TCC's manifest might cause that. (?)

 

[AnrDaemon]

If you ever toyed with compatibility settings of a program, that may be it.