Bork Tuesday, Any Problems Yet?

9 out of band 'Optional' updates for Windows 8.1

 

Hi
Banzi
are all these update optinal?
thanks

 

9 out of band 'Optional' updates for Windows 8.1 = all 9 'Optional'

 

Yeah they are optional mantra, forgot to add that to post

 

From a business point of view I expect that MS assumes that the majority of Home users stay with all the default/ recommended settings, which includes auto WU download/install to maintain a current system. The user would not be aware if a KB had failed or corrupted part of the OS unless something stopped working. MS would just reintroduce the KB after the fact to remedy the problem. The user would remain none the wiser. So far these borks have not been catastrophic (to most), so MS can continue with the 'see no evil' approach with the W10 Home edition.

My sister-in-law who is not computer savvy asked me if KB stood for ' Kinda-Broke' . She would not have understood Kolossal Bork. I dread the day that one of these KBs turn out to be a 'Killer-Brick'. As W10 is destined for the entire MS platform, I wonder what happens if a KB bricks the future OS.

 

M$ has Mark Russinovich post a step by step unbork solution.

 

seriously, all these morons who contributed these ~ Snipped as per TOS ~ codes at MS should be fired, or at least be held accountable. lousy coders have occupied most positions at MS. I think one day for sure there will be a killer-brick coming out that brick the entire MS ecosystem. All these offshore outsourcing **** needs to be cleared out. too many morons working in the IT industry nowadays, that's a fact.

 

I don't understand why MS abandoned the Service pack practice that had been working good for many years. a service pack avoided the frequent, huge patches that MS released to consumers each month, so that only small security patches are needed, which could lead to fewer chances to break the OS.
Management at MS appears to be much incompetent nowadays too, not only the lousy coders they employed. Windows 10 could be a hype that turns out to be not better than 8.1.

 

1 important and 9 optional patches installed successfully on Win 8.1 64-bit.

 

Microsoft: In 2014, 87% of initial updates were not later re-released

 

I'm guessing ... yes.

 

Heaven forbid !
What have MS ever done that makes you think they have that sort of attitude towards their customers -

 

Today Microsoft updates presented itself that 1 important (KB3035583) and 1 optional updates were available. The mentioned KB was hidden by me already and yet it presented itself again. Did hide them both.

 

13% is a huge number for borked patches. WTF is going on nowadays? Do the morons at MS have no shame?

 

W8.1 x64 ~ I received 3020370 in my May queue as an 'Important' update.
Article ID: 3020370 ~ states: Note This is an Optional update. If you have a Windows Server 2008 R2-based computer, you should install this update.
To resolve this issue,we have released an update through Windows Update and Microsoft Download Center. Even though this issue has only been observed in Windows Server 2008 R2, the update also applies to Windows 8.1, Windows RT 8.1, Windows 8, Windows RT, and Windows 7.

Why would I receive an Optional as Important. Why would I receive if only observed for Windows Server 2008 R2 which I believe is like W7..?

 

KB3022345 is causing corrupted files or making SFC /scannow think they are corrupted.

I usually run sfc /scannow after updates to force update to fully install from reboot (sometimes they don't and SFC forces them before it will run) and as a check to see if any files are corrupted. I installed three optional updates today, and SFC found corrupted files. I uninstalled all three, rebooted, and ran sfc /scannow again and now "did not find any integrity violations." I searched for kb3022345, the bigger one of the three, and found many articles about it:

http://www.infoworld.com/article/29...le-corruption-which-sfc-is-unable-to-fix.html

https://www.reddit.com/r/windows/comments/35xz3q/warning_windows_7_update_kb3022345_corrupted_my/

and others

 

Sounds like it's just interfering with the proper functioning of sfc, rather than actually corrupting any files....

 

I agree, few years back there were much less problems with updating Windows (at least that's how I remember it). It looks like guys at QC are not doing their job.

 

The "Note This is an Optional update" text in that article is probably now incorrect. Looking at https://support.microsoft.com/en-us/kb/894199, notice that on May 12 that particular update is listed as "Metadata has changed. Binaries have not changed." In this case, that likely involved Microsoft changing that update from "optional" to "important."

 

Indeed, there were rarely any problems at all with the Win XP updates/patches, even if the update procedure could be a bit sluggish, it worked. And I rather have a slow update process...than receive borked updates.

 

Nah they wouldn't stoop that low....

It just seems that they are releasing more & more dodgy updates, in the past I always installed then as soon as they were released but after so many iffy ones & things like the Windows 10 adware patch & this NSA....ahem sorry diagnostic tracking service patch I now like others in this thread wait a few days before selectively installing needed ones & hiding ones i have no need for

 

If they had shame, and tried to release it as a patch, they'd probably bork it.

 

The irony is ... I wasn't being ironic lol.

 

https://redmondmag.com/articles/2015/05/18/marching-orders-for-it-pros.aspx