This is not the first dirty update procedure i have experienced with windows 10
Yesterday MS forced down the January Cumulative Upgrade (and build number advance) down the users
throats.
Heres what happened to me.. (and i have rarely ever seen something like this before )
While i was installing a game using UPLAY (ubisoft) and watching video in Chrome my brandnew Windows 10 Laptop
(installation age 3 days) become more and more responsive with sound starting to stutter, severe issues that intensified
over a short period of time and i was like "WTF?!?" What happened was that during my tasks windows had decided to
update my rig (of course it doesnt warn you or give you the option to reschedule ) and this update was so severely
dirty implemented that my 16 gb of memory was completely consumed and not released .
I had to reboot of course and after that everything returned to business as usual.
Well, i thought, rare coincidence probably because i was installing a game, watching HD Video at the same time etc and
installing an update.
Boy was i wrong ..today i turned on my older Laptop for the first time in days and it resumed from sleep and just a couple of seconds later after the background update had run..(indicated by the messages i received after booting it after the error ).Bam....wtf .. i never had this one before either.Code:STOP 0x0000001E: KMODE_EXCEPTION_NOT_HANDLED – FWPKCLNT.SYS
MS is really becoming more and more sloppy after they layed of their Quality Control staff they are not able
to release large updates that come without issues.
The Nov and Dec Updates was the same story btw. Plethora of Problems.
I refuse to take the blame here my systems couldnt be cleaner , they have no driver issues , they run stable 100% in all operation including heavy duty encoding, gaming etc.
Hi, I can appreciate your frustration- MS does not necessarily configure things as we might want, expect or need.
Just a simple one first: do you have this in Settings, Update?
Secondly, do you use disk imaging, and if so can you restore an image created before the above?
(Macrium Reflect or Aomei Backupper - free- + their boot disk and external backup medium- essential tools to preserve your system and your sanity).
Agreed, problems with the Nov TH2 upgrade (10586) with system restore turned off, associations reset to default... but for me relatively minor, except there was no warning of how long it would take.
One way to control WHEN Windows Update(s) occurs is by setting it to 'manual' in Services. Only when I click "Check for updates" does this service kick in. After reboot, the service is sidelined again. Of course, staying in touch as to when Updates are available is important for this option. Normally, Patch Tuesday (second Tuesday of every month) is when new Updates are offered. Windows 10 hasn't strayed from this schedule. Occasionally and rarely, critical Updates are offered at other times. That's when staying in touch is so important.
Do you mean Disablein Services ?One way to control WHEN Windows Update(s) occurs is by setting it to 'manual' in Services. Only when I click "Check for updates" does this service kick in. After reboot, the service is sidelined again......
Mine is set to Manual which I believe is the default setting and it is a (Trigger Start)this trigger start is done by Windows not me so updates are checked for and downloaded but a Restart is scheduled
The various methods to disable or enable Windows Automatic Updates are explained @
Windows Update Automatic Updates - Enable or Disable in Windows 10 - Windows 10 blog
That bug has been around for a while. Bad video driver is the main reason why that error keeps popping up. The other is Visual Studio that can cause it.
