Adobe Reader crashes after installing .NET Framework 4.0

[Inigo_S]

Hi,

After installing Microsoft .NET Framework 4.0 and restarting the computer, I click on Adobe Reader's shortcut on the desktop to open it, but a window appears with message title "AcroRd32.exe - Application error" and the following error message "Application error when initializing (0xc0000005). Click Accept to close the application." Does anybody know how I can solve this problem?

I tried the following:

I uninstalled Microsoft .NET Framework 4.0 and reinstalled Adobe Reader 9.0. I opened Adobe Reader and it worked perfectly. Then, I installed Microsoft .NET Framework 4.0 again and I opened Adober Reader again, but the same error window appeared. Next, I installed Adober Reader 10.1.4, but the same error appeared. Then, I installed SumatraPDF 3.1.2 and it works perfectly, but Adobe Reader continues showing the error message. Is Adobe Reader compatible with Microsoft .NET Framework 4.0?

[Test Screen Name]

You've mentioned two ancient versions of Reader. Have you tried the current version?

[Inigo_S]

No, I haven't. The current version doesn't support Windows Vista, it only supports Windows Server 2008 R2 (64 bit), 2012 (64 bit) and 2012 R2 (64 bit); Windows 7 (32 bit and 64 bit), Windows 8 (32 bit and 64 bit) and Windows 10 (32 bit and 64 bit), plus some MacOS and mobile apps.

[Test Screen Name]

Maybe your ancient OS is the problem.

[Test Screen Name · Accepted solution]

Hmm, I looked at the versions. .NET is one of the most commonly installed pieces of software in the world, with billions of users. .NET 4.0 was released in 2011 and made to work on Vista. Reader X is also used a lot, with hundreds of millions of installs, and was made to work on Vista too. I think we can probably assume that millions of people at one time ran both of these on Vista, and that the software hasn't changed in many years. But yours is the only report I can find.

So... clearly a crash is really happening, and those two piece of software are part of the puzzle. But there is more to it than that. Perhaps a third piece of software is interfering. Perhaps the system is damaged. Unfortunately, I can't offer much more than perhapses, and the rest of the world has pretty much moved on; we'd struggle to find anyone to try out this combination today. Given that Reader 9 works, and that Reader 9 and 10 are both equally unsupported, maybe it's easiest to stick with 9 and forget this ever happened,.