Help Fix event 642 [SOLVED]

I had my settings on 'deferred feature updates', but in June my Windows just went and installed the 2004 update all by itself when shutting down one day, no warning, nothing.

Now I can't even find the 'deferred feature updates'-setting.

I thought you could defer the feature update by 6 or 12 months, right? Or at least in the past.

I don't experience a real slow down somewhere, but I get random crashes/reboots, sometimes while gaming but other times just browsing the web and watching a stream or something.

With a heavy system load, I get it, I just update my drivers. But when just doing some minor load? Really?

And the 'event 642' error is always present (that's what got me here).

My biggest issue, my Windows always gets unstable after a feature update. EVERY. TIME. Not just some minor inconveniences here and there, no no, crashing applications and/or the OS.

I always delay the feature update, and when time comes, I'll just format and do a clean install. But not this time apparently.

Oh, and by the way, the only real feature that would actually help me, is two graphics settings called 'Hardware accelerated GPU scheduling' and 'Variable refresh rate'. These settings should help with stuttering a stream or video on my second monitor while gaming on my primary.

But instead it **** everything up. The stuttering was worse than before the feature and I had to disable these features to even be able to implement my own workaround fix again (that actually works!).

Sorry for my rant.

The only way to protect your self from Microsoft totally messing your machine is to make an image backup of the System.

You can do this easily with free software from Veeam, using their Windows Agent for Windows free edition and backup to an external SSD.

If you should always partition your drive in a C drive + Data drive, so when you image and restore is will take 15-30min, not hours.

Most machines are not partitioned, and you have at least 50 - 150 GB or more to backup and restore. 

If you keep your C drive for Windows and programs, put all your data on another partition and you can quickly backup and restore just the sytem partitions.  Its the only way to recover a machine that has lots of stuff installed and configured.

I have used Veeam products for years on Servers for VMs and desktops. It works all the time!

Ditto same thing except it disconnects  my Ethernet connection.

The warning in EVENT ID 642 should have no effects to your system and could be ignored.

If you're experiencing issues with Windows (2004), you should investigate the computer beyond this warning.

The warning also seems to be fixing itself; so it might be all fixed after running Windows 2004 a couple of days.

You can filter your logs and tick ESENT as source if you're interested in the events, but I don't think it has any effect in performance or that it causes freezes.

---

Log Name:      Application

Source:        ESENT

Date:          2-9-2020 13:06:55

Event ID:      325

Task Category: General

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      XXXXXX

Description:

svchost (16476,D,35) DS_Token_DB: The database engine created a new database (1, C:\WINDOWS\system32\config\systemprofile\AppData\Local\DataSharing\Storage\DSTokenDB2.dat). (Time=0 seconds) 

Additional Data: lgposCreate = 00000001:0001:0268,

dbv = 1568.110.240 

Internal Timing Sequence: 

[1] 0.000159 +J(0) +M(C:0K, Fs:2, WS:8K # 8K, PF:4K # 4K, P:4K)

[2] 0.002135 -0.000051 (1) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:3480/2) +M(C:0K, Fs:2, WS:8K # 8K, PF:0K # 0K, P:0K)

[3] 0.007374 -0.000003 (3) WT +J(0) +M(C:0K, Fs:13, WS:44K # 48K, PF:44K # 48K, P:44K)

[4] 0.009379 -0.007728 (1) WT +J(0) +M(C:0K, Fs:56, WS:220K # 272K, PF:88K # 88K, P:88K)

[5] 0.001397 -0.000152 (2) WT +J(CM:0, PgRf:3, Rd:0/0, Dy:3/6, Lg:122/4) +M(C:8K, Fs:36, WS:140K # 84K, PF:156K # 156K, P:156K)

[6] 0.005940 -0.002222 (1) WT +J(CM:0, PgRf:249, Rd:0/0, Dy:16/428, Lg:28550/465) +M(C:56K, Fs:109, WS:432K # 432K, PF:748K # 744K, P:748K)

[7] 0.002927 -0.000342 (4) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:4096/3) +M(C:0K, Fs:3, WS:8K # 12K, PF:0K # 4K, P:0K)

[8] 0.000013 +J(0)

[9] 0.025791 -0.024688 (4) WT +J(0) +M(C:-32K, Fs:5, WS:-16K # 8K, PF:-32K # 0K, P:-32K)

[10] 0.033498 -0.010918 (24) CM -0.023889 (31) WT +J(CM:24, PgRf:381, Rd:0/24, Dy:10/90, Lg:12509/130) +M(C:16K, Fs:24, WS:92K # 68K, PF:36K # 4K, P:36K)

[11] 0.000003 +J(0).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">325</EventID>

    <Version>0</Version>

    <Level>4</Level>

    <Task>1</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2020-09-02T11:06:55.3794577Z" />

    <EventRecordID>1031</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>XXXXXX</Computer>

    <Security />

  </System>

  <EventData>

    <Data>svchost</Data>

    <Data>16476,D,35</Data>

    <Data>DS_Token_DB: </Data>

    <Data>1</Data>

    <Data>C:\WINDOWS\system32\config\systemprofile\AppData\Local\DataSharing\Storage\DSTokenDB2.dat</Data>

    <Data>0</Data>

    <Data>

[1] 0.000159 +J(0) +M(C:0K, Fs:2, WS:8K # 8K, PF:4K # 4K, P:4K)

[2] 0.002135 -0.000051 (1) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:3480/2) +M(C:0K, Fs:2, WS:8K # 8K, PF:0K # 0K, P:0K)

[3] 0.007374 -0.000003 (3) WT +J(0) +M(C:0K, Fs:13, WS:44K # 48K, PF:44K # 48K, P:44K)

[4] 0.009379 -0.007728 (1) WT +J(0) +M(C:0K, Fs:56, WS:220K # 272K, PF:88K # 88K, P:88K)

[5] 0.001397 -0.000152 (2) WT +J(CM:0, PgRf:3, Rd:0/0, Dy:3/6, Lg:122/4) +M(C:8K, Fs:36, WS:140K # 84K, PF:156K # 156K, P:156K)

[6] 0.005940 -0.002222 (1) WT +J(CM:0, PgRf:249, Rd:0/0, Dy:16/428, Lg:28550/465) +M(C:56K, Fs:109, WS:432K # 432K, PF:748K # 744K, P:748K)

[7] 0.002927 -0.000342 (4) WT +J(CM:0, PgRf:0, Rd:0/0, Dy:0/0, Lg:4096/3) +M(C:0K, Fs:3, WS:8K # 12K, PF:0K # 4K, P:0K)

[8] 0.000013 +J(0)

[9] 0.025791 -0.024688 (4) WT +J(0) +M(C:-32K, Fs:5, WS:-16K # 8K, PF:-32K # 0K, P:-32K)

[10] 0.033498 -0.010918 (24) CM -0.023889 (31) WT +J(CM:24, PgRf:381, Rd:0/24, Dy:10/90, Lg:12509/130) +M(C:16K, Fs:24, WS:92K # 68K, PF:36K # 4K, P:36K)

[11] 0.000003 +J(0).</Data>

    <Data>0 0</Data>

    <Data>lgposCreate = 00000001:0001:0268,

dbv = 1568.110.240</Data>

  </EventData>

</Event>

---

Log Name:      Application

Source:        ESENT

Date:          2-9-2020 13:06:55

Event ID:      102

Task Category: General

Level:         Information

Keywords:      Classic

User:          N/A

Computer:      XXXXXX

Description:

svchost (16476,P,98) DS_Token_DB: The database engine (10.00.19041.0000) is starting a new instance (0).

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="ESENT" />

    <EventID Qualifiers="0">102</EventID>

    <Version>0</Version>

    <Level>4</Level>

    <Task>1</Task>

    <Opcode>0</Opcode>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2020-09-02T11:06:55.2667599Z" />

    <EventRecordID>1027</EventRecordID>

    <Correlation />

    <Execution ProcessID="0" ThreadID="0" />

    <Channel>Application</Channel>

    <Computer>XXXXXX</Computer>

    <Security />

  </System>

  <EventData>

    <Data>svchost</Data>

    <Data>16476,P,98</Data>

    <Data>DS_Token_DB: </Data>

    <Data>0</Data>

    <Data>10</Data>

    <Data>00</Data>

    <Data>19041</Data>

    <Data>0000</Data>

  </EventData>

</Event>

Is there anything new regarding the many ESENT 642 errors after updating to 2004?

It's 3 months since Microsoft had to solve this bug.