KB4540409 for Windows 10 Insider Preview Slow Build 19041.113 Feb. 27 Insider

Danielx64 said:

I might do a clean install of 2004 from the offical Microsoft ISO and see if it comes. Is it enough to just install and check the event log?

I think it's triggered directly after installation, yes. I have noticed that events like Windows Update, Win Search, Apps like Groove Music and Movies trigger event 642 plus other background processes that I haven't really figured out yet. For latest Groove Music (with the new icon) you get this:

Music.UI (7244,D,46) {C44E070D-7830-4EC4-8149-E7851344A78E}: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

By all means, it's only warnings and not errors but it is disturbing. You see these the easiest way in the event viewer in Custom Views - Administrative Events.

Fredrik said:

I think it's triggered directly after installation, yes. I have noticed that events like Windows Update, Win Search, Apps like Groove Music and Movies trigger event 642 plus other background processes that I haven't really figured out yet. For latest Groove Music (with the new icon) you get this:

Music.UI (7244,D,46) {C44E070D-7830-4EC4-8149-E7851344A78E}: The database format feature version 9120 (0x23a0) could not be used due to the current database format 1568.20.0, controlled by the parameter 0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat).

By all means, it's only warnings and not errors but it is disturbing. You see these the easiest way in the event viewer in Custom Views - Administrative Events.

I just did a clean install in a VM and this is what I got. Didn't even install VMware tools yet:

Danielx64 said:

I just did a clean install in a VM and this is what I got. Didn't even install VMware tools yet:

Thank you very much for confirming that! Let's see then if Microsoft can do anything about it before version 2004 is introduced to the masses.
Even if only warnings it is an error branch triggered in the code which always degrade performance since cache handling and branch prediction are always set aside when these kind of "try-catch" events occur.

Zardoc said:

What I'd like to know, is it flagged in the feedback hub? Is it new or has it been showing up for a while. Not being in the test team like I used to is harder to follow issues. Let's just hope that the famous ''By design '' phrase doesn't show up like the DCOM errors 10016

It's been there as long as I have tested the pre-2004 release (since December).
Yes I have written about it in the Feedback Hub but I don't think that matters. Too much trivial stuff in there so relevant info drowns.
True about DCOM 10016 - they should not be ignored, especially since they are all possible to solve. Well, most of them.

A few days ago I joined the slow ring to get 20H1, and now that I've got it I want back out. But the only option is to select the "Stop getting preview builds" option, which says it will remove me when the next major release of Windows 10 is installed. I'm hoping that is 2004 & it will opt me out once it goes GA and not 20H2. Does anyone know for certain? I really don't want any more Insider builds, not even 'Release Preview' ones.