Skip to main content
Rick Whitehead
Rick Whitehead
Participant
May 12, 2026

Adobe express injects itself into the default browser and opens all local html files despite no permissions being requested

  • May 12, 2026
  • 1 reply
  • 41 views

I clicked the button “use design tools”  in Acrobat Pro by mistake and now Adobe Express has injected itself into the default browser and takes over whenever I try to open local HTML files. WTAF.
I was not warned/prompted for permission to make this change and there is no obvious way to remove this behaviour. I urge somebody at Adobe to provide a fix immediately. This is unacceptable. 

    1 reply

    Rose DV
    Community Manager
    Rose DVCommunity Manager
    Community Manager
    May 18, 2026

    Hi there ​@Rick Whitehead!

     

    Thank you for flagging this so clearly - I completely understand why this is frustrating!

     

    We've raised this with our internal team and are looking into it. In the meantime, could you share a few details to help us investigate?

     

    - What OS and browser are you using?

    - What version of Acrobat Pro do you have installed?

    - Have you tried uninstalling/reinstalling Acrobat Pro to see if that reverses the behavior?

     

    We'll follow up here as soon as we have more information. Thanks for your patience.

     

    Rose

    Rick Whitehead
    Rick WhiteheadAuthor
    Participant
    May 18, 2026

    Hi Rose DV,
    Thanks for your reply.  

    Mac OS Sequoia 15.7.4 (24G517) (Intel Core i9)
    Acrobat Pro: Continuous Release | Version 2026.00121529

    Architecture: x86_64

    Processor: Intel

    Build: 26.1.21529.0

    AGM: 8.0.1

    CoolType: 11.0.0

    JP2K: 4.0.2.54782

    I tried all the things that AI and the internet suggested including removing certain services which Adobe CS sets up behind the scenes.  Nothing worked for the original HTML file which still opens with Adobe Express in the browser, but sadly somewhere during my frenzied attempts I clearly removed something which prevented the same fate for new local HTML files.  I’m leaving things in that state as I can’t afford to waste yet more time guessing and I can’t afford to have express takeover like this. 

    I look forward to a resolution and will happily test once somebody has been able to reproduce and reverse this behaviour in the same environment. 

    Many thanks

    Rick 

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