Until now, we were on TD3.1SP4. We build several Services with Team Developer 3.1 and the good old ntsvc.ocx.
We have a small Starter-App which talks with windows Service architecture. This App starts as a Service as local system and starts via SalLoadApp a Helper Process.
Any Teamdeveloper 3.1 EXE starts and behave as designed and expected

Not so our new Teamdeveloper 6.3 SP2 Exe ! Its half initialized, SAM_AppStartup Events is not fired or processed....
Not as local system as well as a local User.

Sorry for this (very) late enlightnenment... but i were wrong.
Simple there was a bug at initialisation.
TD6.3 behaves on Windows Server 2012 with good-old ntsvc.ocx as expected.
All Services run well.