Problems launching Bridge CS6

CS6 Beta-on going problem launching CS6 Bridge. Will not open up but CS6 PS does and will work with CS5 Bridge. This obviously is a issue as others have posted this. Have also gone back via "Time Machine" and restored the original CS6 Bridge download which worked for one day, but this no longer works either. Hard to do a beta test when half the program doesn't work! *

please follow related link-
http://forums.adobe.com/message/4289169#4289169

Similar Messages

Problem launching bridge in CS6

I have been trying to launch bridge for hours in CS6 ,having no luck, tried the command- option -o , have uninstalled and re-installed and still no luck.... ? any hints please

thanks, ok, running mac, mountain lion, I have installed CS6, when I launch bridge I get "waiting for bridge cs6" at the bottom of the opened photoshop page, there is a ' br' symbol next to mini bridge but nothing happens when i click on it. I have also gone up to 'file' open in bridge and also mini bridge but nothing there either. I have been to adobes help page and followed instructions to try to remedy the problem but to no avail. Also tried opening camera raw from the > photoshop > preferences > camera raw but no luck either..
thanks again
Col

Problem with Bridge CS6 and MCXRedirector (OS X 10.9.5)

Good afternoon all, I have a very irritating issue with Bridge CS6 that I've pretty much given up on now, so I'm wondering if anyone out there can help me before I do.
The issue lies with Bridge CS6 running in a networked Mac environment, first, a little background: I am using OS X Server's Workgroup Manager facility for various restrictions and folder redirection. Our users had a nasty bug a little while ago that caused saved Photoshop files to end up in ~/Library/Caches/TemporaryItems instead of the actual network home location they selected to save in. While this was happening, a single entry was being used in the MCXRedirectory preference to redirect the entire of ~/Library/Caches/
This was resolved by changing that preference and branching it out a little more, so now the folders subject to redirection are as follows:
~/Library/Caches/Adobe
~/Library/Caches/Adobe Camera Raw
~/Library/Caches/Meta
~/Library/Application Support/Adobe
Doing this fixed the saving issue with Photoshop, but has in turn broken Bridge. When launched, Bridge immediately fails with the error "Adobe Bridge CS6 quit unexpectedly" and gives the three options to ignore, report or reopen.
Taking away the ~/Library/Caches/Adobe redirection allows Bridge to work as normal again, but then I'm back to square one with Photoshop files saving in TemporaryItems again.
Does anyone have any advice to remedy this annoying problem please?
Thanks in advance.
EDIT: Bridge version is 5.0.2.4

Sorry, did not solve the problem. The info given did not bear much relation to what I could see in the print drop down box. I have been through all settings I can access and every thing appears normal. The print preview in the print box appears normal and shows colour, but this does not translate to the actual print.
When printing a docuement of 3 pages or more using double sided the result is the first docuement page on one side of a sheet and the last page on the other side, but upside down, despite orientation set to long edge binding. All other pages between first and last are ignored.
When printing docuements originating from printer software such as Print Quality Diagnostic and Make The Most Of Your Printer, the printer performs correctly with good quality printing and colour.
I assume that the Mac update to 10.9.5 has corrupted something but I am not knowkedgeable enough to understand what. Any further assistance would be greatly appreciated.

Problems launching Bridge from Photoshop and opening files as smart objects in Photoshop from Lightr

I am running Photoshop CC (up to date as of today) and Lightroom 5.2. I am hitting 2 major problems. In Photoshop if I select File/Browse in Bridge I get the following message
"Could not complete the Browse in Bridge command because Photoshop was unable to find the JavaScript plug-in".
However if I simply launch Bridge as an application it works ok (now I have reset the default application for all the appropriate file extentions to Photoshop CC rather than Photoshop in Bridge preferences) and opens the file in Camera Raw 8.2 in Photoshop when a Raw file is double clicked.
The second problem is associated with opening raw files in Lightroom 5.2, editing and then trying to "photo/edit in/Open as smart object in Photoshop" . In this case Photoshop opens with a blank screen and nothing happens Eventually about a minute later this message appears in Lightroom 5.2
"The file could not be edited because Adobe Photoshop CC could not be launched."
Rather strange message as the first thing that happened was that Photoshop CC opened!!
Same thing happens if try "photo/Edit in/Edit in Adobe Photoshop CC" except that having shut down photoshop I see a message from Lightroom 5.2 saying
Lightoom was unable to prepare the selected file at ..... for editing. It will not be opened.
When I click the OK button on this message low and behold the tif version of the RAW file opens in Photoshop. ready for futher editing with all the Lightroom edits applied.
Can anyone help me in sorting out this problem please
Operating system is Windows 8 64 bit and I am running the 64 bit Adobe applications.

