I'm looking at ProcessMonitor and here is what happens when I enable BT through console3.
1. wcourier.exe crates a new thread.
2. c:\program files (x86)\bluetooth suite\adminservice.exe creates a new thread.
3. c:\program files (x86)\bluetooth suite\ath_coexagent.exe creates a new thread.
4. hklm\system\currentcontrolset\services\bthport is read by adminservice.exe.
5. some Atheros registry keys are hit.
6. There is a btvstack.exe and athbttray.exe that also access some registry.
I think what happens is wcourier utilizes WMI to enable/disable the BT.
I would like to see what your ProcessMonitor dump looks like since you're the odd ball here. You can include all processes in the dump, I can sort through them.
G74SX-A1
BIOS: NONE | VGA: 560M @ 311.00 | WIFI: AR9002WB-1NG @ 9.2.0.458 | LAN: Realtek PCIe BGE @ 7.37.1229.2010 | Synaptic: 15.3.43.0 | Audio: Realtek @ 6.0.1.6564
Chipset: 9.3.0.1019 | P4G: 1.1.48 | Wireless Console : 3.0.27