Multiple ESENT Warnings Event ID 642 post 2004 Upgrade

I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

Thank you so much for responding. I can see where they might be a problem with the Windows.old folder and the new install. I will certainly keep an eyes out for the expiration time and let you know what I see. I have thoroughly tested my computers and the installed Apps and I have not encountered any problems but I did get a message about my account and all I did was click on Fix It and re-entered my password and it fixed. I did get two more updates after installing 2004. One was for .Net Framework and the the other was for Adobe Flash. All in all it went smoother than what I anticipated with all the problems I have read about. I will keep a close eyes over the next few days and if I see anything weird I will let you know.  Thanks a lot KenMel.

Respectfully,

Don

I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

Thank you so much for responding. I can see where they might be a problem with the Windows.old folder and the new install. I will certainly keep an eyes out for the expiration time and let you know what I see. I have thoroughly tested my computers and the installed Apps and I have not encountered any problems but I did get a message about my account and all I did was click on Fix It and re-entered my password and it fixed. I did get two more updates after installing 2004. One was for .Net Framework and the the other was for Adobe Flash. All in all it went smoother than what I anticipated with all the problems I have read about. I will keep a close eyes over the next few days and if I see anything weird I will let you know.  Thanks a lot KenMel.

Respectfully,

Don

I have the same problem with a clean install of 2004.  (No windows.old folder to delete) If its related to edge as some have suggested, could possibly be linked to the offer to install edge for windows 10, on completion fo 2004 install.

I installed EDGE a little over a month ago and I have been using it instead of Chrome when I need to open a second browser. Firefox in my default. My Windows.old folder is located on my C: drive with the other folders like User, Program Files etc etc. 

Keep us posted if you find a solution.

Regards don

I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

Thank you so much for responding. I can see where they might be a problem with the Windows.old folder and the new install. I will certainly keep an eyes out for the expiration time and let you know what I see. I have thoroughly tested my computers and the installed Apps and I have not encountered any problems but I did get a message about my account and all I did was click on Fix It and re-entered my password and it fixed. I did get two more updates after installing 2004. One was for .Net Framework and the the other was for Adobe Flash. All in all it went smoother than what I anticipated with all the problems I have read about. I will keep a close eyes over the next few days and if I see anything weird I will let you know.  Thanks a lot KenMel.

Respectfully,

Don

Hello,

My Windows.old file is now gone and I have noticed a considerable drop of the ESENT errors 642. I did a Disk Clean up but I am seeing only "one group"  of 6 ESENT errors containing these two below in that one group and they appear right after a restart. Does anyone have any idea what these could be or how to get rid of them? 

Catalog Database (2460,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).
 
Catalog Database (2460,D,50) Catalog Database: The database format feature version 9180 (0x23dc) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

Thanks

I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

I saw your post on my thread but thought I'd post my findings here just in case some only sees this one:

It's now 10 days since 2004 updated and the Windows.old folder was automatically deleted. My ESENT 642 warnings in event viewer have STOPPED. I cannot answer as to crashing apps and slowdowns but as far as the ESENT warning goes, I think this was the solution.

I'm a consultant to several dental offices and have upgraded them to 2004 and the latest Edge.  Every one is now getting a ton of the ESENT 642 errors with their main dental program crashing a couple of times a day.

Hello Steve,

I agree with you but I have noticed that after I do a restart I see one group of theme with 7 warnings. I asked about it and was told to ignore them. I do not know if you see the similar this. Now what MS needs to do is fix that damn Shared Experiences  in Settings that is giving a lot of people Toast Notifications that they need to fix their account there and also the problem with defrag. This 2004 version has been a nightmare.

Regards,

Don

same problem here:

Catalog Database (4372,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

any ideas how to fix event 642 ?

same problem here:

Catalog Database (4372,D,12) Catalog Database: The database format feature version 9080 (0x2378) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

any ideas how to fix event 642 ?

I do not know if you have gone beyond the 10 day grace period to roll back to 1909 but once your Windows.old file is removed you will see a big changed in the number of ESENT's  642 you get. What you will probably see is what you mentioned above and they will pop up just after you do a restart in one group of seven then you may see one or two singles after that. I did address this to one of the mods and was told to ignore them. Who know but there may be a complete fix coming out today on Patch Tuesday.

Regards.