Skip to main content
D
defaultrh3vqto36zjz
January 16, 2026
Question

Issues with Adobe DC Reader after WIndows 11 Update KB5074109

  • January 16, 2026
  • 2 replies
  • 1655 views

Hi,

 

I have a local application (ERP) that uses Adobe Reader / Browser Plugin to Preview the reports in PDF, after the WIndows Update Security KB5074109, it won't display, ssems that open the application, cause I see it in Task Manager and also sometimes I get the error "There is a problem with Adobe Acrobat/REader. If it is running, please exit and try again (507:507)"

2 replies

A
Anonymous
January 22, 2026

Hi, exactly the same issue for us. Our local ERP didn't display pdfs through Acrobat Reader IE activex.

Does anyone opened a support case for Adobe?

A
Anonymous
January 27, 2026

Same issue here. Rolling back the update resolves the issue but can't live like this forever. Hope it gets fixed soon. Microsoft has already released two out of band updates on the 17 and 24'th, either of these affect the issue?

    creative explorer
    Community Expert
    creative explorerCommunity Expert
    Community Expert
    January 27, 2026

    @31605642 at least it wasn't Adobe fault for breaking things this time around:
    https://cybersecuritynews-com.cdn.ampproject.org/v/s/cybersecuritynews.com/windows-11-update-breaks-systems

    m
    creative explorer
    Community Expert
    creative explorerCommunity Expert
    Community Expert
    January 18, 2026

    @defaultrh3vqto36zjz The update appears to have changed how Windows handles background processes or security permissions, causing Adobe's browser plugin to crash or remain active in the Task Manager without actually displaying the PDF. See KB5074109 from Microosft themselves! It's known and likely will be getting a patch for this — until then, you could roll back to the previous version or disable protected mode in your Acrobat preferences. Because security is an issue for me, I would personally roll back instead. 

    m
    A
    Anonymous
    January 20, 2026

    Same issue here and it's very impactful to the many of applications that we use. nowhere in microsoft does it indicate they know about this issue with the update along with the other several things update KB5074109 broke. 

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices