CoPilot new version

Question

CoPilot new version

Erick Rodriguez 0

New CoPilot version got installed for me and I didn't ask for it, the new behavior is making communications workflow worse rather than better with the legend "Copilot said". Is there a way to roll back to previous version or delete this legend in the new version.?

0 comments

3 answers

Your answer

Answer 1

For Copilot on Windows, rollback to a previous app version is not supported in the provided guidance. The supported options are:

Uninstall the Copilot app.
- Windows 11: Settings > Apps > Installed apps > search for Copilot > … > Uninstall
- Windows 10: Settings > Apps > search for Copilot > Uninstall
Reinstall it later from the Microsoft Store if needed.
If the concern is preventing it from coming back in a managed environment, IT administrators can use AppLocker to prevent installation or remove the Copilot app. Microsoft recommends using AppLocker instead of the legacy Turn Off Windows Copilot policy, which is subject to near-term deprecation.

The provided documentation does not include a supported setting to remove a specific in-app legend such as “Copilot said” while keeping the app installed.

Also, if the app was automatically installed with Microsoft 365 Apps and then uninstalled, it is not automatically reinstalled again. Automatic installation happens only once.

Answer 2

Hi Erick Rodriguez,

I understand how frustrating it can be when an update changes a workflow that was working well for you.

At this point, I recommend that you review and try the steps provided in the AI generated answer on your thread. That reply typically include the most relevant checks for this scenario.

If there is no option to hide it in Copilot’s settings, I recommend submitting feedback directly through Copilot or the Windows Feedback Hub. Please include a screenshot and explain how the label affects your communication workflow, as this will give the product team clearer context for the request. Thank you so much for your understanding.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

Brantner, Geoffrey 0

This is not exactly the same thing, but is related and I'm hoping someone can offer some helpful info. 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:

Windows treats Copilot as a single integrated application package rather than a multi-version stack.
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:

User's image

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.

Vikki-T 10,015 Reputation points Microsoft External Staff Moderator

2026-08-14T12:14:59.41+00:00

Note: For your privacy and security, I have covered the personal information included in your post. Please avoid sharing any personal or sensitive information publicly, such as serial numbers, order details, email addresses, phone numbers, or case-related information.

Hi Brantner, Geoffrey,

Thank you for sharing these details and the screenshot. Since your concern involves removing a Microsoft 365 Copilot package across a managed business environment, it is different from the original issue discussed in this thread.

To avoid mixing the two scenarios and help your question reach the appropriate community experts, please create a new thread with the affected package names and versions, the Windows builds involved and any details reported by your security scanner.

Because this affects a large business environment, I would also recommend that your Microsoft 365 administrator contact Microsoft business support through the Microsoft 365 admin center. Please avoid manually deleting package folders, as this could affect the currently installed version.

Thank you for your understanding.