Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

Midnightwalk

(3,131 posts)
10. Very hard to say
Tue Jan 28, 2020, 07:42 PM
Jan 2020

Last edited Wed Jan 29, 2020, 02:15 AM - Edit history (1)

Without actual failure rate data. Which is very hard to get in this case particularly because from the os point of view there is nothing it can that should be able to cause a hardware failure. Microsoft is going to blame the hardware like software people do. And in this case that may be fair.

But drives do wear out. Near end of life, extra workload from the os could be the straw that breaks the drive. Maybe more so with spinners with all the mechanical issues and media issues that occur, but flash wears out too.

A new OS likely has a bigger memory footprint so paging is more likely, particularly as software is loading. But any increase in read write rates will make the arm move more which can show up latent issues.

It might he interesting for someone to note the memory footprint size in task manager and the size of the swap file before and after the upgrade. Even better would be looking at the disk monitor (forget what it’s actually called)

Edit to add that just installing the new os will put a lot of new work on the drive. Think of it as an ild guy. Extra work can always trigger something

Good health to all

Recommendations

0 members have recommended this reply (displayed in chronological order):

Latest Discussions»Help & Search»Computer Help and Support»I would avoid the windows...»Reply #10