Strange problem loading

[Seayn]

I have two computers on my network both running vista. Yesterday they both worked fine playing DDO. Today my main computer will not load DDO. I ckick the icon...it gets to the "opening main form" text and then just sits there. It never goes to the launcher window. For the life of me I cannot figure out whats wrong or whats different about the 2 computers as the second one loads fine. Any help would be appreciated. I don't think it is an administrator problem as both were working fine yesterday.

[Seayn]

http://http://turbine.fuzeqna.com/lotro.support/consumer/kbdetail.asp?kbid=1912&start=261

I this describes my problem and I tried the fix but it did not work. Still stuck at opening main form.

[RangerMaya]

I'm having the same problem. Of course, like one of the tech assistance people pointed out to me when I couldn't get the game to work after MOD 6, it's probably my fault. :mad:

[RangerMaya]

I looked in the launcher files and this is the error I'm getting:

*** Update Initialization Error 2/24/2008 10:53:45 AM
2/24/2008 10:53:45 AM
The update process could not be initialized. 2/24/2008 10:53:45 AM
2/24/2008 10:53:45 AM
System.Exception: Unknown error (0xc0000005) (0xC0000005) 2/24/2008 10:53:45 AM
2/24/2008 10:53:45 AM

I don't understand what can be different between now and when I played my game last night. I played, shut down my computer and went to bed. This afternoon, I turned on my computer and tried to launch the game.

Ater MOD 6 I couldn't run the game on my regular (administrative) profile so I created a standard user profile and reinstalled the game, and it's been working just fine until today.

[Altumus]

It's exhibiting some sort of memory issue by the looks of it, did you try copying the files from the backup folder into the main DDO directory and then try playing again?

[RangerMaya]

I was getting the error on my standard user account in Vista. So I switched over to my Administrator account and reinstalled DDO there (since I had removed it after the MOD6 update because it wasn't working) and now it's working from that account. </sigh>