Bridge CS6 will not start in Windows 7

Question

Bridge CS6 (both 32 and 64) don't start in Windows 7. 
Bridge starts in Task Manager for a few seconds, but goes away.  No errors, no logs.
I have tried all the suggestions I've found within the forums, including checking settings,, temp environment variables, deleting C:\Users\[your user name]\AppData\Roaming\Adobe\Bridge CS6 (including the directory itself), etc.  No luck.   Adding a new user, then using it to start Bridge worked great, but that is not really a solution.  One added piece of info:  Bridge did recreate the above directory before dying, although it remains empty.  I haven't found any logfiles that might help understand how far it got.   Is there a log file or a registry setting that will enable detailed logging to help diagnose this?
I managed to gather a temp xml file that has some info that might help.  This file shows up for the few seconds when Bridge is running.
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
<OSVersionInformation>
  <WindowsNTVersion>6.1</WindowsNTVersion>
  <Build>7601 Service Pack 1</Build>
  <Product>(0x1): Windows 7 Ultimate</Product>
  <Edition>Ultimate</Edition>
  <BuildString>7601.17835.amd64fre.win7sp1_gdr.120503-2030</BuildString>
  <Revision>1130</Revision>
  <Flavor>Multiprocessor Free</Flavor>
  <Architecture>X64</Architecture>
  <LCID>1033</LCID>
</OSVersionInformation>
<ParentProcessInformation>
  <ParentProcessId>3996</ParentProcessId>
  <ParentProcessPath>C:\Windows\explorer.exe</ParentProcessPath>
  <ParentProcessCmdLine>C:\Windows\Explorer.EXE</ParentProcessCmdLine>
</ParentProcessInformation>
<ProblemSignatures>
  <EventType>APPCRASH</EventType>
  <Parameter0>Bridge.exe</Parameter0>
  <Parameter1>5.0.0.399</Parameter1>
  <Parameter2>4f5ec28e</Parameter2>
  <Parameter3>Bridge.exe</Parameter3>
  <Parameter4>5.0.0.399</Parameter4>
  <Parameter5>4f5ec28e</Parameter5>
  <Parameter6>c0000005</Parameter6>
  <Parameter7>000000000036ae49</Parameter7>
</ProblemSignatures>
<DynamicSignatures>
  <Parameter1>6.1.7601.2.1.0.256.1</Parameter1>
  <Parameter2>1033</Parameter2>
  <Parameter22>dca5</Parameter22>
  <Parameter23>dca5eef3eb4639786ac397e2f866e6e1</Parameter23>
  <Parameter24>cde9</Parameter24>
  <Parameter25>cde994f1594c84823c9c1be215d1d32c</Parameter25>
</DynamicSignatures>
<SystemInformation>
  <MID>C1C89176-2E22-457C-8B68-F9633BDBDBAB</MID>
  <SystemManufacturer>System manufacturer</SystemManufacturer>
  <SystemProductName>System Product Name</SystemProductName>
  <BIOSVersion>0303</BIOSVersion>
</SystemInformation>
</WERReportMetadata>
There is obviously something in my normal user's profile or environment that is getting in the way of startup.  Yes, my normal user is an admin. You (Adobe) have the code and the startup can't be that convoluted. Someone should be able to walk the code, figure out what things are checked between creating the above directory and the next externally detectable step (like creating a file in this directory or logging something into a log file), then reply here with a list of specific things to check.
I got into a chat with Adobe support several days ago, where I went through several steps of ensuring I was using a properly licensed version only to be told that he didn't know Bridge and asked that I call during the day on Monday. The sign off message to that chat was funny - they mentioned 24x365 support :-) Luckily, I've worked support in my past and I have a sense of humor.
I tried to file a bug form the web, but failed to navigate the amazingly bad support web experience of Adobe.com.  At one point, I had found a place to do it, pasted the above into that window, then tried to submit - I wasn't logged in.  So, I clicked the login link and got an error pop-up window with a bad-link error.  I came in fresh - logged in, then could not find that "report a bug" screen again.  Truly amazing.  But I guess, if you cannot report a bug, it doesn't exist - so congratulations on your bug-free products.
A suggestion:
Provide a simple link to report a bug that's not tied to a service plan.  It would simply be a way to tell you about problems with the hope that a solution could be provided in a future release - these can optionally be logged to the forums for community involvement.  I don't mind logging in to prove I'm a valid user.

Answer 1

Adobe staff has to browse these forums on their own time (I know that should be part of their job) so their visits are infrequent.
There are several sites to report bugs which seems to be counterproductive.   I think this one has the most support right now. http://feedback.photoshop.com/photoshop_family
And you are sure you are not running Bridge CS5 in the background?  You can only run one Bridge program at any one time.
In both the Mac and Win OS seems like the workaround to create a new user works frequently, but it is a hassle.  In your problem solving did you unistall everything then run the Adobe Script Cleaner? 
Although this is a stretch for this problem, but might search your uninstall directroy and see if there are any expired Adobe trials you have not uninstalled.  For whatever reason it can stop launch of Bridge "as you need to launch parent application at least once".  Apparently even though it is long gone it is still seeing it as "parent" program.  As I said it is kind of a stretch here, but you never know.
Good luck on this as I know it is extrememly frustrating and Adobe does have its communication problems. 
That is why it is important for the users to step up and start contributing to these forums with suggestions on what to try, thiings they have tried and worked or did not, etc.