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-11T07:47:06+00:00

    Hello,

    I have a french Windows 10 Pro version 2004 build 19041, and Office 16 Pro Plus build 13801.20266 (so > 20182 previously said to be the problem, but < 20288 said to be the solution). My updates are set to automatic, so i don't know why i haven't 20288.

    Should i force update ?

    I have also Visual Studio 10 and debugger settings launching debugger on exceptions.

    So, often, some times after startup, my debugger is launched due to OLicenseHeartbeat exception : KernelBase.dll!00007ffe5c3cd759()

    00007FFE5C3CD72B mov eax,0Fh

    00007FFE5C3CD730 lea rcx,[rsp+40h]

    00007FFE5C3CD735 cmp r8d,eax

    00007FFE5C3CD738 mov rdx,r9

    00007FFE5C3CD73B cmova r8d,eax

    00007FFE5C3CD73F mov dword ptr [rsp+38h],r8d

    00007FFE5C3CD744 shl r8,3

    00007FFE5C3CD748 call 00007FFE5C431E77

    00007FFE5C3CD74D lea rcx,[rsp+20h]

    00007FFE5C3CD752 call qword ptr [7FFE5C55FB08h]

    HERE -> 00007FFE5C3CD759 nop dword ptr [rax+rax] 

    This is called from OLicenseHeartbeat :

    00007FF759284B0F lea rax,[rbp-50h]

    00007FF759284B13 mov qword ptr [rbp+30h],rax

    00007FF759284B17 call 00007FF7592848F4

    00007FF759284B1C xor edx,edx

    00007FF759284B1E lea r9,[rbp+30h]

    00007FF759284B22 mov ecx,0C06D007Eh

    00007FF759284B27 lea r8d,[rdx+1]

    00007FF759284B2B call qword ptr [7FF75928B1E0h]

    HERE -> 00007FF759284B31 mov rax,qword ptr [rbp-18h]

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-03-11T02:17:08+00:00

    Hi All,

    Thanks so much for the effort here.

    Once I thought this issue could be related with the Windows updates, because the impacted users are using different Office Installations, 2016/2019/365.

    And turn out to be wrong. Really sorry about that.

    As Ryan suggested, if you update your Office suite to build 16.0.13801.20288, this issue seems to be resolved. Please try updating it on your side, and post back here if you have any further information.

    For the Office 2016 users, please notice, there are 2 different installation of Office 2016, one is called **MSI (Microsoft Installer)**and another is C2R (Click to Run). As far as I can tell, the issue is currently impacting the C2R users. However, if the MSI users are also seeing this issue on your side, since the MSI Office 2016's update is combined with the Windows OS updates, there is no direct solution to this.

    Regards,

    Alex Chen

    Was this answer helpful?

    0 comments
  3. Anonymous
    2021-03-10T20:41:47+00:00

    I just did the update also. Will see what happens overnight.

    Was this answer helpful?

    0 comments