Solved the problems by uninstalling Bridge and Photoshop then going into Creative Cloud App and re-installing both.

Have you had problems with Bridge CS6 after CR 8.4 installed?

Adobe Bridge CS6 running on Mac OS X 10.7.5 crashed several times while sorting images . After installing Camera Raw 8.4, images in portrait orientation rotated to landscape and now the rotate image buttons and menuitems are unavailable for raw files including dng's. Camera Raw preferences will not open from Bridge. What is the best approach for uninstalling/reinstalling Bridge and CR updates? Should I reinstall Photoshop as well?

I do recommend that anyone who is having weird issues with iTunes try Dave's suggestion of UNINSTALLING Flip4Mac and see what happens (but will an uninstall get rid of this particular file? who knows).
Good point, and something I should not have trusted without confirming. I just tried it and the uninstaller does not remove that framework. That's a serious "oops" on the part of Telestream (and I did confirm that the Flip4Mac installer does install that framework). The framework folder will need to be removed manually.
Regards.

Problem with Bridge CS6 and zooming to 100%

When I click on a file to zoom to 100% it zooms to 800%. I had the same problem in CS5 and fixed it by deleting the com.adobe.bridge.plist, but this does not work with CS6 and I don't even find the plist. I have a Mac with OS X 10.8.2. I found two plists, com.adobe.CSXS.3 and com.adobe.CSXS2Preferences but it didn't fix the problem deleting them.
I use the zoom function alot and would be very grateful if someone could help me. I do not like the preview workspace with the little 100% window, I prefer zooming to 100% by clicking on the file.

It does not work on a Mac, and they have only one set og +/-, at least my Macbook Pro has.
That is a bit strange, it always has worked for that way on both my Mac Pro and my MacBook.
I can use the scroll wheel on my mouse to enlarge the 100 % preview from loupe in preview window to 200, 400 and 800% but also the + and - keys from both my qwerty key board and the number pad of my extended keyboard for the same result.
Hitting tab for full screen preview I don't even have to click, both aforementioned + and - keys set to 100%, 200, 400 and 800% as well my scroll wheel.
All those methods work on both MacPro and MacBook.

Problem loading Bridge CS6, what is the problem?

I have just uploaded the subscription version of Photoshop CS6 and I can't get Adobe Bridge to load, any one have any ideas as to why?

Hi there! Because the forum you originally posted in is for beginners trying to learn the basics of Photoshop, I moved your question to the Downloading, Installing, Setting Up forum, where you'll get more specialized help.
However, you'll need to provide some additional information in order for others to help you. Please provide additional relevant details including:
Adobe product and version number
Operating system and version number
The full text of any error message(s)
What you were doing when the problem occurred
Screenshots of the problem
Computer hardware, such as CPU; GPU; amount of RAM; etc.

Recurring problem with Bridge CS6 64-bit

This happens every time I close Bridge to optimize my resources when I'm working in After Effects. I close out of Bridge - work for a while in After Effects, then need to import a new graphic into the project. When I try to start Bridge, nothing happens. So...I go to the task manager (Win Vista Business 64-bit), and guess what's still running there? bridge.exe - so I close it down in the task manager, then it starts up just fine.
Joe Bourke
Bourke Media

Never done it myself, but isn't there a Mac-style never-close-Bridge thingamy in Preferences (minimise to tray, or Start Bridge at Logon)? I think, when it's ticked, Bridge never closes, it minimised instead.
In Bridge preferences is a setting you can check so that Bridge starts when your computer starts (in other words login to your user account)
When you check this setting in Bridge on a Mac it starts in the background when you start the computer (the application is running but hidden from the desktop)
Hence I always use the option via the system preferences itself because I don't want it to be hidden but immediately active when I start working
However Bridge has it's own mind (sadly enough not limited to this setting only) and every now and then decides to either start hiding itself or even deselect the auto start option totally. To my memory this problem is as old as it first appeared (in CS3?)
I have learned to live with this, although under protest...
Can't think of a reason this setting should not be able in Windows (for Mac it is in the advanced preferences tab 'start bridge at login')
And on a Mac we have three little button icons on a document or open window. A red one to close it, a yellow one to minimize it to the dock and a green one to fit the screen.
Neither of them quits the application itself
That aside I seem to remember other threads about same issue with closing windows and not quitting the application for Windows also.

