I think power system is wonky in 20h2 would explain why i sudden have issue with my gamepad keeping my pc from puting my monitor to sleep, or well I would like to think cause then there is hope it get fixed and I can connect my gamepad again.
Honestly the temptation to install 1909 is still there.... the only thing kinda stopping me is not wanting to install all the programs I use over again.
i only installed 20h2 cause I didnt want windup with forced upgrade at somepoint, at lest this way I did on my own terms, I probably wont touch new build to till the "next" enabling" build happens which year away so i should fine for another year or so. other then gamepad issue i see no issue, and other then alot esent error refering to Code: DllHost (10428,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). Code: DllHost (10428,R,98) WebPlatStorage: 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). Code: Catalog Database (3684,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). bunch entries multiple times day since the upgrade referring to them all. all referring to database format, I think it is some left over that can be safely ignored though
Same question what exactly am I deleting? and does fix all the error i listed or just the ones referring to search? If it indexing and what not I dont even have indexing enabled so there nothing indexed, any search i do in reguard to this points to indexing which like said is not enabled so nothing is indexed Are you talking about deleting this ? "C:\ProgramData\Microsoft\Search"
This is just a guess, I have indexing disabled in drive properties too. The OS might still check and say you removed some apps, like "phone" but it was indexed by OS, even though it is disabled it might throw an event log. I have a bunch of the last one you posted, but not error ones (top two).
nah I have disable in services, anyway I deleted what I posted reneable windows search and rebuild index rebooted and then disable it again it seem to got rid of them all? execpt if I left indexing service aka" windows search" enable I get esent error refering too indexing if i disable there gona, but now I have these Code: Catalog Database (3524,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). Code: svchost (3876,D,12) SRUJet: 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). Code: svchost (3876,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). there all refering to some database format issue, still think there mundane issue that can be ingnored but if i fix I will
I have both of those types (warnings) Catalog database and the Svchost ones. I have indexing service enabled but with the checkmark unticked in drive properties. No ESENT errors though, just warnings and I wouldn't worry about either really.
https://answers.microsoft.com/en-us...vent-642/198b9f3f-f052-4e88-87c4-b96b720e94dd Pretty much all the esent erros i seen are listed in this topic, some said it fix it self when windows did it maintance and deleted windows.old other said it didnt m but some just deleted it manual, other said they just reverted to 1909, so obviously there issue somewhere But some people say it also "freezing" there system then bunch of those error pop up, I have no such freeze though so i dont know, it not first time "upgrade" left remnants the old build and cause event viewer errors, they tend to fix sooner later in updates
I glad my OCD isnt as bad as some people. my OCD isnt that bad that I would do it either, Then again it helps that I Stoped looking at eventviewer so much, I look at when I do "updates" "upgrades" and or change gpu drivers, or I see the monitor flicker for no reason or Firefox do it "internal" tdr that only effect firefox cause all those are accompanied by nvidia driver reset error, I would not even do it to fix my gamepad from causing my monitor not to go to sleep, personal I think 1 of 2 thing something wonky in 20h2 and or nvidia drivers 456.71 some how playing nice with each other, will find out when updates to window happen, and or the next nvidia driver is release I will try them. for now i just disconnected it, seeing I not using and probably wont still I still being obsessed with nioh 2
yah that didnt help, in the 8 hours since i did all that I have no less then 71 esent error for all the thing I menitoned
I have not had any further esent errors since installing 19042.608 and cleaning off the update supersceded files.
Theres no windows.old for a 19041 > 19042 upgrade. Supersceded updates can be removed through disk cleanup or a dism resetbase
That is because I used Windows update assistance to go from 2004>2009. I could of used the enablement package.
You mean like this? https://www.tenforums.com/windows-1...e-feature-update-windows-10-version-20h2.html
19042.610 is out. https://www.neowin.net/news/microsoft-releases-windows-10-builds-19042610-19041610---heres-whats-new