How do I disable the "Artificial Intelligence (AI) Host [etc]" feature?

Anonymous
2023-02-09T16:34:50+00:00

We have started getting complaints from our customers over this "feature" as it appears to be quite the resource hog, and of course they are blaming our add-ins.

Killing the ai.exe process appears to have no ill effect on the usability of Office programs such as Word, Outlook or Excel.

So I need to know how we can disable it. I'd prefer to give an instruction to our users on how they can switch off a feature they do not want, they feel they do not need, and that causes their old PCs to start sounding like a Harrier Jet taking off.

Thank you

Microsoft 365 and Office | Install, redeem, activate | Other | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer recommended by moderator
Anonymous
2024-02-07T21:10:13+00:00

This seems to work. There are all sorts of solutions put out there that involve things like editing the Registry. Here's a much easier fix that seems to have worked for me (and this is from The Geek Page https://thegeekpage.com/how-to-disable-the-artificial-intelligence-ai-host-feature/).

First, the obvious: delete the AI executables from the OFFICE folder:
ai.exe

ai.exe
aitrx.dll

Second - this is incredibly easy. Deleting the executables does not completely work because Office automatically updates itself with new copies of those files.

Since the AI Host runs when you use an Office app:
Disable the Office app updates.

To do this, open any Office application, like Word.

 Click the “File” menu and then the “Account” menu item - this may be under the "More..." menu item, in which case click "More..." and then click "Account"

 There, click on “Update Options”, which brings up a popup menu - on the popup menu, set that to “Disable Updates” to disable Office updates for all Office apps

Was this answer helpful?

20+ people found this answer helpful.
0 comments No comments

240 additional answers

Sort by: Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2023-05-31T00:24:23+00:00

    Thanks for this suggestion, this is the path I've taken ... rename the originals, create 0byte txt files, then copy the txt files as respective exe/dlls.

    Two extra steps I took was to disable permission inheritance on each of the four files in ProgramFilesCommonX86 and make "System" Read/Execute only by removing Full Control, Modify and Write permissions, and remove System completely in ProgramFilesCommonX64.

    Did this on 19/5/23 and ai.exe has not been running since but I'll wait for some Windows & Office updates to run to see if stopping or removing System from writing over the txt files will have the desired effect.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-05-31T01:08:17+00:00

    You should probably do the same for the x86 folder as well. I see what your doing, it might work. You can manually do the Office and MS updates instead of waiting as well... I don't have any patience, I wouldn't be able to wait.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-05-31T01:42:27+00:00

    You should probably do the same for the x86 folder as well. I see what your doing, it might work. You can manually do the Office and MS updates instead of waiting as well... I don't have any patience, I wouldn't be able to wait.

    Yeah ... didn't work. After the manual update the files were restored.

    Looks like we'll have to run regular checks and deletions as per scripts.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments