P: No image preview on Open dialog box on Windows

Partly because there are third party solutions, partly because we have have many more pressing matters for MS to fix.

So why not to publish a codec with such a warning: solution in progress, use on your own risk (MS sucks). And in the meantime why not to press MS a bit harder? I guess it is a matter of at least three years of discussing this topic (e.g. here: http://answers.microsoft.com/en-us/wi...). Congrats, folks.

Lack of an icon is also an OS issue -- we wrote a codec, found bugs in the codec API, and Microsoft has never gotten around to fixing the bugs in the API.

If you really want, you can get codec's for the PSD format -- but understand that third party codecs can still cause the "file busy or in use" problem due to the OS API bugs.

I guess there are actually two separate issues: the lack of preview in the Open dialog (which, I understand is really a MS problem) but also the overall lack of icon preview of .psd files in Win 7 folder windows. The last issue is ridiculous as AFAIK the problem is just a proper codec to be installed in the OS. As third party codecs work fine for 32-bit W7, why Adobe cannot write another one that would work in both versions? Another Microsoft pitfall or what? Hey guys, we actually pay you for that, remember?

Please read the comments. I've explained why this had to happen several times already.

This is not a bug, this is forced by changes in the operating systems and what we will (or won't) be allowed to do with their open/save dialogs.

I haven't read all the comments on this "lack of preview" issue because there are so many! I've only just started using CS6 and the very first thing I noticed was the lack of a preview image. CS6 has been out for a while now and I just can't believe that Adobe can be so arrogant as to dismiss this as "not a problem". I don't like Bridge and didn't use it much in CS5 because of the wonderful image preview which suits the way I work! Having just paid for CS6 I'll see how the rest of the software goes. I may finish up doing what a lot of others have done and go back to CS5. This is a very expensive fix!

My experience with mini bridge (suggested here) is not significantly better than full bridge. In fact, when launching mini bridge, I get the popup that bridge must be running. So it appears that regardless of the intention to offer a smaller footprint in mini, bridge is required.

I won't speak for everyone, but I run in a fairly robust machine - i7 processor and 8GB of ram and 7200rpm hard drive. Bridge is sluggish, requires more clicking than a playing card in the bicycle wheel, and eats up more memory than I want to give. I continue to try various thumbnail codecs and add ons, which only further convolute my system. One would think Adobe could talk to the OS providers if, in fact, that is where the issue began, to express this issue with its users. I understand that other application in the CS6 suite will be updated with this same open dialog change, it is odd to me that it has, as yet, not happened.

I sent a message to the folks at NAPP on the issue, the response was that I had "obviously not explore the robust asset management of Bridge." I knew I was in trouble at that point...

I'm not bashing here - just honestly frustrated that with the size and scope of Adobe Systems, there seem to be a lack of advocacy for its users.

tried this; doesn't seem to work for me.

Please read the previous replies.

May we all remind Adobe that it is 2012, not 1995. How challenging is it really, to implement a simple image preview from within the program? It's bad enough we can't see Adobe related thumbnails from within Windows, and now you take away what has to be one of the most rudimentary, basic features (if you can even call this a feature). Mini Bridge is a cumbersome piece of doo-doo that doesn't even have a direct file path built in, which means it's utterly useless at work. This because mini bridge doesn't recognize the server we work on, nor does it recognize simple desktop shortcuts that would take me where I need to go. A manual, direct file path would solve this. I refuse to use standard bridge. It is slow, chunky, and cumbersome, nor does it actually improve workflow speed. You spend most of your time aimlessly navigating through folders and file paths, constantly saving out PSDs to some location that is halfway across Egypt from where bridge loaded it.

It seems to me that this is Adobe's way of forcing users to work with mini bridge or purchase Bridge on top of Photoshop. Fix this or I'm going back to CS5. It's embarrassing.