Latest Windows 10 update causes system slowdowns, crashes, more

scavengerspc

Posts: 1,678   +1,729
TechSpot Elite
The cold hard reality is, that none of us here are so ploddingly stupid, that we aren't acutely aware you can always "reinstall Windows".

So, with that in mind, is does take quite a bit of hubris, to pass off, "just reinstall Windows", as anything resembling "help".

M$'s stark reality, is that they no longer have leave to bang up customers $300.00 for an OS, to go in a $100.00 tablet. Enter forced adoption,of Win 10, and all the opportunities for sales of their own software it presents. If existing aftermarket software isn't compatible, they could care less if their forced updates brick machines.
Reinstall wasn't the help I was referring to. It was informing him that Home also has an update delay available.

I thought you said your reading comprehension was very high CC.
 

CharmsD

Posts: 411   +255
Reinstall wasn't the help I was referring to. It was informing him that Home also has an update delay available.

Selective reading, don't worry about it. I've had one laptop's drive ground to dust and a newer one has gotten so damn slow it's ready for the recycle bin. I may convert it to linux.

Hmm, this computer is waiting for an update-restart now..I suppose I'll chance it. Lol
 

captaincranky

Posts: 17,411   +6,144
Reinstall wasn't the help I was referring to. It was informing him that Home also has an update delay available...[ ]...
My bad. So, "you can brick it now or brick it later, even on Windows Home", was the "help"?

Although, it sort of resembles a stay of execution. more so than help.
 

CharmsD

Posts: 411   +255
Shut off automatic updates and manually install the ones you want/need. Takes more effort, but saves major headaches in the long run.

I don't know what's going on with MS.. I've been getting an update right after an update, and I'm tired of reading about the update they rolled out to patch the update that patched the previous update patch to the update. Sumthin' like that.

This one did fix/repair the MSVxxx.dll the previous one broke, only about 100 programs had a dependency for it, including Firefox which works again!
 

wiyosaya

Posts: 6,540   +4,937
My bad. So, "you can brick it now or brick it later, even on Windows Home", was the "help"?

Although, it sort of resembles a stay of execution. more so than help.
(y) (Y) Ah, as seems more often than not, you and I are on the same page and you got exactly what I meant.

Simply put, delaying updates does not mean that that delayed update will not brick a PC. Usually, it takes an extraordinary amount of b!tching to M$ that their updates break or otherwise brick PCs before they consider doing something about it. And a "fix" could take much longer than 30 days.

I had to b!tch to them for months that their earlier 10 "updates" completely knocked out user-setup WiFi access points and that they had to be reinstalled with every update before they finally decided the issue was worthy of attention.

And that is only the start of various issues that I have had with WinDOHs 10 - including the time I installed an "update" and my computer booted to a black screen with only the mouse cursor showing. For me, Image for Linux is my savior. :) https://www.terabyteunlimited.com/image-for-linux.htm
 
Last edited:

wiyosaya

Posts: 6,540   +4,937
I don't know what's going on with MS.. I've been getting an update right after an update, and I'm tired of reading about the update they rolled out to patch the update that patched the previous update patch to the update. Sumthin' like that.

This one did fix/repair the MSVxxx.dll the previous one broke, only about 100 programs had a dependency for it, including Firefox which works again!
It was so kind of them to ensure that those 100 programs would work again without the two weeks of work that it would take to reinstall them.

Bow before the great God M$ ? ? ? ? ?
 

wiyosaya

Posts: 6,540   +4,937
Shut off automatic updates and manually install the ones you want/need. Takes more effort, but saves major headaches in the long run.
I've done that on my pro machines. Unfortunately, WinDOHs updates, from my first-hand experience, are like playing the lottery. There is no guarantee that they will not break something when the PC owner does decide to update until the PC owner installs an update and then yells, Oh Crap! WinDOHs Strikes Back and the PC starts making a noise that sounds like Darth Vader's breathing while emitting glowing red lights! :laughing:

Where is Yoda when you need him?
 
Last edited:

ZedRM

