Removing older Copilot without affecting the current version

Brantner, Geoffrey 0 Reputation points
2026-08-13T16:02:24.35+00:00

I work in a completely Microsoft environment and the Microsoft search responses are false based on what I'm looking at. My search repeatedly tells me things like:

Rolling back or keeping multiple side-by-side iterations of Microsoft Copilot or its components is generally not supported. When you update the application or extension, the new version directly replaces the old one.

or:

  1. Windows treats Copilot as a single integrated application package rather than a multi-version stack.
  2. Standard updates overwrite previous files automatically, meaning old binaries do not linger on your disk.

This is false. In a 1K user environment, Windows 11 23H2 and 24H2, we have any number of devices with both the current version of M365 Copilot and an old version that now has a vulnerability. I need to safely remove the old version without affecting the new version, and every bit of information I can find from Microsoft about their own software tells me this doesn't happen. Well, here it is:

Copilot

If anyone can tell us how to safely remove the old version, while leaving the current version functional, I would truly appreciate it. Thank you for your time and assistance.

Microsoft Copilot | Windows Copilot | Copilot+ PC
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Carl-L 21,320 Reputation points Microsoft External Staff Moderator
    2026-08-14T06:36:21.7766667+00:00

    Hello Brantner, Geoffrey,

    Welcome to Microsoft Q&A forum.

    Cleanup process is asynchronous and best effort process, so leftovers of an apps can still remain. However, most of these folders are low risk and don't provide any vulnerabilities as long as the package is gone.

    To check if the old package still exists in the computer, you can type this command in an elevated PowerShell: Get-AppxPackage Microsoft.MicrosoftOfficeHub -AllUsers | Select Name, Version, PackageFullName and press Enter. However, I'd better just let it be even if the package is gone just to make sure nothing happens.

    I'm waiting for your reply.

    Was this answer helpful?

    1 person found this answer helpful.
  2. Carl-L 21,320 Reputation points Microsoft External Staff Moderator
    2026-08-18T14:02:03.5666667+00:00

    Hello Brantner, Geoffrey,

    Thanks for replying.

    Before uninstalling, I'd type Get-AppxPackage -AllUsers Microsoft.MicrosoftOfficeHub in an elevated PowerShell first to see if the package is still count as registered in Microsoft environment. If it still does, I'd unregister it first then proceed with the deletion.

    Feel free to let me know if you have any other questions.

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.