Remove Copilot from Word

Hi Charlotte.

Mine is a private subscription, so there may be complications to yours I'm unaware of. All I can suggest is that your IT people look at the directions in Ian.L - MSFT's post on November 3, 2024, and which other MS posters in other threads have given too; it worked for me.

The next annoyance was dealing with the subscription. Other users have indicated success here (only with the help of Support!), and have "reverted" their subscription to the "Classic" version, that is without Copilot. That option was not available to me for some inexplicable reason. After a chat session with Support, then as they directed by a chat with Sales, I had to cancel my subscription with the promise that before expiry in mid Feb 2025 there will be an invitation email to renew, and the option of choosing "Classic" will be available.

As I said elsewhere - a convoluted waste of my time dealing with something that should not have been inflicted on me without me actively choosing it.

Are the ACCC on to it?

Microsoft put this **** Copilot on Word on my computer without my consent. This according to ACCC is highly illegally and Microsoft has the legal obligation to remove it. Three of my IT people tried to remove so how on earth with my limit computer knowledge going to remove this annoying ****?

How the hell is disabling updates an acceptable solution??

Does Microsoft prefer customers to stop getting any security updates than just letting them disable Copilot??
I will never use Copilot, plastering it everywhere without an opt-out is never going to convince me to use it, so stop pissing me off every time I open a Microsoft product and let me turn it off.

Even when I opt out of all connected services (which does prevent it from working), the bloody icon and prompting is still there!

I am so fed up with this I am genuinely looking into LibreOffice and an alternative to OneDrive so I can end my subscription.

Thank you!.

But why did it take so much annoyance, and then 2 hours this morning to find and apply a fix (perhaps temporary)?

No thanks to Microsoft for wasting my time.

Added note: it took a while for me to realise that running the second command took several minutes to complete - I had not noticed the background window opening, but once I was aware of it and patiently waited the problem was solved (for now). But I'm not overly happy about now missing some necessary updates to fix other glitches that appear at times.