The dvacore.dll issue is a particularly hard one to target in Premiere Elements (any version).
Just in case reference....
But, please take and look at the ups and downs and ups for the following thread, and then let us know
if any of the suggestions worked for you.
I tried the following listed in the article with no success.
Clearing out the preferences in the appdata directory didn't change anything, the my documents folder is mapped to my local C:\ drive, uninstalling and reinstalling doesn't change it either (including wiping from the registry). What does storing your my documents (mine is set to C:\ drive) on the network (H:\ or D:\) vs. local root c my documents folder have anything to with Adobe Premier Elements 12 launching?
Any other suggestions?
Thanks for the follow ups. Sorry that the news were not better.
I am not sure how worthwhile it might be, but here are some possibilities
a. create a new User Account with Administrative Privileges and try to install and run Premiere Elements 12 there.
b. Download and install a new set of Premiere Elements 12 installation files...or for 13 for that matter...
When you go this route, you need to read and carry out carefully the web page's "Note: Very Important Instructions"
in order to avoid an Access Denied message.
The history on the dvacore.dll is encouraging. But, please review and consider.
Please update us on your progress when your schedule permits.
Thanks for the suggestions. I have tried various administrative accounts, locally, domain admin, user accounts with administrative priveleges, but still the same result. I have not tried installing premier elements 13. Would my version 12 key work on version 13 files?
Thanks for the update. Sorry no resolution yet.
You cannot use your purchased Premiere Elements 12 serial number in Premiere Elements 13. Right now,13 tryout is being suggested as just a troubleshooting aide. If the error is gone, then you would have to decide whether or not to purchase a serial number for it.
Your 12 is beyond the Adobe period for 12 - 13 exchange. And, 12 is not longer the current version. Nonetheless, if you purchased from Adobe, then I would encourage you to contact Adobe via its Adobe Chat to explain the matter and ask for consideration, especially with the dvacore.dll issue being involved. I cannot predict how it will go on this matter. But worth the try.
We will be watching for further developments.
Thanks for all your help with this, I am still trying different graphics card drivers, testing in safe mode, testing different services and processes to see what is causing this crash. I checked with Adobe support and they don't have any chat or phone support for this product, which seems weird to me. I'll try version 13 just to test it, but even if it does work, I would like to get version 12 to work, since it was purchased.
Let us see how you do with version 13.
One way or another we could try to make contact with Adobe and its Adobe Chat, using an active Chat line even if its titles not
Membership, Account, Payment
Payments, Invoices, Orders
If the link does not hold its set, then you will need to navigate to the Chat Panel using the above titles as guides.
Looking forward to further developments.