This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
In the last several days I have noticed my laptop CPU fan blowing constantly. The culprit seems to be 4 identical processes using the same amount of CPU as each other continuously hovering at about 8-12%. This keeps the fan blowing 24/7.
The Task Manager shows the Process name as "Microsoft 365 and Office (32 bit)" and no Office applications are running. When I view the details the executable names are "odt____.tmp.exe" with the underscores representing some 3- 4-character hex value, e.g. C67A.
I can end the tasks but they come back after a time and the CPU fan turns on again.
What are these processes and can I turn them off?
TIA
BTW, I tried to include a screenshot, but the image upload doesn't work.
Processes in Microsoft 365 for setting up Office apps, redeeming product keys, and activating licenses.
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.
I am investigating the windows search service now also
Troubleshoot Windows Search performance - Windows Client | Microsoft Learn
Can any of you try to upgrade BIOS and see if the problem persists? And let me know if this works. Thx.
Our fleet of devices automatically update BIOS every time an update is released and this hasn't helped us. So far, we've had success with two of the previously mentioned approaches:-
We're waiting to see if either or both approaches are permanent of if the problem may resume, possibly as patch management or MDM tries to push further Office updates.
MS Support has told me that any support tickets need to be opened with their MDM department, not Intunes or Office. Our testing has shown it is the MDM checking to push updates that is causing this.
I opened a ticket with Microsoft - and after a very long wait - this was their response:
"Apologies for the late reply on this.
This seems to be a new known issue that is being reported by other users as well. Rest assured that I am already having our internal team check on this. I will let you know if we can confirm a working resolution as soon as possible."
I'm not resting.... or assured...