Bridge CS6 64-bit and 32-bit FREEZE on Launch

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?

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.

Bridge CC cache not compatible with bridge CS6

Starting the Photoshop CC adventure. First install was Bridge. First test was to see if the Bridge CC cache is compatible with Bridge CS6 cache. First result is NO.
Test method:
1. Set the Bridge CC cache location to the same folder I use for CS6, which contains 10+ gigs of thumbs for my library.
2. Navigated Bridge CC to a sub-folder with about 30 images, see Bridge CC re-do the thumb extractions.
3. Close Bridge CC, launch Bridge CS6, navigate to the same sub-folder, see Bridge CS6 re-do the thumb extractions.
4. Close Bridge CS6, launch Bridge CC, still pointing to the same sub-folder, see it re-do thumb extractions again.
5. Repeat steps 3&4, always with same result, a redundant re-generation of thumbs.
Conclusion:
The actual thumbnail files in the cache are the same. But something happens in the index files (data/store) to make each version think it does not have thumbnails, so it re-generates them. IOW, when Bridge CC looks at the cache last used by Bridge CS6 it says "I have not been here, must re-cache", and visa-versa.
Solution:
Must let Bridge CC have its own separate cache, so the two versions don't walk over each other. Must let Bridge CC re-cache everything, which for me (and most users I assume) will be a long and time consuming process.
Not much surprise here. The same was true for CS5 vs. CS6.

Not much surprise here. The same was true for CS5 vs. CS6.
Then it also should not be a surprise for you that this behavior already started in the Filebrowser (Bridge predecessor that came with CS1 and by far the most stable and fast cache ever in the history of Bridge) and has not changed since. Nor is it likely it will chance in the future.
Hence my advice to not use Bridge for long term DAM because you need to recache the lot every new version...

Bridge CS6 crashes when I apply metadata

