• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Error code 0xc000007b when opening After Effects

Community Beginner ,
Oct 09, 2020 Oct 09, 2020

Copy link to clipboard

Copied

Hey all, I'm receiving error code 0xc000007b in After Effects off a fresh install.  Based on the info here I tried playing whack-a-mole with the VC++ Runtimes but had no luck.

https://community.adobe.com/t5/after-effects/0xc000007b-error-upon-opening-adobe-ae-and-premiere-pro...

 

OS: Windows 10 64-bit

AMD Ryzen 7 3600x

NVIDIA RTX 2060 SUPER with driver 456.71

 

Any suggestions at all?

TOPICS
Crash , Error or problem

Views

610

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Community Beginner , Oct 11, 2020 Oct 11, 2020

Okay I found the solution!  In my case, MFPLAT.DLL was a 32x version installed, and it was crashing there (I'm on Windows 10 N 64x).

 

To update I needed to install the latest and greatest Windows Media Pack as directed here: https://support.microsoft.com/en-us/help/4562569/media-feature-pack-for-windows-10-n-may-2020

 

I found this out by using Dependency Walker.  If you have a similar issue this might help:

  1. Download and unpack the Dependency Walker x64 from the official website http://www.dependencywalker.com/
...

Votes

Translate

Translate
LEGEND ,
Oct 10, 2020 Oct 10, 2020

Copy link to clipboard

Copied

Without more specific info from your system event viewer we can't realyl tell you much. the usual applies: Start by reinstalling the programs with sufficient user privileges and also run them that way., check your system's drivers via device manager and so on, turn off security stuff that may block access. This literall can be anything.

 

Mylenium

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 11, 2020 Oct 11, 2020

Copy link to clipboard

Copied

Thanks for the response!  I'll try that.  What sort of information can I gather from the event viewer?  Is there a way I can gather specifics about the error and the failed dependency load?  (I'm a technical user if that helps)

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
LEGEND ,
Oct 11, 2020 Oct 11, 2020

Copy link to clipboard

Copied

At the very least the event viewer can tell you the crash module, sometimes extended info about drivers. just look for the yellow and red warning signs. For advanced debugging you can of course jnerd out and use tools like Sysinternals' Process Explorer specifically set to filter for the application executable. perhaps it's as trivial as a botched Registry key or a file being blocked by Windows Defender...

 

Mylenium

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Oct 11, 2020 Oct 11, 2020

Copy link to clipboard

Copied

LATEST

Okay I found the solution!  In my case, MFPLAT.DLL was a 32x version installed, and it was crashing there (I'm on Windows 10 N 64x).

 

To update I needed to install the latest and greatest Windows Media Pack as directed here: https://support.microsoft.com/en-us/help/4562569/media-feature-pack-for-windows-10-n-may-2020

 

I found this out by using Dependency Walker.  If you have a similar issue this might help:

  1. Download and unpack the Dependency Walker x64 from the official website http://www.dependencywalker.com/
  2. Run Dependency Walker, press File -> Open and select the problem game .exe file (not a shortcut);
  3. In the Module section, find the red error messages;
  4. Select problem dlls and look at the cause of the error;
  5. If the error is Error opened file. The system cannot find the file specified …, so the problem is that this library is missing;

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines