Select Page
closeLook how old this is!
I post at SearchCommander.com now, and this post was published 18 years 2 days ago. This industry changes FAST, so blindly following the advice here *may not* be a good idea! If you're at all unsure, feel free to hit me up on Twitter and ask.

I just bought a “new” version of Voice Command (July 2005!) and I incorrectly assumed that Voice Command would work via Bluetooth by now, and frankly, I’m shocked that it doesn’t.

Although the software is great, and will announce upcoming appointments, and react to spoken commands quite well, it’s amazing that you still have to physically pick up the phone and push buttons to initiate the program, even though you’re connected wirelessly via a BT headset.  Come ON, Microsoft, get it together already!

Here’s a great article From Microsoft explaining WHY Bluetooth doesn’t work with Microsoft Voice Command, and here’s the registry hack that *might* make it work  for you –

DO THIS ONLY AT YOUR OWN RISK! ( I did not try yet, but lots of people sem to have made it function. Howeverm, they all have other complaints now, so i’m leaving it alone)

Open up a registry entry program such as Resco Registry that comes with Resco Explorer 2005. Then go to “HKEY_LOCAL_MACHINE\SOFTWARE\OEM\VoiceCommand\Path”.

Change the default value from “\Windows\SDDialer.exe” to “\Program Files\Voice Command\VoiceCMD.exe”. Now you should be able to activate Micrsoft Voice Command by pressing the connect button on your bluetooth headset.

If you like what you've seen here, would you please share this?