Windows 10 2004 Feature Update

my old c6h & 1800x on the bike trainer updated fine last night

going to wait on the rest till they fix the usb printer thing
 
LOL, went to install updates on my Intel box today and saw a message that said my "device isn’t quite ready for" 2004.

Oh noes! :rolleyes:
 
So thats why troubleshooting the printer today was stuck in spooler... damnit MS.

I managed to clear that one myself with a few restarts tho.
 
If I'm not mistaken, they actually declared 2004 "done" sometime in December. That means they spent the last six months testing and fixing bugs with the insider/preview builds before they unleashed it on the rest of us... and we still got a half-baked OS that isn't ready for primetime.

It's been five years since the first release of Win10. You'd think they would've figured out by now that these twice-a-year feature "upgrades" don't really work out all that well.
 
Yeah, remember when they released Win 10 for free, and we all thought, "What's the catch?"

Turns out there was no catch, it was just crap! :lol:

And I know that's a bit strong, as Win 10 is still generally slick and works fairly well. But when it comes to the quality level of their ongoing support, it has just been so shabby! Really feels like MS is trying to work themselves out of the OS business.
 
On my system it gives me this message on the Windows Update page:

The Windows 10 May 2020 Update is on its way. We’re offering this update to compatible devices, but your device isn’t quite ready for it. Once your device is ready, you’ll see the update available on this page. There’s nothing you need to do at this time.
Click to expand...

Not sure what the wording "your device isn’t quite ready for it" means. Isn't it more like MS isn't quite ready to give me the update yet?
 
KAC said:
This shizzle ma nizzle stable now?
Click to expand...

It is for me. I did a in place upgrade from 1909. Build 1909 made my PC almost unusable. Windows explorer would randomly stop responding and crashing which also eats 50% of the cpu. Streaming videos would drop frame and apps hang when CPU usage is low. Navigating in windows was non-responsive.

The 2004 build didn't give me any of those problems. I'm been running it for 8days now and so far no problems.:bleh:
 
0091/2 said:
It is for me. I did a in place upgrade from 1909. Build 1909 made my PC almost unusable. Windows explorer would randomly stop responding and crashing which also eats 50% of the cpu. Streaming videos would drop frame and apps hang when CPU usage is low. Navigating in windows was non-responsive.

The 2004 build didn't give me any of those problems. I'm been running it for 8days now and so far no problems.:bleh:
Click to expand...

I had the same problems with Explorer.exe occasionally gobbling up the CPU in 1909. Seemed totally random, and the only way out was to kill & restart that process.

No problems on 2004 so far.
 
I think Win10 is awesome. My laptop took the 2004 update no problem, and I really like the new Edge. It's super snappy. I might switch everything over. I use Chrome on everything except my laptop, but that might change now.
 
Nunz said:
I think Win10 is awesome. My laptop took the 2004 update no problem, and I really like the new Edge. It's super snappy. I might switch everything over. I use Chrome on everything except my laptop, but that might change now.
Click to expand...

I just switched from FF. Really enjoying it here as well.
 
Windows Update said 2004 was available for me, so I went ahead and clicked "Update". The update churns and churns like it's doing something, but then 10 minutes later "we're sorry, something happened so we can't complete the update at this time. But don't worry, we'll try again later". Of course, no indication of WHY it failed, just "something happened". Good grief, Microsoft...
 
Munkus said:
Windows Update said 2004 was available for me, so I went ahead and clicked "Update". The update churns and churns like it's doing something, but then 10 minutes later "we're sorry, something happened so we can't complete the update at this time. But don't worry, we'll try again later". Of course, no indication of WHY it failed, just "something happened". Good grief, Microsoft...
Click to expand...

I wish I had advice to offer ... the only thing I can say is not VPN'd in when updating and about as standard fw and av config as you might find...
 
You must log in or register to reply here.
Back
Top