Windows 10: Event ID 642

Discus and support Event ID 642 in Windows 10 BSOD Crashes and Debugging to solve the problem; Since the update to 20H2, I get event ID 642 in a large number, one restart 26 times!!!. It is a Warning in the Event Viewer. Here are examples of the... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by NVFOX, Oct 30, 2020.

  1. NVFOX Win User

    Event ID 642


    Since the update to 20H2, I get event ID 642 in a large number, one restart 26 times!!!. It is a Warning in the Event Viewer. Here are examples of the text:


    Video.UI 18016,D,2 {C0DA2038-938C-4F3E-B7C4-FA7FE07F30CA}: 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.


    This one 5 times!

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------

    DllHost 12000,D,12 Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: 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.


    This one 6 times!

    -----------------------------------------------------------------------------------------------------------------------------------------------------------------------

    svchost 20468,D,15 Unistore: 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.


    This one 5 times!

    ------------------------------------------------------------------------------------------------------------------------------------------------------------------------

    SearchIndexer 2620,D,50 Windows: 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.


    This one 2 times!

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

    svchost 3052,D,50 SRUJet: 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.


    This one 2 times!

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

    svchost 3052,D,50 SRUJet: 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.


    This one 2 times!

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------------

    Catalog Database 6280,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.


    This one 2 times!

    --------------------------------------------------------------------------------------------------------------------------------------------------------------------

    DllHost 13128,D,50 Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: 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.


    This one 2 times!

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------

    I do not understand a number of things. No explanation what this is. No solution to eliminate the this. No help from MS. But MS created the texts, and that is all. The user is the dumb one to figure out!?


    And- NO, no new reinstallation to resolve this. I ran a batch file like this one:


    @Echo off

    date /t & time /t

    echo Dism /Online /Cleanup-Image /StartComponentCleanup

    Dism /Online /Cleanup-Image /StartComponentCleanup

    echo ...

    date /t & time /t

    echo Dism /Online /Cleanup-Image /RestoreHealth

    Dism /Online /Cleanup-Image /RestoreHealth

    echo ...

    date /t & time /t

    echo SFC /scannow

    SFC /scannow

    date /t & time /t

    pause


    No success, everything appears to be fine. is there any solution to this freaking warning?

    :)
     
    NVFOX, Oct 30, 2020
    #1

  2. Event id 642

    Hi Franco,

    I actually got these issues after installing 14986.

    Source: ESENT

    Event ID: 642

    Description:

    wuaueng.dll (3044) SUS20ClientDataStore: The database format feature version 8980 (0x2314) could not be used due to the current database format 1568.20.0, controlled by the parameter 1073741825 (0x40000001).

    Source: ESENT

    Event ID: 642

    Description:

    SearchIndexer (6972) Windows: The database format feature version 8980 (0x2314) could not be used due to the current database format 1568.20.0, controlled by the parameter 1073741825 (0x40000001).

    I think these issues have to do with someting which goes wrong in the update.

    The issue with the search indexer I think I fixed it by reindexing. but need a few more days to see if it's really fixed.

    The windows update database I'm working on..

    I have a thread going here
    about issues with 14986.

    Cheers Guido
     
    Guidouit venlo, Oct 30, 2020
    #2
  3. Eventlog warnings ; ESENT id=642

    " Can you share your temp fix so others can use it please ?"
    Here you go ;

    Logboek wissen.batApplication_ESENT_642.txt

    Attach this task to the id=642 .
    Place the batch-file in C:\
    In the txt-file ; change my name to yours and convert from txt to XML , try to import the task into your eventviewer .
    If this wont work , make your own task from the id=642 , after you placed the cleaning-batch into C:\

    Its an event-id task specified to delete the bloated, crappy "ESENT id=642 "
    The batch-file will clean all eventlogs , when its been triggered by ; id=642 .

    Maybe someone in this forum can change this batch-file to clean only the 642 ids , all other events will remain .
    My batch-file will be triggered only by id=642 event.

    good luck ! *Wink
     
    pietcorus2, Oct 30, 2020
    #3
  4. Franco F Win User

    Event ID 642

    Event id 642

    There is also:

    Livello Data e ora Origine ID evento Categoria attivit

    Avviso 06/12/2016 21:42:19 ESENT 642 Generale SearchIndexer (980) Windows: Non è stato possibile utilizzare la versione della funzionalit di formattazione del database 8980 (0x2314) a causa del formato del database corrente 1568.20.0, controllato
    dal parametro 1073741825 (0x40000001).
     
    Franco F, Oct 30, 2020
    #4
