I had this p[roblem with PS CS4 and now with PS CS5. I use Firefox, and have been through several updates of it since the problem began. At onepoint I removed and reinstalled Photoshop CS4. So far, nothing has solved the problem on this (desktop running Windows 7) computer, although Bridge works on my laptop (running XP).

Thanks to everyone contributing to this on-going issue. AJ, I initially ran

CCleaner from Piriform on the registry and cleaned out a lot of naval lint

but didn't see anything there that seemed to impact the launching of Bridge.

I may try another registry cleaning program as well to see if CCleaner

(which I recommend and it is free) missed anything. Just a reminder, always

back up your registry before making any changes to it.

How many of those affected her are using Norton Internet Security?

Several years ago I had a computer crash and burn, no retreaval possible, caused by Norton System Works right after they had integrated Ghost file back up to the software. I discovered after the fact that I was not the only one that happened to. So I do have a healthy distrust of the Norton product line. I finally went relented and went back. Right now my subscription is up in 21 days so I would like to figure out if this is causing problems to me.

Hi Cathy-

I closed down completely Norton Internet Security and tried launching Bridge

again... still no luck.

Ron

Hi Curt-

Read the thread on the earlier Norton problem. It was a problem that

required a special free version of Norton supplied, as you correctly pointed

out, by Comcast to their subscribers and it manifested itself only on WinXP

machines. It involved Norton creating some virtual drives and a hincky dll

called bushell. Removing the dll resolved the problem, although Adobe did

develop a small self-executable patch as well.

I've completely shut down the Norton suite and tried to launch Bridge, but

still have had no luck. I've also tried to debug Bridge using Microsoft's

Software Development Kit's debugging tool as well as analyzing Bridge using

Sysinternals Process Explorer. PE is tough because Bridge has to try to

launch long enough so that you can select it in PE and then use the dropdown

menu to debug and copy the strings. My reflexes aren't that fast to select

and copy all the processes.

Meanwhile, I am still trying to Google my way out of this mess (with no luck

so far).

Ron

Hi SB-

At this point I don't think it's Norton either. I'm about Googled-out of

looking for previously found solutions.

Ron

win xp sp3

no norton installed no firefox

ran all updates through the Adobe installer

using Vipre virus

can open ACR  6.3 in PS one image at a time (JPGS)

I can open in Bridge any image previously adjusted by Bridge ACR from CS3

facebook export does not work but Flickr does

any attmept to open mulitple files in Bridge ACR

get error: you must launch parent application

well have done so many times

in PS I can set the camera raw preferences

but try to open same in Bridge, gets same error

also cannot access Creative Suite preferences

I can  upload images but without being able to process images many at a time it is totally USELESS to me

guess it's back to CS 3 for me

it will not let me reinstall or do updates- says already installed

I've decided that we should collectively rename this topic "The Bridge to

Nowhere."

Curt, thanks for your latest email. You are right, the problem appears to

reside in the kernel32.dll. Kernel32.dll accesses all the primary resources

available to a Windows system. This is where you find the way to things like

file systems, devices, processes and threads, and error handling. This is

essentially where the rubber hits the road when calling an executable.

I think it might be helpful to all of us to compare notes, so to speak, by

examining where Bridge seems to be failing on each of our systems. It is

actually pretty simple to do and if five or ten people post their results

here, we may have enough information for Adobe Support to actually do

something about this problem.

To use Event Viewer in Windows (the Microsoft snap-in utility that enables

you to browse and manage event logs.) is pretty simple:

To start Event Viewer by using the Windows interface

     1. Click the Start button.

     2. Click Control Panel.

     3. Click System and Maintenance.

     4. Click Administrative Tools.

     5. Double-click Event Viewer.

To start Event Viewer by using a command line

     1. Open a command prompt. To open a command prompt, click Start,

click All Programs, click Accessories and then click Command Prompt.

     2. Type eventvwr.

Click on "Windows Log" and scroll down the middle panel until you see a red

"error" icon.

Click on the error icon and then you should be able to read how Bridge has

done you in.

Click the Copy button on the bottom of the Event Viewer and then post your

failure here for everyone to see, point to and giggle at.

Thanks.

Much like Kat Woman, I have no Bridge Errors.

What I do have is a "SideBySide" error.

Activation  context generation failed for "C:\Program Files (x86)\Adobe\Acrobat  9.0\Designer 8.2\FormDesigner.exe".Error in manifest or policy file ""  on line . A component version required by the application conflicts with  another component version already active. Conflicting components are:.  Component 1:  C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6 595b64144ccf1df_6.0.7600.16661_none_fa62ad231704eab7.manifest.  Component 2:  C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_659 5b64144ccf1df_6.0.7600.16661_none_420fe3fa2b8113bd.manifest.

Log Name: Application

Source: SideBySide

Event ID: 80

Level: Error

User: N/A

Logged 1/12/2011 12:53:53 PM

Task Category: None

Keywords: Classic

Chris

Well, ten days ago I again talked to my new best friend Ravi at Adobe Tech

Support in New Dehli. He apologized that Adobe Tech Support at the next

level up had not responded to me as promised. This time he had me shut down

most all Microsoft-related products and then reboot... no change. Bridge

still does not launch. He then kicked me over to his supervisor who again

apologized for the delay in response and promised that "the engineers" would

get back to me within two days. That was, I think, now approaching two weeks

ago. Still no response. I'll try calling again today.

Hi Ron and all other long suffering Bridge CS5 users,

I'm sorry to say that I'm also one of the huge number of folks whose Bridge CS5 won't open.

I'm running Photoshop CS5 on my Win 7 64-bit, 4GB RAM, 2.2GHz quad core Phenom system. Bridge worked fine until after the last update, but can't do anything with it now. I'm running Bridge CS3 for now, but as other have said, it's not really a workaround worth much.

Still running Ps CS5 64 bit without incident, as well as Lightroom 3 64-bit, again without any problems/incidents.

I don't run Norton (running Avast for anti virus software), so the only thing I think I have in common with other posts here is that it worked until the last update from Adobe. By the way, I have a 32-bit installation of Bridge CS5 at work and that's still running fine, but at work our networked machines don't have admin rights so it doesn't have the latest update - thi sdoes seem to be the root of the issue.

Hope this info might be helpful. Can't beleive there's no official comment yet from Adobe???!

just went down to two displays and bridge opened without restarting.  so did illustrator.    added displays back and things work fine again.  hrmmm...

Adobe are you listening?

I don't think the display "driver" is the issue.  The intersection between windows explorer and script found in the creative sweet common file create the issue.

And starting your computer in safe mode doesn't necessarily disable the driver.

Please answer my earlier posted questions and lets see if we can get this at least back to working for you.

What programs don't work?  What error are you getting?  What is your hardware and display config?  What is your software config?

Have you tried going down to one display  WITHOUT restarting but before you "launch" bridge?

I would agree with this Stradibarrius. I have only ever run a single

display, yet suffer the problem with Adobe Bridge CS5, 64-bit. Again,

like many others, I can use Bridge CS3 (32-bit of course) without

trouble, but 64-bit Bridge CS5 simply will not open and throws an error

to the error log. I get the same errors that others have already posted

to this forum.

I really miss having the Bridge CS5 functionality and this really

impacts my workflow rather negatively.

Lets hope the Adobe team are actually actively working towards providing

a practical resolution to this.

Thanks to all of you who are contributing to this thread. I think every

response helps to further refine the problem. Like Stradiberrius I too have

created a different user account in Windows, but Bridge will still not open

for me in the new user account. I still have not heard further from Adobe

Tech Support. I appreciate that this is a problem that may take some real

time to resolve as I also believe this is a serious flaw in the actual

program, but their seeming indifference evidenced by a total lack of

communication doesn't help. Even an email saying simply we're still trying

to resolve this would be appreciated.

Well I am glad that someone got a work around out of this. I have tried to figure out a painless way to transfer everything over but I haven't figured it out yet.

Adobe certainly is no help.

I will certainly think long and hard before I buy another version of Photoshop

Everyone needs to remember when Adobe releases CS6 and tries to get us all to upgrade.

I had this same problem but I think I have resolved it. In the Windows logsif indicated that the DLL SCCore.dll was at least part of the problem. I've run into this sort of error before when developing my own DLLs and it is usually caused be a mismatched DLL (the exe is trying to use a different version of the DLL). So I looked through my Photoshop folder and found the same file which was the same size but a different date. I renamed the SCCore.dll file in the Bridge folder, so that I had a backup, and then copied the SCCore.dll from the Photoshop folder into the Bridge folder. Bridge now works just fine. I think Adobe forgot to update the file in the Bridge folder.

Hopefully this will help others out as well.

By the way, I had the same issue with InDesign and following this same procedure also fixed InDesign.

Cheers!

Sure. Sorry I should have given more details.

First, the files I am referring to are found in the install directory of the 32

bit installation. This is usually C:\Program Files (x86)\Adobe for 64 bit Win7

and C:\Program Files\Adobe for 32 bit installs. Inside this folder is a

directory for each installed Adobe program, i.e. Bridge, Photoshop, etc.

Ok, so all you have to do is follow these steps:

1) Inside the Bridge folder ("C:\Program Files (x86)\Adobe\Adobe Bridge CS5" for

64 bit installs) you will find the file SCCore.dll. Rename this to something

