New
#410
Did you check your eventlog............?
Did you check your eventlog............?
I updated via a USB drive made using the Media Creation Tool yesterday and apart from the fact that this was the most trouble free and quickest upgrade ever for me... and seemingly with zero issues that I can find... the most striking thing is that it all seems to run with minimal CPU usage and very little fan activity. Not that there was a problem before, but here we are on the hottest day so far and I've 3 tabs open (Edge) and here I am typing away with just 1 to 2 % CPU usage.
It's very noticeable to me.
Downloaded ISO via MCT, mounted and ran setup.exe. Took about an hour to complete the upgrade to 2004.
So far all is well. No new problems, no resolved problems. Microsoft Edge is at Version 83.0.478.37 (Official build) (64-bit).
Windows.old is at 2.3GB. Did a Macrium backup so I can delete Windows.old any time I want.
i got many of these errors now since using media toll to update .
Log Name: ApplicationSource: ESENTDate: 5/30/2020 11:58:45 AMEvent ID: 642Task Category: GeneralLevel: WarningKeywords: ClassicUser: N/AComputer: LAPTOP-EVII47JSDescriptionllHost (9132,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).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-05-30T18:58:45.2603571Z" /> <EventRecordID>2731</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>LAPTOP-EVII47JS</Computer> <Security /> </System> <EventData> <Data>DllHost</Data> <Data>9132,D,12</Data> <Data>Microsoft.Windows.Search_cw5n1h2txyewy_NOEDP_LEGACY_IDB: </Data> <Data>0x410022D8 (8920 | JET_efvAllowHigherPersistedFormat)</Data> <Data>9080 (0x2378)</Data> <Data>1568.20.0</Data> </EventData></Event>
Not good , warnings may become errors............
Well ok, this is the first time that I 've had a major problem with Windows updates/upgrades. 2004 refuses to install on my main machine, where it appears to be starting the upgrade but just stops after a while & goes back to showing the desktop. It's also assigning a drive letter to the 100mb 'System Reserved' partition......very strange.
Main secondary machine which has much of the same (older) hardware took the upgrade with no issues at all, as has an even older one. Makes no sense to me at all!
Have a look here. It may give you a clue. Known and Resolved issues for Windows 10 May 2020 Update version 2004
I have no idea why Windows Update would offer the version 2004 update and then take away the offer. My computer isn't affected by any of the known issues.
Instead of waiting for Windows Update to offer the version 2004 update again, I used the Windows 10 Update Assistant. The update took seemingly forever, but I've using version 2004 for about a day now without issues.