Discussion in 'other software & services' started by Daveski17, Nov 12, 2014.
Took about 3 hours to upgrade... (on my ~10 years old PC)
But seems to work fine!
Updated Windows 10 to Version 2004, OS build 19041.264 (took 1hr. 45min.) So far so good.
Used the Update Assistant and it only took 14 minutes on here? It really did, I timed it from download to updated desktop. No major problems, just a renewed acquaintance with some Insider bugs that I thought had been fixed already, namely the disk optimization where it says "Never run" when you did run it and then restarted machine. I tried disabling it in Task Scheduler as others recommended but that didn't cure it. If anyone knows how to work around this effectively, do tell.
These Are the Windows 10 May 2020 Update Issues Causing BSODs
Microsoft acknowledges several issues in the latest update
May 28, 2020
Microsoft blocks Windows 10 May 2020 Update on PCs with Memory Integrity enabled
Windows 10 May 2020 Update Crashing with a BSOD Due to Old NVIDIA Drivers
Getting this error and warning "PerfDiag Logger failed to start with the following error:0x000035", in the Event Viewer since the upgrade to Win. 10 2004. Wasn't a problem with 1904 version. Any info would be appreciated.
Hi Wolfrun. Those Kernel Event tracing errors and warnings are meaningless. My experience with this type of events is as follows. The Event 2, I see about 3 of them every month. One at a time, and always when cold starting or rebooting the computer. The 3 and 4 are rare and come together. The one and only way I get them is when I visit a particular website, and stay in the website for a long time. In this website you upload and download files, and there is a lot of activity. Before I started visiting this website, never saw this events (3 and 4). There is another Kernel Event Tracing error, number 1. I used to get that one often, but a while back, I found a solution that fixed it. As of yet, I haven't seen any of this events in W10 2004.
I have a couple of old Asus VivoTabs. They won't update beyond 1803. Message was something like "incompatible with this version of Win10". I tried 1809, 1903, 1909 and 2004.
I deleted all partitions from the drive and installed 2004. No issues and everything works.
@bo elam Other then the Event Viewer warnings and errors, Win.10 2004 runs fine along with sandboxie. Just a pain to see those alerts in Event Viewer. The other error which I seemed to have solved was "Kernel-Event Tracing 0x0000188 Ready Boot". Anyway I'm taking your advice about that the warnings are meaningless. Now I have less stress.
Clean install Brian? Wash your mouth out with soap.
Paul, it was the only way I could get beyond 1803. Upgrades didn't work.
I have known machines that wouldn't take a clean install until the disk was fully flattened (wiped)
It was as if they still retained a faint memory of what they once were.
I always do a diskpart /clean before installing Windows. It's faster anyway than to delete each partition separately and also ensures to get rid of any hidden system partitions.
I had a data partition which I wanted to keep so I only deleted the RE, ESP, MSR and Win10 partitions and left the Data partition.
FYI to those "forcing" 2004 Feature Upgrade. Refer to the below screen shot that appeared on my device this morning. Interestingly, my device has none of the published issues MS has released to date. So I assume there might be other "unpublished" issues that MS is not "fessing up to" currently.
You can force update the upgrade right away with the Update Tool = https://download.microsoft.com/download/8/3/c/83c39dca-2d27-4c24-b98b-0a4d6d921c80/Windows10Upgrade9252.exe
My point is one should not force an upgrade if MS indicates system issues exist in applying the upgrade. Or, be prepared "to pay the price" for doing so.
Agreed, it should not be forced. If someone does dare to do so, be prepared to have a disk image and restore it when things don't work out. I've seen PCs go into a BSOD loop after applying upgrades that should not have been.
FWIW, on the 28th when I clicked Check for updates, I got nothing. The update was not offered, and got no message from Windows updates telling that there might be a problem updating to 2004. So, I used the Update assistant.
I heard about the many supposed issues with version 2004, but so far all I seen is a pretty nice and decent system. I am happy to have gotten having to do the update out of the way.
Microsoft starts notifying users if Windows 10 2004 is blocked
I had a pause, after getting to v1909 in April:
However, I did just get an Update for:
Successful: Windows successfully installed the following update: Intel - Extension - 4/1/2019 12:00:00 AM - 1918.104.22.1683
My Windows Updates will resume in a week's time.
See, I didn't lie:
Not much activity so far this month, but that should be about to change.
Well, 2004 is running a lot more smoothly and quickly after a few days. I had Full telemetry enabled in the Privacy settings. Still getting a few of those ESENT 642 warnings in Event Viewer but the number and frequency of occurrence is very much reduced, maybe like six or so a day, down from literally a couple dozen. Switched back to Basic diagnostics. Hopefully, 2004 will approach the performance and cleanliness of 1909, which I think was the best Windows 10 to date.
Windows 10 May 2020 Update is causing issues with Intel Optane
June 4, 2020
Intel confirms Windows 10 May 2020 Update issues with Optane (June 6, 2020)
Separate names with a comma.