else (I just renamed it to SCCore_old.dll). This is just a precaution so that if

something goes wrong you can get the original file back.

2) Go to the Photoshop directory ("C:\Program Files (x86)\Adobe\Adobe Photoshop

CS5" for 64 bit install) and find the same file (SCCore.dll). Right click on it

and choose "Copy".

3) Now go back to the Bridge folder and right-click on an empty area of the

folder and chose "Paste".

4) If you have InDesign or other Adobe programs that are not working you can

repeat these steps for them also.

That should do it. For me Bridge ran just fine and it seems to still be working.

I suspect that in an Adobe update the file was either not updated correctly or

for some reason Win7 wouldn't allow it to copied over (maybe a rights issue or

maybe it was in use at the time).

Let me know if you have any other questions.

Cheers,

-Brent

Ron,

Sorry to hear that. I was hoping that this would fix the issue for everyone.

This issue has happened to me twice on different machines. The strange thing is

that I have setup the programs on several other machines with no problems, so

it's an odd issue. I have a couple of questions if you don't mind that may help.

1) Have you looked in your windows log file to see what error is actually

generated? Maybe in your case, it's another DLL that is out of date.

2) Is it only Bridge that doesn't work for you or do other Adobe programs have

issues?

3) Make sure you are working in the 32 bit directories to copy the DLL.

I made some step-by-step instructions for another guy that I'll stick here as

well. Maybe that will help. I'm happy to help if I can. I've been very

frustrated with this issue as well. I even stopped using Bridge and started

using Picassa but it doesn't do exactly what Bridge does unfortunately.

Anyway, here are the step by step instructions:

First, the files I am referring to are found in the install directory of  the 32

bit installation. This is usually C:\Program Files (x86)\Adobe  for 64 bit Win7

and C:\Program Files\Adobe for 32 bit installs. Inside  this folder is a

directory for each installed Adobe program, i.e.  Bridge, Photoshop, etc.

Ok, so all you have to do is follow these steps:

1)  Inside the Bridge folder ("C:\Program Files (x86)\Adobe\Adobe Bridge  CS5"

for 64 bit installs) you will find the file SCCore.dll. Rename this  to

something else (I just renamed it to SCCore_old.dll). This is just a  precaution

so that if something goes wrong you can get the original  file back.

2) Go to the Photoshop directory ("C:\Program Files (x86)\Adobe\Adobe Photoshop

CS5" for  64 bit install) and find the same file (SCCore.dll). Right click on it

and choose "Copy".

3) Now go back to the Bridge folder and right-click on an empty area of the

folder and chose "Paste".

4) If you have InDesign or other Adobe programs that are not working you can

repeat these steps for them also.

Hope this helps,

-Brent