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. Anonymous
    2023-08-25T04:31:02+00:00

    I shall take a look through the posts and look at the GPO option.

    The AD GPO blocking option should be confirmed with the domain users. I asked one of my clients if they wanted me to disable ai.exe using GPO and AV blocking and weirdly they said NO!

    The GPO policy I created was under "Computer Configuration", I wanted it network-wide here.

    If you want to include/exclude by user accounts you'll can create the same rules under "User Configuration" instead. Then a Domain Group called "Block ai.exe" would be created for users who want it disabled and the group added in Security Filtering for the policy.

    This is also useful if users change their mind and want ai.exe, so they would be removed from the group and after GPO propagation it "should" start working for them again.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-08-25T16:59:45+00:00

    Also - if you use group policy, you want to run GPUPDATE /FORCE from an elevated command prompt to apply the policy to the computer you have made the change on, or on the domain server with AD where you have edited the default domain policy for all computers. I usually reboot after. If on a domain - you probably need to reboot those computers to have them again login to the domain and pickup the changes... if you want immediate change. Otherwise they will pick it up eventually.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-08-25T17:17:56+00:00

    YRP_1161, Hi again. I suppose it depends on the environment, whats acceptable on the computers...what kind of organization.... whether the computer is business owned or personal. My approach is, if its business owned - the business has all say over what runs on them and how they are used. For obvious reasons - you really don't want employees just doing what they will or browsing all day long with the computers. If you are say, working with realtors... where they use their own computers, then yes - maybe let them destroy theire computers, UNLESS they are joined to company domains... I have learned that you really have to have rules with acceptable use of computers... though its hard to get a business to even draw up that form in the first place. If I have users infecting the computers all the time - on a domain, then its time to get into group poicy and restrict them.

    Now AI.EXE.... Ok we don't like it... we don't want it... we do not know what all it does or will be doing... Unless there is some good reason for an individual to need AI.EXE running... I will just take it out... the user never knowing. On business computers, to keep things stable... and I have done this on personally owned computers - and I explain this to the owner, what it is, why I dsiabled it... escpecially if the system is quirky or unstable... not an objection yet.

    IF... someday... we find we really should allow this to run??? If they develop some wonderful thing (its all.... "wonderful"...*gag*...) and this has to be available? Well... then we might need to remove the blocking we created...

    Thanks for the info on what can be donew in a mixed environment group policy.... that can be useful in the future if I run in to that need. Thanks! Appreciate you looking at that.

    I agree with you entirely,,, and not disagreeing here... its just my clients are all in a position where I don't think any of them understand what AI is and sure aren't using any... I do not know any AI users.... LOL.... if I do... they aren't affected apparently....

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2023-08-28T11:59:48+00:00

    Either it becomes easy to switch on and off the new Microsoft AI enhanced browser or it isn't. If it isn't easy to do and I'm not happy with it and I'll simply have to use another browser. That should have been baked into your decisions in the first place

    Was this answer helpful?

    0 comments No comments