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)
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 features that help users manage their subscriptions, account settings, and billing information.
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.
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.
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
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.
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
Greetings Alex - so let me try to answer your inquiry -
* For the kernelbase file - I actually have (3) of those folders you referenced (all 3 are a little longer than what you referenced) - each version has a kernelbase.dll file in it - each is different - the bottom-most folder (dated 2/28/21) does have the exact version you referenced (newest).
Windows build:
I recently had the 20H2 version installed, but I was experiencing hard-lockups randomly like some others have reported here on this website (I can dig up the thread if needed for research, just let me know if you need it) - so I rolled back to the 2004 version that had been flawless up to the point of upgrading to 20H2 and since the rollback to 2004 I have had no more lockups (don't know if the two are related, but I doubt it since others with 20H2 are also reporting the issue here), but I did start noticing these crashes with Office in the Reliability Monitor report and so started digging into it.
Hope this is helpful, if you need more information, feel free to ask.
Has anyone tested to see if this problem was resolved on their computer after Patch Tuesday yesterday? In my case patching is delayed a week so I have nothing new to report.