Posts: 641   +401
I don't know what's going on with MS.. I've been getting an update right after an update, and I'm tired of reading about the update they rolled out to patch the update that patched the previous update patch to the update. Sumthin' like that.

This one did fix/repair the MSVxxx.dll the previous one broke, only about 100 programs had a dependency for it, including Firefox which works again!
And this is why I disable automatic updates. I install only cumulative major updates once or twice a year and that is only after the updates have been released for enough time for MS to find problems.

I have been tired of the "rolling update" model of software distribution since XP. It is unacceptably flawed and problematic. It seems to be getting worse, not better.
 

CharmsD

Posts: 411   +255
And this is why I disable automatic updates. I install only cumulative major updates once or twice a year and that is only after the updates have been released for enough time for MS to find problems.

I have been tired of the "rolling update" model of software distribution since XP. It is unacceptably flawed and problematic. It seems to be getting worse, not better.

I think I've finally figured out what Feedback Hub is. It's "Windows 10 Complaint Sink", where compliments are fished for and "your whines" get buried.

Clever Microsoft, very clever!

I could take partial blame for the missing DLL. I uninstalled VS (Pro) but I won't.

That dll is a VS re-distributeable - meaning programs written to use it can freely distribute it, and millions of programs did. Including Windows.

So they broke it, they have to fix it.

I can now spend a month RE-installing software I spent a month RE-installing the other time, a few months ago, when Windows Fun Edition (PRO) freaked out.

You gotta be smart tough and fast to keep a Windows computer running!
 

wiyosaya

Posts: 6,540   +4,937
I have been tired of the "rolling update" model of software distribution since XP. It is unacceptably flawed and problematic. It seems to be getting worse, not better.
Seems? Don't worry, it is not your imagination. :laughing:
 

wiyosaya

Posts: 6,540   +4,937
I think I've finally figured out what Feedback Hub is. It's "Windows 10 Complaint Sink", where compliments are fished for and "your whines" get buried.

Clever Microsoft, very clever!
A few years back, it was even worse. Some of the M$ people that used to reply offered essentially useless suggestions to the point of it not being worth going there as a non-answer was almost guaranteed.

Though I never saw this reply, many of the "answers" that they gave were no better than "Is your computer on?" - IMO.

At least now, some of the answers at least sound as if the person answering has an iota of technical skill, however, that Reinstall answer just brings me back to them asking "Is your computer on?"

I could take partial blame for the missing DLL. I uninstalled VS (Pro) but I won't.

That dll is a VS re-distributeable - meaning programs written to use it can freely distribute it, and millions of programs did. Including Windows.

So they broke it, they have to fix it.

I can now spend a month RE-installing software I spent a month RE-installing the other time, a few months ago, when Windows Fun Edition (PRO) freaked out.

You gotta be smart tough and fast to keep a Windows computer running!
Speaking as a programmer with 25+ years of experience, the thing is is that that MSVXXX.dll is a shared dll. There used to be, and may still be, an entry in the registry that should have been incremented for each program using it. It is, as you noted, used by many applications. An uninstall of VS should be smart enough to know, by reading that registry entry, that there are a number of other programs (on any PC where VS is installed) that are using it, and that removing VS should leave it there - not remove it.

IMO, you did nothing wrong. This is all on M$ not you! :)

And all that effort that it sounds like you went through to update your update is why I use Image For Linux. I image before one of these so-called updates, then if anything goes wrong, I restore the image. For me, it is a $30 investment that has saved me countless hours, and maybe days, of time. It is well-maintained with responsive support on the very rare occasions (like two or three times in the at least eight years I have owned it), very easy to use, and bootable so that it bypasses any other OS that might boot. (PS - I don't work for them; I am just a very happy customer.)

And on top of that, IMO, is, assuming both the pro version and administrative access, going into the policy editor and disabling automatic updates. From what you have said, in other posts it sounds like you do not have admin rights; however, you might make an argument for it, or at least an argument for TPTB to turn off automagic "updates" based on the amount of time you have wasted fixing M$'s problems through reinstalling your software. Just promise TPTB that you will periodically check for updates. ;)