VoxCommandoSP.exe - No languages suitable...

[liltee89]

...for speech found. If you are sure you have languages installed that support speech recognition, then you may need to run as an administrator." (see attachment)

If I run it as admin, all works fine. The problem is that I've installed it in C:\VoxCommando for NOT executing it as administrator (as the installer says). Why is it asking this? I've installed all the Microsoft Speech runtime component needed (core, SR and TTS voice), in fact VoxCommand works with that, but requires admin. Can anyone help me? Should I change installation folder or what?

[jitterjames]

I believe this is a bug that Microsoft introduced in Windows 8.  I don't think this issue relates to what folder you install to.  Windows does not allow programs to access the speech platform languages without administrative privileges. 

The solution is to run as administrator, or to use the regular non-SP version of VoxCommando.

You can create a shortcut for VC and adjust its properties so that it always runs as administrator automatically.

[jitterjames]

I tested this today on Windows 8.1 with UAC enabled and ran VC not as adminstrator and I don't have any problems so I guess it only affects certain systems.  But still the fact is that you need to run VC elevated or it can't see your speech engines.  I don't think there is anything we can do on our end other than complain about Windows 8.

[liltee89]

Ok thank you, so there's no solution. Is it possible to run it as admin without clicking on the uac? And without disabling it?

[nime5ter]

Try Option 5 here: http://www.eightforums.com/tutorials/9564-run-administrator-windows-8-a.html

(Or Option 6 to do the same thing using the program's shortcut icon.)

[jitterjames]

or maybe this:

http://www.thewindowsclub.com/create-elevated-shortcut-run-programs-bypass-uac

We are just googling so you could try that too! 

[nime5ter]

or maybe this:

http://www.thewindowsclub.com/create-elevated-shortcut-run-programs-bypass-uac

I have now had time to test this solution. It works well, however the syntax that the tutorial provides for the shortcut target in the final step is not quite correct.

Do not use quotation marks (" ") around the task name. So, if you name the task "NoUAC1" as he does in the tutorial, the shortcut target should be:

Code Select Expand

schtasks.exe /run /TN NoUAC1

Of course you can name the task whatever you prefer, and the shortcut as well.

[liltee89]

Okay thank you all for the support  I'll try these workarounds!