Upgrade = same result. This means I'll have to roll back to a backup, undoing a half-dozen installs/uninstalls. Swell.

From the Sony Knowledgebase:
Clean Uninstall and Reinstall Instructions for Windows 7 (64-bit Editions)

Mike

Thanks a lot Mike. Unfortunately I had already done all that and a bit more and it had no impact. I tried it again anyway. Looks like it's restore to prior state.

Appreciate it though.

Try holding shift+ctrl when you start Vegas. This will prompt you to reset Vegas to defaults and clear its caches.

Note: You will loose any previous preference settings and will have to reconfigure Vegas.

Peter

You know, I was looking for those - had already tried combinations of shift, ctrl even alt. That didn't work either, but nice to know.

Now I'm on a mission though because it's downright weird -where are they storing state? I just rolled back to an 11/3 backup. That means of course that all of the C drive is completely different bits...and it still repro's! I can't see how that can mean anything except they aren't storing the prior crash state in either the registry or local app data or anywhere on the C drive at all. So I loaded up process explorer from sysinternals and I can see it reaching into the AppData\Local\ looking for saved files which seems to contradict that. But deleting those files has no effect.

My new hypothesis is that the software shell which obviously wraps Vegas and catches crashes is based on web stored state; admittedly wild but hard to explain otherwise. I don't store my project files in C drive, but it's not looking there and I don't auto open the last project in any case.

Wish I was getting paid to test this though. Problem is - I converted at least a couple of dozen projects to Vegas 11 so, while I do have all my Vegas 9 files, is not an attractive proposition. And I like Vegas 11 (not build 510/11 which is usuable for me) except for the crashes. But this is a good feature gone rogue in some weird edge case that test missed. And it's driving me nuts - all productivity lost.

Finding for test team: If I leave the Problem Report dialog up, Vegas 11 continues to load in the background and will eventually succeed. I can then even load and save a project. But with the next launch, the crash report from Hell reappears. No matter what way I get there or which of the two options I choose, Vegas will go down immediately - apparently in an orderly way based on what I see in Procmon, at least I see what looks like orderly and systematic file/reg key close operations, but without being able to debug I can't say for certain whether the app shutdown is from within the vegas exe or an external process kill by the rogue error reporting code.

Vegas saves all of the options info into a separate file which is not un-installed. That's why they tell you to un-install all Sony apps then some of the .net files which contain the options information that you selected for each Sony app. DVD-A 5.2 is also intertwined with the .net file.
JJK

SamAt said: "But wait - there's more. Uninstall/reinstall doesn't resolve it either, because (gasp) the uninstall code doesn't thoroughly clean up!"

It worked just fine for me.

Yeah but the big mystery here is that the entire c drive was restored to a prior point in time 6 weeks before this started and it still behaves that way. So where are they storing crash state? Also, the clean uninstall instructions are therefore incorrect.

But in any case: Killed the state stored in net location hypothesis - disabling network has no effect.

Only workaround so far:
Wait until Vegas 11 comes up in background.
Kill the error reporting task in Task manager.
Vegas is now usable.

However it will still return on next launch.

Perhaps there's been some kind of hardware failure in your system.
Might be a good time to start running some diagnostics like Memtest.

Bob.

Maybe a Windows System Restore to a point of time prior to the problem?

...Jerry

Disabled the crash reporting dll by flipping a setting in C:\Program Files\Sony\Vegas Pro 11.0\ErrorReportConfig.xml
Enabled = "No"

Vegas is running fine.

Does not explain:
1. Why the endless loop/Vegas thread kill is happening.
2. How the heck it survived a complete partition restore to 6 weeks earlier.

Boy, I would love to find out the gory details on this one, but doubt I ever will.

I'm going to restore back to my original point in time and do the same fix. I'll resume error reporting when I get a stable build.

Sam

That would be my normal first response. But I had done numerous installs/uninstalls and Windows didn't keep my restore point. So I had to restore back using a full partition backup which is as clean as it gets. I was actually a bit surprised I even had 11 installed on that date.

My current hypothesis is that some patch sequence has triggered this bug on my system. The first thing I did after restore was Windows Update. I also had to update my video drivers to accomodate an added Video card (to support GPU accelleration.)