Now I am having problems with Bridge CS6 again. Both 64-bit and 32-bit suddenly have the behavior of freezing on launch. I get the application window open but no icons populate and I can't do anything in the interface. Not even close the application. I have to use Windows Task Manager to quit the application forcibly.
Not sure what's going on. I went to the start menu and hit Ctrl+Bridge 64-bit to give me the options to reset preferences, dump the cache, and one other option that I also checkmarked. Still no dice.
Can anyone help me out before Adobe Customer Support becomes available in 4 hours?
Yes, sorry. I didn't want to make my initial post too long.
I'm running Windows 7 64-bit Ultimate with more than 8GB RAM and a recently (just last week) updated Nvidia Graphics Driver for a Quadro FX 4000 Series GPU.
I have 2 partitions on a RAID Mirror setup with a reasonable amount of disk space remaining on both partitions.
I do appreciate that advice Curt but unfortunately, like the other case I had with Bridge, it simply does not list any pertinent information in the event viewer regarding any application crashes or any events related to Bridge whatsoever. There is no faulting module listed. I am in discussion with Adobe Tech support about this case but if you have any other suggestions, please feel free to make them as I might advise a support specialist about what was discussed in this forum in case they can't come up with a solution.
While searching for a set of files on my computer using traditional search in the gui i discovered that the indexing functionality of windows was turned off. I tried to turn it on and search again but kept getting the error that indexing was turned off. I went to the event viewer and saw hundreds of events related to this error. I thought by suspicion that there might be a correlation between this windows malfunction and adobe bridge not functioning properly. After finding an appropriate solution to reset the search functionality of Windows known as 1) Windows Search and also as 2) Indexing, I tried to run Bridge again and now it works just fine. So the solution to the Bridge problem was to fix Windows Search and also fix Indexing of files.
I think your solution may be coincidental. I have never had indexing on, and many others have it turnted off as well. It eats up resources and frequently will can a message in PS when saving file "file in use" as Windows is indexing it.
But glad you are up and running.
By the way, searching with Windows will still work without indexing. May just take a little longer.