Teamviewer 5 (www.teamviewer.com) doesnt start sandboxed (using START so not installed). Unsandboxed no problem and Teamviewer 4 works sandboxed and unsandboxed. Vista 32 bits using Sb 3.42.

I tried it on XP and had no problem connecting to my "remote partner" at ID 12345.
It worked for me, whether I installed it inside a sandbox, or installed it normally and then used "Run Sandboxed" (during a virtual session).

@Guest10

With XP Teamviewer 5 works here too (with KIS 2010). Stil no luck with Vista (with NIS 2010).

Maybe this will help.

Clsid -------------------------------
Ipc -------------------------------
Ipc O \RPC Control\SbieSvcPort
Pipe -------------------------------
WinCls -------------------------------

You should get a lot more from the Monitor than that.
First, turn on Sandboxie's Resource Access Monitor.
Then run the TeamViewer program, sandboxed, while leaving the Monitor window open.

Go through the process of connecting to another computer, and then copy the output from the Monitor to the Clipboard - post it here.

Here it is. Remeber Teamviewer 5 wont run sandboxed. One can see the teamviewerpicto though using Sandboxie control.

snipped. --tzuk

I would get this one out of the way first:
WinCls X #32770
I've seen it stop an "install", although not stop a "run" as is happening to you:

Sandbox Settings > Resource Access > Window Access
'Edit/Add' button and
#32770
in the box. Then OK.

If that does no good, try the same steps with some others:
(I have no idea what these are)
CiceroUIWndFrame
IME
MSCTFIME UI
---
Some TeamViewer and TVDLL resources show up, but they don't show as blocked.
Try adding these two with:
Sandbox Settings > Resource Access > IPC Access > Direct Access
'Edit/Add' button and put in the box
*\BaseNamedObjects*\TeamViewer*_Win32_Instance_Mutex
*\BaseNamedObjects*\TVDLL_*
then OK your way out.

Thanks Guest10. Its a Norton Internet Security 2010 related problem...

Thank goodness.
It's one thing to find necessary exclusions when I can run the program for myself.
Trying to identify necessary exclusions remotely, when someone else runs it, can be a pain.

@Guest10: your solution didnt work unfortunately.

I looked into this, on Windows Vista (and later) Team Viewer 5 uses some new networking functionality that is only available on Windows Vista (and later). But a problem in Sandboxie was making this new functionality inaccessible. I fixed this, and now I get TeamViewer to start correctly in Windows Vista. However,

* This is only with the "Run" mode with no installation. With full installation it still doesn't work sandboxed but I'm going to leave that to another day.

* I don't know that it actually works, for me it was enough at this time to get the start-up window. deugniet, you can test it when I release 3.43.09 (probably tomorrow) and tell me if there are still other problems.

With 3.43.09 Teamviewer 5 works (only "Run" mode). Thank you Tzuk.