It's a bumpy road for version 2004 rollout

I updated to 2004 when the first RC came out back in January or so. It immediately bluescreened after booting into Windows (right after I updated NVMe drivers) but has since been fine.

Every time a new version is due I say I won't upgrade until after it's been out a few months, yet every time it comes out I install the RC version.
 
Same here. In fact, I've waited as long as 6 months before I do a major update. I have my system setup for a delay of 365 days, and 30 days for quality updates.
 
Most discouraging: Many of these problems were reported on the Feedback Hub, but apparently they fell on deaf ears.

This is just sad.
 
if you look at the list most of it is from specific old devices/drivers and a couple(11 total) problems have already been mitigated. so out of the millions of possible config combos, 11 specific issues isnt that bad. but please, tell me how im wrong and a shill in 3, 2 , 1....
 
if you look at the list most of it is from specific old devices/drivers and a couple(11 total) problems have already been mitigated. so out of the millions of possible config combos, 11 specific issues isnt that bad. but please, tell me how im wrong and a shill in 3, 2 , 1....

True, but what about unknown issues? I am seeing tons of complaints in r/Windows10.
 
there always is and 9/10 times its something on their system.
I'm sure there are instances of that but it seems to me that Windows quality/reliability has dropped significantly over the years. Many of their updates, whether large or small, seem to result in a plethora of issues.
 
I'm sure there are instances of that but it seems to me that Windows quality/reliability has dropped significantly over the years. Many of their updates, whether large or small, seem to result in a plethora of issues.
i dont. i think its just more people screeching on the internet.
 
I mean you can allege that but that facts are quite the contrary, especially my own experiences.

I'm glad it works for you.
my experience counts more than yours ;) and thanks for proving my point.
"tell me how im wrong and a shill in 3, 2 , 1.... "
 
I'm sure there are instances of that but it seems to me that Windows quality/reliability has dropped significantly over the years. Many of their updates, whether large or small, seem to result in a plethora of issues.

The issue is that they roll out Kernel updates way more often now. Instead of every couple year service packs, we get these massive updates twice a year. We still had issues like this back in the XP days with the service pack roll-outs. Those almost always broke stuff, but because they weren't as frequent it wasn't as big of a deal.
 
I've never had issues with updates until this one. I launch MS Edge and it takes 10 seconds to launch compared to 2 seconds. I click on the weather app it sits at the splash screen for 5 seconds, before it was almost instant. (Running on SSD of course.) Discord and Steam both had graphical bugs upon opening. Rolled back and it's back to normal. It's funny how you can tell when things are just off..
 
Some of my tech-dependents all ran into the boot to black screen after doing the update. Other than that - it seems to be working alright. Nothing good, nothing bad.
 
And more problems...

Windows 10 2004: Defragger bug defrags SSD Drives too often

https://www.bleepingcomputer.com/ne...t-defragger-bug-defrags-ssd-drives-too-often/

There is a thread about that already.
https://hardforum.com/threads/windows-10-defragger-bug-defrags-ssd-drives-too-often.1997858/

It only "defrags" your boot drive, mainly optimizing files related to the Volume Shadow Copy service (System Restore, etc). It's not performing a traditional defrag the same as it would on a mechanical drive, and it doesn't defrag any SSDs that aren't boot drives. Windows still knows the difference between a HDD and SSD. The bug is that it "forgets" the last time it performed maintenance every time you reboot, so it can result in it performing that maintenance (which includes the limited defrag) more often, if you reboot more than once per month.

SSDs should never be defragged... All it does is increase wear.

It's not that simple. You shouldn't be running traditional defrag tools on an SSD, that defrag an SSD the same way that it would defrag a HDD. There is however still some limited benefit to performing an intelligent, SSD specific defrag on an SSD. I'm guessing that you don't really care much about the nuances of this topic, and probably just jumped at the chance to bash windows again, but just in case I'm wrong, this is a reasonably good article that talks about the benefits of performing an intelligent defrag on an SSD:

https://www.hanselman.com/blog/TheRealAndCompleteStoryDoesWindowsDefragmentYourSSD.aspx
 
So what your article was essentially saying was that due to limitations of NTFS, Windows needs to defragment SSDs. I'm not overly surprised.
 
I updated my mini-STX HTPC - honestly, it seems more stable than it ever was. Used to get a lot of random issues with videos freezing and choppiness, haven't seen any of that yet after updating.
 
"Defrag" on SSD with Win 10 just issues the TRIM command. At least on my build, it says "trimming drive" and takes three seconds.
 
I almost always turn the stupid defragger off. Running it once a blue moon is good enough these days. Also, defraggers make all kinds of issues with image based backups. Leaving you with way to much changes and uploads that are not really necessary. If I re-establish a base image I will defrag just before that and otherwise leave it off.
 
Back
Top