Hello, on our Windows Server 2008 R2 Terminalserver suddenly all users report that they can no longer open image files like jpg, gif, bmp and so on. Other files like pdf, docx, work as expected. The default program associated with these file types is Windows Photoviewer. I logged in as an administrator on the Server and i see the same behaviour. It does not matter if the file is newly created or existing and it does not matter if the file is on a network path or local. The problem appeared over night. No updates were installed and no new programs. Yesterday all was fine. I had a look at the following registry key: HKEY_CLASSES_ROOT\jpegfile\shell\open\command Value is: %SystemRoot%\System32\rundll32.exe "%ProgramFiles%\Windows Photo Viewer\PhotoViewer.dll", ImageView_Fullscreen %1 When i create a new key under HKEY_CLASSES_ROOT\jpegfile\shell named open.viewer and under that create a new key named command so it looks like this HKEY_CLASSES_ROOT\jpegfile\shell\open.viewer\command Same Value: %SystemRoot%\System32\rundll32.exe "%ProgramFiles%\Windows Photo Viewer\PhotoViewer.dll", ImageView_Fullscreen %1 This creates a new entry when i right click a jpg file and when i click on that this does not work either but throws an error message saying that i do nat have permissions to the path or folder. Then when i change the command to not use System Variables and it looks like: c:\windows\system32\rundll32.exe "C:\Programme\Windows Photo Viewer\PhotoViewer.dll", ImageView_Fullscreen %1 it works!!!!! When i copy this command without Variables back to HKEY_CLASSES_ROOT\jpegfile\shell\open\command it does not work. This makes me crazy. I really need to know how to solve this one.

Hi, have you checked how are configured System Variables on that server ?Edoardo Benussi - Microsoft MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org

This is in the path variable: %SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\

and what is in %ProgramFiles% ?Edoardo Benussi - Microsoft MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org

What do you mean? I can navigate to %programfiles% in a command prompt so the variable is working. doing the dir command in that directory shows the Windows Photo Viewer directory as well.

It seems that HKEY_CLASSES_ROOT\jpegfile\shell\open\command is the wrong place to look for. Can you point me to the right regkey that is responsible when double clicking an image file or opening it with right click and open with?

It seems that HKEY_CLASSES_ROOT\jpegfile\shell\open\command is the wrong place to look for. Can you point me to the right regkey that is responsible when double clicking an image file or opening it with right click and open with? the place is right: see here http://www.devx.com/vb2themax/Tip/19230 Edoardo Benussi - Microsoft MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org

O.K., good to know but how to solve the problem that when double clicking image files nothing happens?

I suggest you to verify what happens using Process Explorer by sysinternals that you can find here http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx Let we know. byeEdoardo Benussi - Microsoft MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org

Edoardo, Did you mean Process Monitor? Utto, Can you give us the exact text or a screenshot of the error that you see when you try to open an image? Also, please open Control Panel and in the search box, type in "File associations". Under Folder Options, click "Change the file type associated with a file extension." Scroll down to .jpg and confirm that the "Current Default" program listed is Widows Photo Viewer. Check the other image types as well. Finally, have you checked your applicaton and system event logs to see if anything was added/changed after this issue was discovered?David Beach - Microsoft Online Community Support

Edoardo, Did you mean Process Monitor? Hi, no, it is even called Process Explorer. See the link.Edoardo Benussi - Microsoft MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org

Edoardo, Did you mean Process Monitor? Hi, no, it is even called Process Explorer. See the link. Edoardo Benussi - Microsoft® MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org Interesting. Typically in support we use Process Monitor for access issues, and Process Explorer for handle/thread issues. If I'm understanding correctly, you are recommending that Utto use Process Explorer to watch and see whether the application is properly invoked or not when the file is clicked? Either way could potentially shed some light on the cause of the issue, so hopefully it will help Utto out.David Beach - Microsoft Online Community Support

If I'm understanding correctly, you are recommending that Utto use Process Explorer to watch and see whether the application is properly invoked or not when the file is clicked? Hi David, yes, you are right. Now we can waiting for Utto's tests.Edoardo Benussi - Microsoft MVP Management Infrastructure - Systems Administration https://mvp.support.microsoft.com/Profile/Benussi Windows Server Italian Forum Moderator edo[at]mvps[dot]org