Eventlog warnings ; ESENT id=642

Page 1 of 13 12311 ... LastLast

  1. Posts : 1,904
    Windows 10 Pro x64
       #1

    Eventlog warnings ; ESENT id=642


    Since the upgrade to latest Win10 version 2004 , Im getting these ESENT id=642 , after each reboot .
    Never seen before , any solution / idea how to solve these annoying warnings .........??

    Event Data ;
    Catalog Database
    4968,D,12
    Catalog Database:
    0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)
    9080 (0x2378)
    1568.20.0
      My Computer


  2. Posts : 12
    windows 10
       #2

    pietcorus2 said:
    Since the upgrade to latest Win10 version 2004 , Im getting these ESENT id=642 , after each reboot .
    Never seen before , any solution / idea how to solve these annoying warnings .........??

    Event Data ;
    Catalog Database
    4968,D,12
    Catalog Database:
    0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)
    9080 (0x2378)
    1568.20.0
    Same here, several each day. As well as lots of other warnings/errors. I clean installed 2004 using a usb stick, formatting the ssd first.

    https://i.imgur.com/jxRxwBL.gif


    cpu : ryzen 3700x
    motherboard : b450 mortar max
    16gb ddr4 ram
    crucial m4 ssd + crucial mx500 ssd
    2080ti graphics card
      My Computer


  3. Posts : 1,904
    Windows 10 Pro x64
    Thread Starter
       #3

    Could not find a solution , untill now !!
    Hope to get some more help from this forum ...........Im not the only one with this problem !

    Maybe Im too fast with this upgrade and better wait a few weeks more . ( windows bug ??)
    My eventlog is always clean in previous versions , this ESENT id=642 is new for me , never seen before !
    btw, still no solution found ............I guess there are much more people with this error.
    Last edited by pietcorus2; 29 May 2020 at 16:10.
      My Computer


  4. Posts : 12
    windows 10
       #4

    pietcorus2 said:
    Could not find a solution , untill now !!
    Hope to get some more help from this forum ...........Im not the only one with this problem !

    Maybe Im too fast with this upgrade and better wait a few weeks more . ( windows bug ??)
    My eventlog is always clean in previous versions , this ESENT id=642 is new for me , never seen before !
    btw, still no solution found ............I guess there are much more people with this error.
    Hi,

    I created a thread at reddit, seems to be a common issue.

    Esent Event ID 642 warnings since updating to windows 10 2004 : Windows10
      My Computer


  5. Posts : 1,904
    Windows 10 Pro x64
    Thread Starter
       #5

    I thought already on a MS-bug ........looks like we are too fast , but a lot of people have seen it , so a solution has to come soon !
    btw , I will roll back to previous 1909 , and then install again with the upgrade media ( Win-DVD) , see what happens.........

    Well tried to install with the media-DVD , gave me the same result ...............this annoying " id=642 " keeps coming back , my Logitech-webcam is not recognised also, to me its very clear now ; its one of the many stubborn MS-bugs !

    Lets hope MS will solve it soon............
    Im not in a hurry to upgrade anymore !
    Last edited by pietcorus2; 30 May 2020 at 06:36.
      My Computer


  6. Posts : 20
    Windows 10
       #6

    Yeah I created another thread down below and I think it also affects call of duty modern warfare. I don't know for how long I get these warnings, but after cod started crashing with no error, I saw in event viewer these warnings too (along the crash report).

    Any chance they associate with directx? Twice I got an error message and it said "directx encountered an unrecoverable error".
      My Computer


  7. Posts : 1,904
    Windows 10 Pro x64
    Thread Starter
       #7

    Just made a task for the eventviewer , which immediately, automaticly and invisible, removes these discusting bloatware ESENT id=642 logs from my eventwiewer , works perfectly !
    Gone (!) are these annoying logs , dont see them anymore .
    Will use this task untill a working solution for " ESENT id=642 " appears !!
      My Computer


  8. Posts : 25,075
    10 Home x64 (21H2) (10 Pro on 2nd pc)
       #8

    pietcorus2 said:
    Since the upgrade to latest Win10 version 2004 , Im getting these ESENT id=642 , after each reboot .
    That's really odd. I get no ESENT errors in Home upgraded to 2004.....

    Eventlog warnings ; ESENT id=642-2004-home-no-esent-errors.png

    ...or a clean install of Pro 2004 in a VM.

    Eventlog warnings ; ESENT id=642-2004-pro-no-esent-errors.png
      My Computers


  9. Posts : 1,904
    Windows 10 Pro x64
    Thread Starter
       #9

    " I get no ESENT errors in Home upgraded to 2004....."................you must be one of the very lucky few , coz lots of people have this " ESENT id=642 " in eventviewer !
    Still dont know the reason for these warnings , searching for a solution also.............no luck untill now !
    Most people dont even look in these logs , so they dont know ..........
      My Computer


  10. Posts : 6
    Windows 10 PRO x64
       #10

    Yes, I get this after every restart. It started after upgrading to 2004, which broke some of my programs too and had to reinstall.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:44.
Find Us




Windows 10 Forums