Similar problem to this: http://forums.adobe.com/message/5025995
The problem started suddenly last week. If I try to apply metadata or keywords to an image, Bridge closes. Sometimes I can apply one or two keywords before this happens, but not many and it always closes after applying more than a few keywords. Before this started, I had no problems with Bridge CS6.
Have tried updating graphics card drivers, resetting preferences, rebooting, changing the locatioon of the photos, with no luck.
Win7-64 bit, 3GB RAM
Version=1
EventType=APPCRASH
EventTime=130075875636681628
ReportType=2
Consent=1
UploadTime=130075875638241658
ReportIdentifier=164771e9-8b45-11e2-84ee-002186f773e8
IntegratorReportIdentifier=164771e8-8b45-11e2-84ee-002186f773e8
Response.BucketId=91441965
Response.BucketTable=4
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=Bridge.exe
Sig[1].Name=Application Version
Sig[1].Value=5.0.2.4
Sig[2].Name=Application Timestamp
Sig[2].Value=50d9a019
Sig[3].Name=Fault Module Name
Sig[3].Value=StackHash_616b
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.17725
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=4ec4aa8e
Sig[6].Name=Exception Code
Sig[6].Value=c0000374
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000c40f2
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.4
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=616b
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=616b82bd806673b43f5b3a110bcea586
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=dd62
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=dd6240926115030fc2df7dbe321d314b
UI[2]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
UI[3]=Adobe Bridge CS6 has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[5]=C:\Windows\system32\GDI32.dll
LoadedModule[6]=C:\Windows\system32\USER32.dll
LoadedModule[7]=C:\Windows\system32\LPK.dll
LoadedModule[8]=C:\Windows\system32\USP10.dll
LoadedModule[9]=C:\Windows\system32\msvcrt.dll
LoadedModule[10]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.76 01.17825_none_2b253c8271ec7765\gdiplus.dll
LoadedModule[11]=C:\Windows\system32\ole32.dll
LoadedModule[12]=C:\Windows\system32\RPCRT4.dll
LoadedModule[13]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\icuuc40.dll
LoadedModule[14]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[15]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[16]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\icudt40.dll
LoadedModule[17]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\MSVCR100.dll
LoadedModule[18]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\icuin40.dll
LoadedModule[19]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Symlib.dll
LoadedModule[20]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\amtlib.dll
LoadedModule[21]=C:\Windows\system32\WINHTTP.dll
LoadedModule[22]=C:\Windows\system32\webio.dll
LoadedModule[23]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[24]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[25]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[26]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[27]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[28]=C:\Windows\system32\NSI.dll
LoadedModule[29]=C:\Windows\system32\WINNSI.DLL
LoadedModule[30]=C:\Windows\system32\SHELL32.dll
LoadedModule[31]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\BIB.dll
LoadedModule[32]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\ExtendScript.dll
LoadedModule[33]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\ScCore.dll
LoadedModule[34]=C:\Windows\system32\WS2_32.dll
LoadedModule[35]=C:\Windows\system32\d3d9.dll
LoadedModule[36]=C:\Windows\system32\VERSION.dll
LoadedModule[37]=C:\Windows\system32\d3d8thk.dll
LoadedModule[38]=C:\Windows\system32\dwmapi.dll
LoadedModule[39]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\d3dx9_43.dll
LoadedModule[40]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AXEDOMCore.dll
LoadedModule[41]=C:\Windows\system32\UxTheme.dll
LoadedModule[42]=C:\Windows\system32\MSIMG32.dll
LoadedModule[43]=C:\Windows\system32\WINMM.dll
LoadedModule[44]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobeXMP.dll
LoadedModule[45]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\MSVCP100.dll
LoadedModule[46]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobeXMPFiles.dll
LoadedModule[47]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\ACE.dll
LoadedModule[48]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\BIBUtils.dll
LoadedModule[49]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AXE8SharedExpat.dll
LoadedModule[50]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\CoolType.dll
LoadedModule[51]=C:\Windows\system32\IMM32.DLL
LoadedModule[52]=C:\Windows\system32\MSCTF.dll
LoadedModule[53]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[54]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1d f_6.0.7601.17514_none_fa396087175ac9ac\Comctl32.dll
LoadedModule[55]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\adobe_caps.dll
LoadedModule[56]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[57]=C:\Windows\system32\propsys.dll
LoadedModule[58]=C:\Windows\system32\ntmarta.dll
LoadedModule[59]=C:\Windows\system32\WLDAP32.dll
LoadedModule[60]=C:\Windows\system32\profapi.dll
LoadedModule[61]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AGM.dll
LoadedModule[62]=C:\Windows\System32\msxml6.dll
LoadedModule[63]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Required\PhotoshopAdapter.apl
LoadedModule[64]=C:\Program Files\Common Files\Adobe\Plug-Ins\CS6\File Formats\Camera Raw.8bi
LoadedModule[65]=C:\Windows\system32\PSAPI.DLL
LoadedModule[66]=C:\Windows\system32\OPENGL32.dll
LoadedModule[67]=C:\Windows\system32\GLU32.dll
LoadedModule[68]=C:\Windows\system32\DDRAW.dll
LoadedModule[69]=C:\Windows\system32\DCIMAN32.dll
LoadedModule[70]=C:\Windows\system32\mscms.dll
LoadedModule[71]=C:\Windows\system32\USERENV.dll
LoadedModule[72]=C:\Windows\system32\icm32.dll
LoadedModule[73]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[74]=C:\Windows\system32\apphelp.dll
LoadedModule[75]=C:\PROGRA~1\OpenAFS\Client\Program\AFS_SH~1.DLL
LoadedModule[76]=C:\Program Files\OpenAFS\Common\afsrpc.dll
LoadedModule[77]=C:\Program Files\OpenAFS\Common\afspthread.dll
LoadedModule[78]=C:\Windows\WinSxS\amd64_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_88e41e092fab0294\MSVCR80.dll
LoadedModule[79]=C:\Program Files\OpenAFS\Common\afshcrypto.dll
LoadedModule[80]=C:\Program Files\OpenAFS\Common\afsroken.dll
LoadedModule[81]=C:\Program Files\OpenAFS\Common\afsauthent.dll
LoadedModule[82]=C:\Program Files\OpenAFS\Common\afsprocmgmt.dll
LoadedModule[83]=C:\Windows\system32\NETAPI32.dll
LoadedModule[84]=C:\Windows\system32\netutils.dll
LoadedModule[85]=C:\Windows\system32\srvcli.dll
LoadedModule[86]=C:\Windows\system32\wkscli.dll
LoadedModule[87]=C:\Program Files\OpenAFS\Common\libafsconf.dll
LoadedModule[88]=C:\Windows\system32\DNSAPI.dll
LoadedModule[89]=C:\Windows\system32\MPR.dll
LoadedModule[90]=C:\Windows\system32\Secur32.dll
LoadedModule[91]=C:\Windows\system32\SSPICLI.DLL
LoadedModule[92]=C:\Windows\WinSxS\amd64_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.619 5_none_8448b2bd328df189\MFC80U.DLL
LoadedModule[93]=C:\Windows\WinSxS\amd64_microsoft.vc80.mfcloc_1fc8b3b9a1e18e3b_8.0.50727. 6195_none_bc20f59b0bdd1acd\MFC80ENU.DLL
LoadedModule[94]=C:\PROGRA~1\OpenAFS\Client\Program\afs_shl_ext_1033.dll
LoadedModule[95]=C:\Users\rmunde.AD\AppData\Roaming\Dropbox\bin\DropboxExt64.17.dll
LoadedModule[96]=C:\Windows\system32\dbghelp.dll
LoadedModule[97]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCP90.dll
LoadedModule[98]=C:\Windows\WinSxS\amd64_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.616 1_none_08e61857a83bc251\MSVCR90.dll
LoadedModule[99]=C:\Windows\system32\EhStorShell.dll
LoadedModule[100]=C:\Windows\System32\cscui.dll
LoadedModule[101]=C:\Windows\System32\CSCDLL.dll
LoadedModule[102]=C:\Windows\system32\CSCAPI.dll
LoadedModule[103]=C:\Program Files (x86)\DisplayFusion\Hooks\AppHookx64_A8B98FDD-7B80-43AA-B9C7-82B660068E89.dll
LoadedModule[104]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[105]=C:\Windows\system32\rsaenh.dll
LoadedModule[106]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[107]=C:\Windows\system32\mssprxy.dll
LoadedModule[108]=C:\Windows\system32\SnacNp.dll
LoadedModule[109]=C:\Windows\System32\drprov.dll
LoadedModule[110]=C:\Windows\System32\WINSTA.dll
LoadedModule[111]=C:\Windows\system32\AFSRDFSProvider.dll
LoadedModule[112]=C:\Windows\System32\ntlanman.dll
LoadedModule[113]=C:\Windows\System32\davclnt.dll
LoadedModule[114]=C:\Windows\System32\DAVHLPR.dll
LoadedModule[115]=C:\Windows\system32\dlumd64.dll
LoadedModule[116]=C:\Windows\system32\wtsapi32.dll
LoadedModule[117]=C:\Windows\system32\nvd3dumx.dll
LoadedModule[118]=C:\Windows\system32\powrprof.dll
LoadedModule[119]=C:\Program Files (x86)\NVIDIA Corporation\3D Vision\nvSCPAPI64.dll
LoadedModule[120]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\FileInfo.dll
LoadedModule[121]=C:\Windows\system32\OLEACC.dll
LoadedModule[122]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\adbeape.dll
LoadedModule[123]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[124]=C:\Windows\system32\COMDLG32.dll
LoadedModule[125]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\WinFeatures.dll
LoadedModule[126]=C:\Windows\system32\XmlLite.dll
LoadedModule[127]=C:\Windows\system32\LINKINFO.dll
LoadedModule[128]=C:\Windows\system32\SearchFolder.dll
LoadedModule[129]=C:\Windows\System32\cscobj.dll
LoadedModule[130]=C:\Windows\system32\tquery.dll
LoadedModule[131]=C:\Windows\System32\StructuredQuery.dll
LoadedModule[132]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\SwitchBoardClient.dll
LoadedModule[133]=C:\Program Files\Common Files\Adobe\APE\3.3\adbeapecore.dll
LoadedModule[134]=C:\Program Files\Common Files\Adobe\APE\3.3\adbeapeengine.dll
LoadedModule[135]=C:\Windows\system32\CRYPT32.dll
LoadedModule[136]=C:\Windows\system32\MSASN1.dll
LoadedModule[137]=C:\Windows\system32\WININET.dll
LoadedModule[138]=C:\Windows\system32\Normaliz.dll
LoadedModule[139]=C:\Windows\system32\iertutil.dll
LoadedModule[140]=C:\Windows\system32\urlmon.dll
LoadedModule[141]=C:\Windows\system32\msi.dll
LoadedModule[142]=C:\Windows\system32\DSOUND.dll
LoadedModule[143]=C:\Windows\system32\mlang.dll
LoadedModule[144]=C:\Windows\system32\credssp.dll
LoadedModule[145]=C:\Windows\system32\schannel.DLL
LoadedModule[146]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobePSL.dll
LoadedModule[147]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\tbb.dll
LoadedModule[148]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\tbbmalloc.dll
LoadedModule[149]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[150]=C:\Windows\system32\wbemcomn.dll
LoadedModule[151]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[152]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[153]=C:\Windows\system32\NTDSAPI.dll
LoadedModule[154]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\FastCore.8BX
LoadedModule[155]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\MMXCore.8BX
LoadedModule[156]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\libmmd.dll
LoadedModule[157]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Plug-Ins\MultiProcessor Support.8BX
LoadedModule[158]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\PLUGIN.dll
LoadedModule[159]=C:\Windows\system32\MMDevAPI.DLL
LoadedModule[160]=C:\Windows\system32\wdmaud.drv
LoadedModule[161]=C:\Windows\system32\ksuser.dll
LoadedModule[162]=C:\Windows\system32\AVRT.dll
LoadedModule[163]=C:\Windows\system32\AUDIOSES.DLL
LoadedModule[164]=C:\Windows\system32\msacm32.drv
LoadedModule[165]=C:\Windows\system32\MSACM32.dll
LoadedModule[166]=C:\Windows\system32\midimap.dll
LoadedModule[167]=C:\Windows\System32\shdocvw.dll
LoadedModule[168]=C:\Windows\system32\slc.dll
LoadedModule[169]=C:\Windows\System32\ieframe.dll
LoadedModule[170]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\AdobePIP.dll
LoadedModule[171]=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\LogSession.dll
State[0].Key=Transport.DoneStage1
State[0].Value=1
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Adobe Bridge CS6
AppPath=C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe

