I connect to my computer remotely a lot but I don't use the regular RDP in Windows, I use TeamViewer instead. Since wallpaper changes tend to make remote sessions quite slow since it has to draw the new wallpaper every time it changes, I added the "Teamviewer_Desktop.exe" to the compatibility settings and checked the box to pause wallpaper changing while the application is active. "TeamViewer_Desktop.exe" is the executable which gets launched when you connect to the TeamViewer host (my computer in this case).
The wallpapers just keep on changing unfortunately.
I did not have this problem with the same setup when on Wndows 7 SP1 (x64).
I'm running the latest stable version of DF.
I just tried it with notepad.exe and the wallpapers paused as soon as I launched Notepad so it seems like it's something specific for the TeamViewer executable. On the other hand like I already mentioned, I had no problems with this on Windows 7.
Thanks! I've tested this out here with the same rule settings as yours, and it seems to work fine. Just to verify, you've created the Compatibility rule on the remote machine that you're connecting to, and not your local machine, correct?
Thanks! I've tested this out here with the same rule settings as yours, and it seems to work fine. Just to verify, you've created the Compatibility rule on the remote machine that you're connecting to, and not your local machine, correct?
Looking at the process manager part in the troubleshooting info, it looks like DF isn't recognizing that the TeamViewer_Desktop.exe file is even running.
The wallpaper is set to change every ten seconds (tried setting it to a minute too though but that didn't make any difference).
Ah, interesting. If you open up the Troubleshooting info on that machine, and also Task Manager, does TrueCrypt_Desktop.exe show up in Task Manager, but not the Troubleshooting info?
Ah, interesting. If you open up the Troubleshooting info on that machine, and also Task Manager, does TrueCrypt_Desktop.exe show up in Task Manager, but not the Troubleshooting info?
Yep, TeamViewer_Desktop.exe is listed in the Task Manager but not in the Troubleshooting info.
Weird! I'm not even sure how that can be possible... if you click the Select Application button in the Compatibility rule, does TeamViewer_Desktop.exe show up there?
Weird! I'm not even sure how that can be possible... if you click the Select Application button in the Compatibility rule, does TeamViewer_Desktop.exe show up there?
Nope, I have to browse for the executable file manually.
I must not have drank enough coffee when I initially tested this. When I tested, I used TeamViewer.exe, not TeamViewer_Desktop.exe.
I am actually seeing the same behaviour as you on both Windows 7 and Windows 8 machines. The reason that DisplayFusion isn't able to enumerate the TeamViewer_Desktop.exe process, is because it's running as the SYSTEM account, instead of your user account.
Since you mentioned that it used to work for you, yet it's not working for me in either OS now, my guess is that a recent TeamViewer update changed TeamViewer_Desktop.exe from running as the normal user to running as the SYSTEM user.
Unfortunately, there's nothing we can do to resolve that though, as it's just a security restriction in Windows. The only thing I can suggest is to manually pause the desktop wallpaper changes when you connect via TeamViewer. If I can think of another way to detect the TeamViewer session and pause the wallpaper, I'll let you know!
