Heartbeat Exe not working

Anonymous
2021-03-04T00:22:13+00:00

Faulting application name: OLicenseHeartbeat.exe, version: 16.0.13806.20000, time stamp: 0x601e33f7

Faulting module name: KERNELBASE.dll, version: 10.0.19041.804, time stamp: 0x0e9c5eae

Exception code: 0xc06d007e

Fault offset: 0x000000000002d759

Faulting process ID: 0x11f0

Faulting application start time: 0x01d71034c99d2236

Faulting application path: C:\Program Files\Common Files\Microsoft Shared\Office16\OLicenseHeartbeat.exe

Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll

Report ID: 1461e9dc-6097-****-****-b4406ef205e1

Faulting package full name:

Faulting package-relative application ID:

Hya all here is the information about this issue i have with the Office heartbeat Exe i would like to know 2 things what it does and why has it stopped woprking

Microsoft 365 and Office | Subscription, account, billing | For home | Windows

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
Answer accepted by question author
Anonymous
2021-03-10T15:40:48+00:00

16.0.13801.20182 is the problem - either upgrade to 16.0.13801.20288 or downgrade as I wrote below and have been working for 3 days without the error.

Was this answer helpful?

7 people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2021-03-10T15:36:05+00:00

This has NOTHING to do with Windows updates.

This is caused by the "Office 16 Click-to-Run Licensing Component" and its latest update to version 16.0.13801.20182 or later.

Rolling back to version 16.0.13530.20528 (aka "Version 2012") will solve the problem.

See below I have been error free since the downgrade after 3/7/21

Was this answer helpful?

7 people found this answer helpful.
0 comments

49 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2021-03-08T12:40:46+00:00

    Hi,

    I can confirm that running SFC and/or DISM has absolutely no effect on this error. As far as i can tell, it is a common problem, appearing on systems with Office 2016 installations and all more recent versions of Office. It does not seem to be related to any Windows updates but updates to Office itself.

    Hope this helps...

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2021-03-08T08:35:33+00:00

    Hi All,

    Seems like this Kernelbase.dll is the root cause behind this issue.

    For every user who has been impacted by this issue, please check if your kernelbase.dll version is 10.0.19041.804.

    The Kernelbase.dll will be found at the following path:

    C:\Windows\WinSxS\wow64_microsoft-windows-kernelbase

    Right Click on it > Properties > Details:

    Meanwhile, as many users have mentioned, this issue start after the recent Windows updates. Please kindly attach your Windows Build version as well.

    If it's convenient for you, you could also revert the Windows update at Windows update > View update history >Uninstall Updates.

    Regards,

    Alex Chen

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  3. Anonymous
    2021-03-08T00:15:31+00:00

    Ya I am receiving the same errors for the last several days. On 3/4 it appears that some Office updates or reconfigurations were pushed by Microsoft and they were completed successfully, but every day after that overnight (likely when my system either checks for updates or does maintenance) it lists this error for the Heartbeat - appears to me to be a Microsoft-caused issue due to poor QA.

    I'm running Office 2019 if it matters.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments