Multiple ESENT Warnings Event ID 642 post 2004 Upgrade

Anonymous

Today 6/9/20 I got the update for Win 2004 along with several other updates. I installed the patch Tuesday updates before installing the Win 2004 update with no problems. I then installed Win 2004 update and I had no problems with it and after testing things on my computer everything seems to be ok but I have run across in my Applications Event Viewer multiple ESENT Warnings Event 642. I do not seem to have any performance problems but who is to say that this will eventually cause some. The same thing happened when I upgraded to 1903 which was fixed by creating a TileDatabase folder by doing the below:

C:\WINDOWS\system32\config\systemprofile\AppData\Local\
(You may have to click on “Continue” when prompted.)
Once you are in the above mentioned location, right click and create a new folder and rename it as TileDataLayer
Double click on the TileDataLayer folder and inside the folder create a folder and name it as Database

I restarted my computer and they are still there. It would seem MS should have learned from it previous mistakes and fixed this before sending out another upgrade. I am not the only one experiencing this flood of warnings as there as many others who have upgraded the computers to this bug infested updated. MS needs to be aware of this and just take a look at it and realize this is a bug and it needs to be fixed. People are losing faith in MS and their products and this should have been caught and fixed while in testing. THIS is a MS bug and MS needs to address it and come up with a fix either in an update or instructions to users on how to fix it..

Log Name: Application

Source: ESENT

Date: 6/9/2020 4:00:00 PM

Event ID: 642

Task Category: General

Level: Warning

Keywords: Classic

User: N/A

Computer: DESKTOP-

Description:

svchost (4828,D,22) SRUJet: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

Event Xml:

<Channel>Application</Channel>

<Computer>DESKTOP- </Computer>

</System>

<Data>svchost</Data>

<Data>SRUJet: </Data>

<Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data>

</EventData>

</Event>

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

56 answers

Anonymous

2020-08-17T07:29:28+00:00

I agree it isn't bad hardware, if it's only 2004 doesn't like it.

It's pretty quick to try the clean boot. I would try that first because it prevents processes & services from starting automatically in the background (whether you run the app or not).

My 1st try at 2004 through Windows Update became very unstable very quickly. My 2nd try through an upgrade-install from a USB Installation drive was stable, but eventually Search would not work when clicked on the Taskbar or in a File Explorer box. No fix would fix it, not the troubleshooter or a reset from an app downloaded from MSFT.

I did a repair-install yesterday/so, & all looks great. I think it's worth a try for you too. It could just be 2004 has installed badly the first time. I'm unsure it makes a difference, but, if you make the USB drive today, it starts off as OS Build 388. By the end of the repair process, you will be 450.
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-17T06:47:34+00:00

I have already done a hardware test and if I boot it into a different operating system (linux or Windows Server 2016), its working fine, have also tried running it barebones and I always have the latest drivers its an MSI H61M-P3 (G3) (MS-7788), I7-3770, 16gb Ram, whilst still an old machine by todays standards it still does the job when its working properly, like i said it can work fine for several hours and then just die, doesn't matter what apps are running and i have also checked for things like memory leaks etc.

Personally I don't think its a hardware or bios problem. I don't use the onboard graphics card as I have a NVidia GT-740 which is perfectly adequate as I don't tend to run games on the pc.

Its only started doing it since the latest version of windows 10 2004, (OS Build 19041.450).

So I am thinking there is something in there that the computer doesn't like lol
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-17T06:26:25+00:00

(1) You should back up your user files & downloads to external media &/or onto OneDrive, in case the end is near for that computer.

(2) Maybe do some hardware tests that may be in your BIOS or at the site of your computer. What System Model is it in MSInfo32(type into Search)? That can be Googled for possible driver updates as well as diagnostic tests.

(3) Try the clean boot, then maybe the repair-install, as I posted above.
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-17T06:07:22+00:00

Not that it helps much, but I have also started to get the Green screen of death, and my pc reboots, everything is fine for a few hours, it can be quite frustrating at times. There is nothing in the event logs to show why the system is rebooting either. Done the usual things to solve this type of issue but I cannot catch the error message on the screen of death as it doesn't stay on for long enough.
Was this answer helpful?

0 comments No comments
Anonymous

2020-08-17T05:48:20+00:00

(1) Forget the ESENT errors. It doesn't cause all that & probably causes nothing at all. I've got them too.

(2) Try a clean boot to see whether File Explorer & all else improves. If so, it likely is a 3rd-party app causing the problems. If you can't guess which one, there is a procedure to follow to track it down...

https://support.microsoft.com/en-us/help/929135/how-to-perform-a-clean-boot-in-windows#:~:text=1%20Sign%20in%20to%20the%20computer%20as%20an,select%20System%20Configuration%20from%20the%20results.%20See%20More

How to perform a clean boot in Windows

(3) If a clean boot fails to improve it, then likely it is Windows itself the culprit. And things sound bad enough to me to go straight to the big guns. Just before a clean install, try a repair-install. I just did one for something else, & it worked beautifully. It keeps files, apps & settings.

(a) Turn off Controlled Folder Access at "Defender, Virus & Threat Protection, Manage Settings, Manage Controlled Folder Access", if you ever had turned it on. Otherwise, it will interfere near the end of the upgrade/repair-install.

(b) Make a Win 10 Installation USB drive here...

https://www.microsoft.com/en-us/software-download/windows10

Download Windows 10 -- currently, this is version 2004

You download the MediaCreationTool2004.exe, plug in an 8 GB USB drive, & double-click the tool to run. It could take up to 2 hours, but will create bootable media that could be used to clean install Windows, if the repair-install is ineffective. But for the repair-install, just open the Installation USB drive in File Explorer, & click Setup.exe. That could take another 2.5 hours to complete.

Good luck with it.
Was this answer helpful?

1 person found this answer helpful.

0 comments No comments