Skip to main content
April 25, 2014
Answered

unknown software exception (0xc0000409) occurred in the application at location 0x0041240b

  • April 25, 2014
  • 3 replies
  • 107308 views


Good day,

Whenever I select an Adobe PDF file (not actually opening it) or if I actuall do open it, I always get this delaying error display: "The exception unknown software exception (0xc0000409) occurred in the application at location 0x0041240b". If it displays the error if you click Cancel, or Ok, it closes the PDF, and you need to reopen it, at which the second attempt it does not display the error message. Anyone have an idea what may be causing this?

OS: Windows XP SP2

Adobe Reader Version: 11.0.0.6 (be advised that this problem has be persistent in many versions since V10.00)

This topic has been closed for replies.
Correct answer Ancient_Brit

OK. I have a workaround for now. @~graffiti posted elsewhere:

"Can you start up Reader after you get the error?

If so, go to Edit>Preferences>Security (enhanced)>Sandbox protections and deselect Enable Protected Mode at startup. See if that clears it up."

This worked for me. Hopefully Adobe will fix the issue by the next release.

3 replies

Participant
March 30, 2022

Issue persists in current 32 bit version of Adobe Acrobat running on Windows 8 (work environment)

Solution seems to still work.

 

Thanks Ancient Brit!

I love I can always rely on decade old fixes like this!

Participant
January 18, 2018

Worked for me, too.

Thanks!

pwillener
Legend
April 26, 2014

Reader 10 and 11 are not supported on Windows XP SP2; it needs at least SP3 (for the 32-bit version that is).  See http://get.adobe.com/reader/enterprise/

Ancient_BritCorrect answer
Participant
August 10, 2014

OK. I have a workaround for now. @~graffiti posted elsewhere:

"Can you start up Reader after you get the error?

If so, go to Edit>Preferences>Security (enhanced)>Sandbox protections and deselect Enable Protected Mode at startup. See if that clears it up."

This worked for me. Hopefully Adobe will fix the issue by the next release.

Participant
May 14, 2020

It also worked for me. Thanks for the info.