Skip to main content
G
gebali
Participant
August 6, 2025
Question

Bug: Duplicate Taskbar Icon Created When Using Virtual Desktops in Windows 11

  • August 6, 2025
  • 1 reply
  • 758 views

Product: Adobe Acrobat Reader (Continuous Release, 64-bit)

Operating System: Windows 11

Bug Summary: The application creates a persistent duplicate/ghost taskbar icon that does not correspond to an active window.

Reproducibility: The bug is 100% reproducible by switching to another virtual desktop and then switching back to the desktop containing the Acrobat window.

Key Diagnostic Proof: The bug is completely prevented by right-clicking the application in Task View (Win + Tab) and setting it to "Show this window on all desktops." This confirms the issue is a window management conflict with the Windows DWM during virtual desktop transitions.

Exhaustive Steps Taken: The bug persists after a complete removal using the official Adobe Acrobat Cleaner Tool followed by a fresh installation, confirming the issue is not related to local installation or profile corruption.

1 reply

T
Tariq Dar
Legend
August 6, 2025

Hi @gebali, 

 

 

Thanks for reaching out, and I appreciate sharing the relevant details.

We have a similar known issue, kindly check this discussion and let us know if you are experiencing the same issue: https://adobe.ly/4my78kY

 

Thanks for the support.

Best regards,
Tariq | Adobe Community Team

    G
    gebaliAuthor
    Participant
    August 6, 2025

    Hi @Tariq Ahmad ,

     

    Thanks for the prompt reply and for the other issue. The other issue probably stems from the same bug. It appears to be open for over 2 years with multiple users reporting the same issue until maybe a couple months ago and for different releases.

     

    Is Adobe ever willing to fix that bug?

     

    Anyway, we can close this issue and I will comment on the other one that I have the same issue, if that makes sense.

     

    Thanks!

    T
    Tariq Dar
    Legend
    August 6, 2025

    Appreciate the swift response, @gebali!

    I understand this issue has been open for some time. There are some technical bottlenecks that need to be fixed, but for the most part, we didn't have a reproducible case.  

     

    I will add the details to the existing bug with engineering, and we can keep this discussion as is. 

     

    Thank you for your patience and support.



    Best regards,
    Tariq | Adobe Community Team

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