Here is the report that includes the faulting module. Is this what you meant?
Description:
Faulting application name: Bridge.exe, version: 5.0.2.4, time stamp: 0x50d9a019
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec4aa8e
Exception code: 0xc0000374
Fault offset: 0x00000000000c40f2
Faulting process id: 0x64c
Faulting application start time: 0x01ce1f655f6c8caf
Faulting application path: C:\Program Files\Adobe\Adobe Bridge CS6 (64 Bit)\Bridge.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: 130d23f2-8b59-11e2-84ee-002186f773e8

Bridge CS6 bug (?) opening Hasselblad RAW files

Summary:
Some of my Hasselblad RAW files cause an error message when opening in Bridge or PS. Further when using Bridge, more and more of these files get corrupted. I can use Nikon RAWs without problem so it does not seem to be my system or setup. I only happens with the Hasselblad RAWs. I can use Hasselblad files using the original Hasselblad software without problems so it can not be my Hasselblad camera setup which I am using for years now. Further, I can still open these CS corrupted files with the hasselblad software. When I only work with the Hasselblad software there is absolutely NO problem for years now. I only have this issue when I switch to Bridge CS6.
Details:
I have a set of Hasselblad FFF RAW files that I can use and open without problems in Bridge CS6 (5.0.0.399 x64). But one file of them did not show a preview icon and when I tried to open it in PS6 or RAW editor, I get an errormessage "Could not complete your request because an unexpected end-of-file was encountered.". When I open the same file in Hasselblad "Phocus" software there is no problem. I can see the preview thumb there and I can play around with the file and even export to TIF or DNG without any trouble. I can even open the exported DNG in PS or Bridge/RAW editor then. But it is impossible to work with the RAW file in Bridge.
Yes, it looks like the file is corrupted. But why can I open the same file with the Hasselblad software? I work with the Hasselblad software for years now and NEVER had any issues.
Now I started working with the uncorrupted files in CS6 (playing with the RAW settings, open in PS, etc.). After some days I get more and more "corrupted" files. Even files that showed a thumb before are no longer showing the icon and are unable to open. So the same files that where ok at first now are corrupted! This only happens with Hasselblad files. I have absolutely no issue with Nikon RAWs, which I also use a lot. So the problem can not be caused by my computer or my system.
No there is no issue with my Hasselblad setup because I use this for years now and it workes absolutely flawless with the Hasselblad RAW software. the problems arised when I started using Bridge CS6. When I turn back to the Hasselblad Phocus software all these corrupted files are able to open! All files are 100% ok there! It shows all the thumbs and I can export these files to TIF and DNG without any trouble. Back in Bridge I can even open the DNG files then but not the original RAW files.
Please don't tell me my files are corrupted or I need to change my way of file transfer. This is definately not the case because everything works fine when I work the way I did for years. The problems started when I switched to CS6.

The older FFF format is not completely supported in ACR. I suggest using Phocus to read the FFF files and save/export as DNG, which can then be read in ACR.

Bridge CS6 open file bug with Hasselblad RAW file

There is a bug in Bridge CS6 (or RAW editor?) with (some) Hasselblad RAW files. I have a set of FFF files that I can use and open without problems in Bridge CS6 (5.0.0.399 x64). But one file of them does not show a preview icon and when I try to open it in PS6 or RAW editor, I get an errormessage "unexpected end of file...". When I open the same file in Hasselblad "Phocus" software there is no problem. I can see the preview thumb and I can play around with the file and even export to TIF or DNG without any trouble. I can even open the exported DNG in PS or Bridge/RAW editor then.
Well, you might say I should not care for a single file but it leaves a bad taste, when the Hasselblad software can handle the file without problems...
If some developer want to take a look at this I could provide original files.

Curt Y wrote:
Also, be sure to use a card reader for file transfer as a camera transfer can introduce errors.
I work with a Hasselblad medium format camera. I do not have a CF card in use. And I can tell that this worked absolutely flawless for many years. I NEVER had corrupted files caused by transfer. Many photographers using pro medium format cameras work the same way (Phase One, Leaf, etc.). They do not use CF cards but firewire cable. the problem arised when I started using the CS6 Bridge software. And it turned out that I get more and more corrupted files which appeared to be fine before. So from one shooting i.e. 1 file of 100 was corrupted first. Since I started using Bridge and changed RAW settings and worked with the same files after some days I have 5 corrupted files of 100 now. And NO it is not my system. It works fine with other camera RAWs where I have absolutely no problems. It is only the Hasselblad files. Though I still can open the Hasselblad RAW files with the Hasselblad software. The problems are only with the Bridge (respectively the raw editor) in combination with the Hasselblad files.
To me it looks like CS is corrupting the files since they worked fine at first - even in CS and after some days playing around in CS the appear to be corrupted. Funny that I can open the same files without problems using a different software - isn't it? ;-)
thanks for the link I will try it.... :-)

