Eventlog warnings ; ESENT id=642

Zardoc · 04 Feb 2021

C & D updates are not security updates. They are mostly bug fixes. So if you have an issue with ESENT errors, then there is your bug fix. If you don't have issues with Windows, no need to install the update it should nevertheless be included in Patch Tuesday because not all of us run around looking for errors in our Windows.

Unlike a beta install which is sometimes more difficult to remove, You can also remove this update. But in my case it fixed the issue that has been nagging all of us in this post ESENT ERRORS GONE.

Eventlog warnings ; ESENT id=642-bug-fix-2021-02-04_09-20-24.png

steve108 · 04 Feb 2021

I still have singed hairs from a recent "preview" update, so ain't going there anymore - but I do appreciate everyone who does.

Also ESENT warnings are now like a familiar friend as I've had to ignore them for so long, so what's a few more days, months, years of ignoring them for me?

Nothing!

Garrett · 05 Feb 2021

Finally fixed, February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789). Addresses an issue that incorrectly logs Extensible Storage Engine Technology (ESENT) event 642 in the Application Event Log.

coolmistry · 05 Feb 2021

Garrett said:

Finally fixed, February 2, 2021—KB4598291 (OS Builds 19041.789 and 19042.789). Addresses an issue that incorrectly logs Extensible Storage Engine Technology (ESENT) event 642 in the Application Event Log.

Same here

erpster4 · 19 Feb 2021

Bree said:

... but this close to 'Patch Tuesday' it hardly seems worth installing. Like steve108, I'll wait for the 'real thing'.

then install KB4601319 (released Feb. 9, 2021) or newer CU, which also include the ESENT 642 bugfix
NUFF SAID! JUST DO IT - NO ANDs, IFs or BUTs! And NO EXCUSES

edit - I might create a custom built 2004/20H2 ESD/ISO install media that will include this bugfix (KB4598291, KB4601319 or better) so I won't worry about these ESENT errors showing up when clean installing Win10

Bree · 19 Feb 2021

erpster4 said:

Bree said:

.. but this close to 'Patch Tuesday' it hardly seems worth installing. Like steve108, I'll wait for the 'real thing'.

then install KB4601319 (released Feb. 9, 2021) or newer CU, which also include the ESENT 642 bugfix
NUFF SAID! JUST DO IT - NO ANDs, IFs or BUTs! And NO EXCUSES

You are replying to a post I made on 03 Feb 2021 at 20:07. The 'real thing' I was waiting for was the 'Patch Tuesday' KB4601319, to be released six days later - and yes, of course I have installed it

pietcorus2 · 19 Feb 2021

ESENT id=642 finally dissapeared from my system ..........now Im getting other ESENT infos ; id=326 , 300,301,302,102 and 105 !
Made a task for the scheduler ; " Application_ESENT_102 " , which starts the bat-file ; "clean eventlog ".
So when this shows up my eventlogs will be cleaned at once .............no worthless bull**** -info on my machine !

steve108 · 19 Feb 2021

pietcorus2 said:

ESENT id=642 finally dissapeared from my system ..........now Im getting other ESENT infos ; id=326 , 300,301,302,102 and 105 !
Made a task for the scheduler ; " Application_ESENT_102 " , which starts the bat-file ; "clean eventlog ".
So when this shows up my eventlogs will be cleaned at once .............no worthless bull**** -info on my machine !

One step forward and two back from the CU

pietcorus2 · 19 Feb 2021

" One step forward and two back from the CU

"........indeed !
Its only info ( no warnings/errors) , what to do with all these id=326, 300,301,102,105, etc..............wonder if there is a better way to get rid of this worthless info.....!!

steve108 · 19 Feb 2021

pietcorus2 said:

" One step forward and two back from the CU

"........indeed !
Its only info ( no warnings/errors) , what to do with all these id=326, 300,301,102,105, etc..............wonder if there is a better way to get rid of this worthless info.....!!

I only have about 40 in the last 7 days. How many do you have? I'm just going to ignore them.