Thema:

Event ID 642

Loading...
  1. Event ID 642 - Similar Threads - Event 642

  2. 642 event error problems

    in Windows 10 Support
    642 event error problems: Hi everyone it seems that recent updates have started generating repeated 642 event errors. I sometimes fail to fully boot into windows, and occasionally I am experiencing random freezing. For example - I might leave my pc, and return after say 30 minutes, and be met by an...
  3. Event ID: ESENT 642 - Restarting Computer

    in Windows 10 Ask Insider
    Event ID: ESENT 642 - Restarting Computer: Has anyone else been having this issue? The event keeps popping up whenever my computer restarts itself. It's really annoying and after doing some attempted fixes based on the ol' interwebs, I cannot seem to resolve it. Past news states that Microsoft resolved this issue or...
  4. Windows 10 2004 vs 20H2 Event id 642 database format feature version 9080 warning

    in Windows 10 Installation and Upgrade
    Windows 10 2004 vs 20H2 Event id 642 database format feature version 9080 warning: Informative post. 2004 still has the silly event id 642. Dev 20H2 does not. Interesting. https://answers.microsoft.com/en-us/windows/forum/all/windows-10-2004-vs-20h2-event-id-642-database/393e41da-6d80-4f19-931b-634325b6fd4d
  5. WIndows 10 2004 Event ID 642 Warning - database format feature version 9120 could not be used

    in Windows 10 Installation and Upgrade
    WIndows 10 2004 Event ID 642 Warning - database format feature version 9120 could not be used: It has now been roughly 3 months since this issue surfaced. I have been searching for a resolution but the best I have come up with is ignore it SFC/DISM do not work. I have a very generic setup. I have not dug that deep but it would be great to know why this occurs...
  6. Fix Event ID 642 ESENT error on Windows 10

    in Windows 10 News
    Fix Event ID 642 ESENT error on Windows 10: [ATTACH]The Extensible Storage Engine (ESE), which includes the ESENT.DLL, has been included in all releases of Windows since Windows 2000 and it’s used by a […] This article Fix Event ID 642 ESENT error on Windows 10 first appeared on TheWindowsClub.com. read more...
  7. Event ID 642 - ESENT - "database format feature version 9180 0x23dc could not be used due...

    in Windows 10 Network and Sharing
    Event ID 642 - ESENT - "database format feature version 9180 0x23dc could not be used due...: Event Viewer shows me the following WARNING: Video.UI 12688,R,98 {6C7604E6-4685-473E-B030-2BE1EE829F6D}: 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...
  8. want to fallback to 1909 because of ESENT event id 642 but no windows.old folder.

    in Windows 10 Ask Insider
    want to fallback to 1909 because of ESENT event id 642 but no windows.old folder.: Hi, ESENT warning event id 642 making my OS stutter outta nowhere, tested it while watching movies as well, every time there was a stutter event viewer logged at least 2 ESENT warnings and gaming is a nightmare with very well timed stutters. I have tried disk cleanup,...
  9. Windows 10 2004 Event id 642 database format feature version 9080 warning

    in Windows 10 Installation and Upgrade
    Windows 10 2004 Event id 642 database format feature version 9080 warning: I have tried upgrades and new installs yet still get this warning message. My hardware is rather generic and only 2 years old so I would not think something like that would slip through the MS cracks. Guessing this will be fixed on the next patch Tues? Log Name:...
  10. Event display: Esent 642 Error ID?

    in Windows 10 Installation and Upgrade
    Event display: Esent 642 Error ID?: I have this error in the event display. Can anyone help me? Ereignisanzeige: Esent 642 Fehler ID?