Windows 10: EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update

Discus and support EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update in Windows 10 BSOD Crashes and Debugging to solve the problem; Log Name: Application Source: ESENT Date: 22-06-2020 22:48:18 Event ID: 642 Task Category: General Level: Warning... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by SayanSarkar95, Jun 22, 2020.

  1. EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update


    Log Name: Application
    Source: ESENT
    Date: 22-06-2020 22:48:18
    Event ID: 642
    Task Category: General
    Level: Warning
    Keywords: Classic

    User: N/A
    Computer: DESKTOP-8KJ8GNJ
    Description:
    Video.UI 3708,D,2 {AA19F9DB-4C01-4B62-9CB7-58A379E4707C}: 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.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    <System>
    <Provider Name="ESENT" />
    <EventID Qualifiers="0">642</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-06-22T17:18:18.7728124Z" />
    <EventRecordID>1588</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>DESKTOP-8KJ8GNJ</Computer>
    <Security />
    </System>
    <EventData>
    <Data>Video.UI</Data>
    <Data>3708,D,2</Data>
    <Data>{AA19F9DB-4C01-4B62-9CB7-58A379E4707C}: </Data>
    <Data>0x410022D8 8920 JET_efvAllowHigherPersistedFormat</Data>
    <Data>9080 0x2378</Data>
    <Data>1568.20.0</Data>
    </EventData>
    </Event>


    +System
    -Provider

    [ Name] ESENT
    -EventID642
    [ Qualifiers] 0
    Version0
    Level3
    Task1
    Opcode0
    Keywords0x80000000000000
    -TimeCreated
    [ SystemTime] 2020-06-22T17:18:18.7728124Z
    EventRecordID1588
    Correlation
    -Execution

    [ ProcessID] 0
    [ ThreadID] 0
    ChannelApplication
    ComputerDESKTOP-8KJ8GNJ
    Security
    -EventData

    Video.UI
    3708,D,2
    {AA19F9DB-4C01-4B62-9CB7-58A379E4707C}:
    0x410022D8 8920 JET_efvAllowHigherPersistedFormat
    9080 0x2378
    1568.20.0


    :)
     
    SayanSarkar95, Jun 22, 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, Jun 22, 2020
    #2
  3. Bree Win User
    Known and Resolved issues for Windows 10 May 2020 Update version 2004

    That's really odd. I get no ESENT errors in Home upgraded to 2004.....


    EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update [​IMG]


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


    EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update [​IMG]
     
  4. Brink Win User

    EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update

    Features removed and deprecated in Windows 10 version 2004

    Source:

    See also:
     
    Brink, Jun 22, 2020
    #4
Thema:

EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update

Loading...
  1. EVENT 642 ERROR SINCE UPGRADING Windows 10 version 2004 Feature Update - Similar Threads - EVENT 642 ERROR

  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. 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
  4. 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...
  5. 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:...
  6. Update Errors since Windows 10 version 2004

    in Windows 10 Installation and Upgrade
    Update Errors since Windows 10 version 2004: On June 13, 2020, my desktop computer updated to Windows 10 version 2004. Other than the widely reported ESSENT warnings flooding the event log, I have two persistent update failures. Here's the first one: Installation Failure: Windows failed to install the following...
  7. Multiple ESENT Warnings Event ID 642 post 2004 Upgrade

    in Windows 10 BSOD Crashes and Debugging
    Multiple ESENT Warnings Event ID 642 post 2004 Upgrade: 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...
  8. Multiple ESENT Warnings Event ID 642 post 2004 Upgrade

    in Windows 10 Network and Sharing
    Multiple ESENT Warnings Event ID 642 post 2004 Upgrade: 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...
  9. ESENT 642 errors after update to version 2004

    in Windows 10 Installation and Upgrade
    ESENT 642 errors after update to version 2004: I posted in another forum section as an additional responder in someone else's thread to having this problem. I am starting my own thread in this section hoping someone from Microsoft can respond with a fix. Since upgrading from 1909 to 2004 win 10 home 64 bit late on...
  10. Esent Event ID 642 warnings since updating to windows 10 2004

    in Windows 10 Ask Insider
    Esent Event ID 642 warnings since updating to windows 10 2004: [ATTACH] Anyone else seeing similar event id 642 warnings appear in event viewer since updating to windows 10 2004 (Version 10.0.19041 Build 19041) ? Clean install of windows, formatted ssd first (using usb stick). Some of the vent id 642 warnings that ive seen :...