Premiere Pro 1.5 and msvcrt.dll – freezing on startup?

[Tim Kurkoski]

I haven’t had this problem myself, but have seen reports like this in various forums for Premiere and Photoshop and other applications.

The problem usually comes down to the fact that the msvcrt.dll (or msvcrt70, or msvcrt71, etc.) file is located in the WindowsSystem32 directory and some applications have a bad habit of copying their own version of the file in there. Premiere Pro has it’s customized version located in it’s own root directory (Adobe is smart enough not to overwrite system files), but if the DLL is already loaded into system memory, it’s probably not trying to launch it. Instead it ends up trying to use the actively loaded version, and crashes when it encounters a non-MS alteration.

Best bet is for you to get a clean copy of the Microsoft version of the file, from your i386 folder or Windows install disk, and copy it back in to the System32 directory.

[Derek Marazzo]

Timothy,

Thanks alot for info and recommendations. I’ll try to put a clean copy of the dll into the system32 dir. I didn’t realize that some programs use their own customized versions of the dll, but after doing a search I found a bunch of instances of it.

-Derek

[Derek Marazzo]

OK, I found the problem. Anyone having a similar problem should try this:

I did a search on c: drive for msvcrt.dll and found a few of them in a couple windows system folders – no problem with those. The other one I found was in an installed VST audio plugin (a freebie suite called VPP effects or something) Since Premiere Pro now supports VST plugins, launching PPro would load the vst plugins first and then try to load Adobe’s custom msvcrt.dll for Premiere after. The problem was that a msvcrt.dll was already loaded into memory from the vst plugin, thus creating the conflict. Got rid of that plugin and it loads correctly now.

– Derek