I'm wondering if I should create a separate boot partition just for PE12 and Windows with no changes being made to it ever. Maybe that will keep any dll's from becoming corrupt.
After you determine if Adobe Chat's troubleshooting worked for you, then, since you have its attention, you should really ask for it's opinion on the above.
We will be looking forward to your results.
Thanks for reporting on your experiences with dvamarshall.dll et al.
Add On....Did you see this April 2014 Adobe Premiere Elements Forum thread
Saw that but his install would never run. Mine ran fine for two weeks, then poof, gone! So I wanted to find out what happened in the middle of seemingly nowhere. And his problem was never solved, so I thought I'd give it a go. All Chat would say that is was a corruption with a dll file. He couldn't/wouldn't tell me why replacing the dvamarshal.dll wasn't an option or why PE12 was so damn sensitive, just to try those two options.
Not sure I want to reformat and reload all my software and data in spite of how used to PE I am. Also not even sure how to dual-boot Windows 7 on two different partitions!
Thanks for the reply. I understand your concerns.
Have you tried the classical steps, as just in case measures, in spite of the Problem Signature data?
First...does the problem exist with or without the antivirus disabled?
1. Deletion of the Adobe Premiere Elements Prefs file and, if necessary, the whole 12.0 Folder in which it exists
Local Disk C
and in the 12.0 Folder is the Adobe Premiere Elements Prefs file that you delete. If that does not work, then you delete the whole 12.0 Folder in which the Adobe Premiere Elements Prefs file exists. Be sure to be working with Folder Option Show Hidden Files, Folders, and Drives active so that you can see the complete path cited.
2. If necessary...
a. If you can get into the program at any time, Help Menu/Sign Out (otherwise, skip this step)
b. Uninstall (Control Panel/Programs route)
c. free ccleaner run through (regular cleaner and registry cleaner parts) to get rid of leftovers from incomplete installs and reinstalls.
d. reinstall the program with the antivirus and firewall(s) disabled.
By the way, in order to work with MotionJPEG in Premiere Elements 12, did you have to download and install any codec packs that might be
contributing to the issue?
Sometimes unlikely suggestions hit the issue head on; sometimes not. Let us see.
I completely uninstalled the software, I went through the registry and hand deleted every reference to Elements. All folders and preferences were removed during the uninstall procedure. I reinstalled it and it still didn't work, even when I tried to run it from the PE Edit executable rather than the desktop icon. I didn't install any codecs to deal with MJPEG so I guess PE has them built in now.
And the most important thing is that it worked fine for two weeks and then stopped.
Well there's another hour+ I've put into this problem. For the record, I uninstalled PE12 again, removed all folders related to PE12 from all places I could find (I did not bother to go through the registry this time), found out how to run an installation in Safe Mode, and reinstalled PE12 in Safe Mode with networking.
I rebooted and ran it from the icon on the desktop, and it wouldn't do anything until I signed in (even though that's not what the warning says...it says I have 7 days but oh well). And when I signed in, I got the same exact crash message with the exception of the timestamp.
Which means my only option according to Adobe is format and reinstall Windows. Which will mean reinstalling about 25 separate pieces of software and all my data files just for this one issue.
Anyone have any experience running PE on a virtual Windows machine? It's either that or figuring out how to dual boot, because I really don't think I have the patience to rebuild this box from the ground up.
Thanks for the follow ups.
Please remind me, have you assured that the antivirus and/or firewall(s) are not involved by looking at the issue with and without them disabled?
In search for dvamarshall.dll solutions, I came across
My only experience with virtual machines and Premiere Elements 12/12.1 is related to
Windows XP Mode (virtual Windows XP Professional SP3 32 bit) that was a free download with Windows 7 Professional SP1 64 bit.
Premiere Elements 12/12.1 works fine in that virtual system. However, since XP is 32 bit system, I had myself a 32 bit application for the Premiere Elements 12/12.1 installed on the 32 bit operating system.
I did not disable my MS Security Essentials or Windows Firewall when I did the installation the first time and the installation and running of the software went fine. In Safe Mode there is no AV running and Windows Firewall doesn't really do anything anyway. The whole point is that the software ran fine for two weeks and then wouldn't run. AV and Firewall did not corrupt the dvamarshall.dll file which is removed on uninstall and reinstalled clean each time with no luck.
Going forward I will be deciding whether to try my hand at running PE12 in a virtual machine or getting another copy of Win 7 to load on a 2nd hard drive with only PE12 on it, and boot to that for video editing, saving all files and settings to one of my other drives. I'll will report back here when I've figured out which I'm going to do. I've never used VM before so that's an additional learning curve, whereas another copy of Win 7 is just money. One thing I will not be doing is formatting my HD and starting from scratch.
Thanks for checking in.
By the way, that solvusoft.com link seems like a complete BS site to me, trying to get you to download their exe file. I think people should seriously stop posting that link in these forums unless you have had a problem and fixed it using their executable. Every page on that site has the exact same instructions and a link to an executable file. Does NOT seem legit to me.
Thanks for the update.
Sorry that the informational link on dvamarshal.dll that I found in a Google Search did not serve its purpose in helping you. Previously I had not seen any negative feedback on this link and had no problems with it with regard to my antivirus and spyware removal computer programs. But, I will look into the history of the web site.
These dvamarshal.dll matters are particularly troublesome especially when they fall into the class where the program has worked before but not now.
We will continue to watch for further developments.