Even local drives not seen by Bridge CS6 (64bit)

Hi,
I am having problems with Bridge CS6 unable to find any drives in the system as well as Network Drives. The funny thing is I can see all local and Network Drives in Bridge in the Folders Panel as well as in Edit->Camera Raw Preferences, but when I try Edit ->Preferences->Cache-> Choose, all I see is Desktop & \User Folder. No local drives or network drives. I am running Bridge as an Adminstrator, and Windows 7 Professional, 64Bit. I do not have any problems whatsoever in other CS6 applications like Photoshop, Premiere Pro, Indesign, Fireworks, Dreamweaver etc.
Please see the screen shot below:
What hurts? TIA.

Sorry, forgot to include link. http://forums.adobe.com/message/4394643

How can i reset Bridge CS6 to its default settings?

Hello,
i have a problem with Bridge CS6. Somehow its very slow and lags. when i tried to open a folder it takes sometimes several minutes before anything happens. is there a way to reset bridge to its default settings without reinstalling?
Thanks

What OS?
It is probably either a full HD or too large of a cache. You should have 10-20% free space on HD. You can purge cache in edit/preferences/cache.
If you have cache exported to folders also this will not purge it. Have to go to Tools/cache/purge cache for xxx folder.

Problems launching Bridge CS6

Similar Messages

Maybe you are looking for