Using Win7RC, browsing and using Windows Preview (photo viewer) to view public pictures on a Vista SP2 machine in the same workgroup. On the Vista machine I used 'Preview' to view the pictures in the public pics folder and all is ok. On the Win7 machine, browsed across the network to the same Vista shared public pictures folder. Used 'Preview'. The pictures look ok, but the file names displayed are all mixed up, not matching the picture actually displayed. Using Win7 Preview to view pics on the local drives works ok. So... Seems like the Win-7RC photo viewer is having some issues keeping the file names & pics in sync across the net. I know this couldn't be happening, so tried it a couple more times, double checking the folders, locations, file names, etc. But it is still happening.

Could you please capture screenshots when you preview from network and preview locally? We will compare these two screenshots and try to find some clues. Please attach the screenshots in SkyDrive of your Live Space. Then please provide the web address in your post.Arthur Xie - MSFT

I've determined the problem is not the picture viewer, but it does seem to be Windows Explorer on the Windows-7 machine. The filename problem with the viewer was just a symptom of the underlying problem described below. A few file names are "stuck in cache" when I use explorer to browse and view a particular shared directory on a Vista SP2 machine. I've renamed, deleted, re-created, copied, edited and otherwise fooled around with the files in question. I've managed to copy the remote shared directory to a local shared directory and the problem was copied with the files, so I believe the problem is totally contained within Windows-7. For example, there is a picture named creek.jpg. When I browse with Win7 explorer the file is seen as Chrysanthemum.jpg. (I'll call it C.jpg from now on to simplify). If I delete creek.jpg, the c.jpg name goes away. If I copy a different .jpg file and call it creek.jpg, then Win7 again shows it as C.jpg. If I delete creek.jpg and create an empty text file and rename it to creek.wav then C.jpg shows up again. If I rename creek.jpg to creekZ.jpg, then creekZ.jpg shows up properly in Win7 and C.jpg is gone. But then I rename it back to creek.jpg and the bogus C.jpg name shows up again. Browsing, copying, etc with cmd.exe works properly in all cases. So the file system seems ok. A Complete NTFS file system check with chkdsk found no problems and fixed nothing. I've deleted desktop.ini files and recreated directories to start fresh. There are more hours of tinkering that I won't describe here regarding copying to/from Win-7, Deleting with Win7 and re-creating with Vista, etc. But I've decided that a few filenames are stuck in Windows-7 Explorer Cache. Not the file contents, just the file name. I have found no way to flush Win7 explorer file name cache(s). Reboots don't help. Explorer restarts don't help. So I guess the question now is: Is there a convenient way to cause Windows-7 Explorer to flush or rebuild any filename caches and get a fresh start?

It seems that you have a messed desktop.ini settings files or something like that. These files should be kept with hidden and system attributes, so perform that in a command prompt with administrative privileges, to hide these files, and therefore not let it be messed up again by accident: for /r "%SystemDrive%" %i in (desktop.ini) do attrib +H +S "%i" wait until the command completes performing, since it adds hidden and system attributes to ALL desktop.ini files, that you have on the system drive. So I guess the question now is: Is there a convenient way to cause Windows-7 Explorer to flush or rebuild any filename caches and get a fresh start? You can try to rebuild your search index via Indexing Options in Control Panel, maybe it also rebuild the cache.

I usually keep hidden+system files as +h+s unless I'm troubleshooting. And I didn't start mucking around with desktop.ini files in this case until a problem showed up that needed to be understood (after all, we ARE testing the RC for the benefit of all mankind, right?). And you can tell I've been around the block once or twice. Haven't resolved it yet. It almost has to be desktop.ini (or related) involved in some way. I will visit the issue some more as time permits. In the meantime folks might want to keep an eye open for situations when browsing pics and a filename doesn't match the picture. Not likely I'm the only one. The(my) goal is to discover and cause to be fixed one genuine bug in Win-7. So far this problem is as close as I've come to discovering one. Pretty darned solid for a Beta/RC. I've found a couple of features to hate, but not bugs :-)