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 No 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 No 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 No comments

49 additional answers

Sort by: Newest
  1. Anonymous
    2021-03-08T20:51:04+00:00

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

    Regards,

    Alex Chen

    Which update?

    You shouldn't uninstall any updates, as we discussed above, it's a bug (probably), and I hope it will be fixed with future Windows or Office updates/patches.

    I agree with Ерунов Егор's advise. So far the error reported in the reliability log is a nuisance and nothing more. At this time, I don't see any issues with my Microsoft 365 subscription programs being affected. If they do become affected over time, that will be a different issue. I too expect this issue to be resolved soon. Backing out an update is not always an error free process in itself and can create more trouble that it solves.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-03-08T20:11:07+00:00

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

    Regards,

    Alex Chen

    Which update?

    You shouldn't uninstall any updates, as we discussed above, it's a bug (probably), and I hope it will be fixed with future Windows or Office updates/patches.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-03-08T19:48:11+00:00

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

    Regards,

    Alex Chen

    Which update?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments