Bridge no longer starts

Report · Jan 14, 2019

Between yesterday and today, Bridge will no longer start. I'm using Windows 10. When I go to start it, I get a little chime but then nothing happens. I've gone through some online forums and have tried several solutions without success:

1. Made sure that there weren't other copies running in the background using the Task Manager.

2. Tried running as administrator

3. Uninstalled and reinstalled Bridge (twice, including using the Cleaner tool and rebooting before the 2nd reinstall)

4. Updated my graphics processor (nvidia)

5. Tried running using the both the nvidia and the integrated graphics processors

6. Tried one suggestion to ctrl-click on the icon but didn't get anything like what was described

I just started using Bridge and have spend several hours classifying and getting my tags up to date and would hate to lose this effort again.

Thanks, Keith

Report · Jan 14, 2019

go to control panel/administrative tools/event viewer/window logs/application

see if there is an app error for Bridge.

If there is select "copy as text" and post it here.

If not try creating a new user and try running Bridge from new user.

Report · Jan 14, 2019

Log Name:	Application
Source:	ESENT
Date:	1/14/2019 1:50:21 PM
Event ID:	916

Task Category: General

Level:	Information
Keywords:	Classic
User:	N/A
Computer:	Lenovo-Keith

Description:

DllHost (12848,G,98) The beta feature EseDiskFlushConsistency is enabled in ESENT due to the beta site mode settings 0x800000.

Event Xml:

	<Provider Name="ESENT" />
	<EventID Qualifiers="0">916</EventID>
	<Level>4</Level>
	<Task>1</Task>
	<Keywords>0x80000000000000</Keywords>
	<TimeCreated SystemTime="2019-01-14T18:50:21.201364400Z" />
	<EventRecordID>8212</EventRecordID>
	<Channel>Application</Channel>
	<Computer>Lenovo-Keith</Computer>
	<Security />

</System>

	<Data>DllHost</Data>
	<Data>12848,G,98</Data>
	<Data>
	</Data>
	<Data>EseDiskFlushConsistency</Data>
	<Data>ESENT</Data>
	<Data>0x800000</Data>

</EventData>

</Event>

Report · Jan 14, 2019

Look for a list list of services in windows and shutdown Superfetch and disabled its auto run setting.

reboot and you should be good to go.

Jim

Report · Jan 15, 2019

Jim, I tried that and still no good. Same result with getting the chime but no splash screen or startup. I've confirmed that superfetch did not restart. Any other ideas come to mind?

Report · Jan 15, 2019

Have you run the windows 10 program compatibility troubleshooter?

You can select Bridge 2019

Select trouble shoot program.

Also are you using a USB drive to store files? If so can you

disconnect it and try running Bridge.

Did the Esent error go away?

Chime is a hardware notification. Something weird going on,

Report · Jan 15, 2019

Can you go into task manager and see if you have a bridge.exe process

already running?

If you do, kill the process, reboot and try a relaunch of Bridge.

Report · Jan 16, 2019

Nope, no other bridge process but found this in the tools:

Fault bucket , type 0

Event Name: PCA2

Response: Not available

Cab Id: 0

Problem signature:

P1: Bridge.exe

P2: 9.0.2.219

P3: Adobe Bridge CC 2019

P4: Adobe Bridge CC 2019

P5: Adobe Inc

P6: 100

P7: 0

P8:

P9:

P10:

Attached files:

\\?\C:\Users\Keith\AppData\Local\Temp\PCW317F.tmp

\\?\C:\Users\Keith\AppData\Local\Temp\ACG320D.tmp

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAAC8.tmp.WERInternalMetadata.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAB17.tmp.xml

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERABC0.tmp.csv

\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERAC4E.tmp.txt

These files may be available here:

C:\ProgramData\Microsoft\Windows\WER\ReportArchive\NonCritical_Bridge.exe_a47124b18a5be9f53b6d476f34ad2ac7be33cc36_00000000_11aeb48a

Analysis symbol:

Rechecking for solution: 0

Report Id: 63bcfbae-7e93-4f7a-839a-b56ea2067d6d

Report Status: 2147491840

Hashed bucket:

Cab Guid: 0

Report · Jan 16, 2019

What is your DPI setting in windows 10?

Report · Jan 16, 2019

My resolution is 1920 x 1080, if that's what you're asking. I tried checking the box in properties for both "Program DPI" and also for "High DPI scaling override" and got the same results. Under the "Program DPI" option, I tried it with both the window and programs pulldowns.

Report · Jan 16, 2019

Meaning the selections in the Compatibility tab in the Properties for Bridge - not the Windows settings

Report · Jan 16, 2019

Can you delete Bridge, and reboot, Then....

Can you run a Microsoft program from the command prompt with elevated

privileges.

SFC/ scannow

Reinstall Bridge.

Something is buggered with your windows 1o OS

Jim

Report · Jan 16, 2019

Jim,

First, I want to tell you hoe much I appreciate the time and effort you've spent with me on my issue. It's commendable.

I did do the removal and reboot. SFC showed no issues. Reinstalled but still no luck. Just can't figure out what changed from day to day.

Keith

Report · Jan 16, 2019

What is weird is the chime when you try to run Bridge.

You could find and run a program called process manager and use a filter to trap all processes that use a wav file and maybe that would help.

Have you tried creating another user (with administrator rights) profile and running Bridge from the new user file.

Only other suggestion would be to run a program like Ccleaner to clean up your registry.

I hesitate to suggest it only because I don't know if you would break something else.

PCA 2 is called program compatibility assistant in windows 10

Find Program Compatibility Assistant Service and double click on it.

On ‘Startup Type’ click ‘Disabled’ and click ‘Stop’ button the ‘Apply’.

You can try that as well

Report · Jan 17, 2019

So I start the computer up this morning and it takes forever to boot - "Please wait.........". It finally starts and, before starting your new suggestions, I browsed through the display settings but didn't really change anything. I went to start Bridge to see if I got a new error message in the Event Viewer and the crazy thing started up and ran. I played around with it for about 15 minutes and it all seemed to work fine so I decided to reboot to see if it came back up. Windows wanted to update so I had no choice but to let that happen. Long story short - when it rebooted, Bridge started right up and I'm using it now. No idea what I might have done with the display settings except that, by opening them, I may have refreshed a connection. In any case, all looks well for now. Again, I appreciate you allowing me to tap into your expertise and taking so much of your time. I just wish I know what fixed it so you/we could put that information into our toolbox for later.

Thanks, again

Keith