Microsoft yanks .Net security patches over conflict with SQL Server, Veritas Backup

[Karlston]

After official warnings from Microsoft and Veritas, .Net Security/Quality rollups KB 3210137 and KB 3210138 are pulled

Credit: William Mewes

 

If you’re using SQL Server or Veritas Backup on a Windows 8.1, Server 2012, or 2012 R2 system, and running .Net Framework 4.5.2, you may be having problems with this month’s .Net security patches, KB 3210137 and 3210138.

 

The problems are so bad that Microsoft yanked the patches from the Microsoft Update Catalog, and issued a formal warning yesterday for those who use SQL Server. Veritas independently posted a warning about those patches blocking its BackupExec Management Service. Microsoft’s warning comes with a manual workaround for SQL Server. Veritas says you should either upgrade to .Net Framework 4.6.1 or uninstall the patch.

 

Surprisingly, Microsoft didn’t pick up the bug in its “Preview of Quality Rollup” phase, which put the patches out for testing in November. I didn’t see any notice about the problem until yesterday--a full week after the final, December versions of the patches appeared and a month after the bug first hit in the “Preview” phase.

 

Microsoft’s warning, KB 3214106, says:

The December 13, 2016, Security and Quality Rollups updates 3210137 and 3210138 contain a known issue that affects the .Net Framework 4.5.2 running on Windows 8.1, Windows Server 2012 R2, and Windows Server 2012… Applications that connect to an instance of Microsoft SQL Server on the same computer generate the following error message:

provider: Shared Memory Provider, error: 15 - Function not supported

Microsoft is researching this problem and will post more information in this article when the information becomes available.

Veritas' warning, called Backup Exec Console will not connect after installing November 2016 or December 2016 Windows Updates, warns:

Error Message

BackupExec Management Service was unable to start. Connection open and login was successful, but then an error occurred while enabling MARS for this connection. (provider: Shared Memory Provider, error: 15 - Function not supported)

Veritas goes on to note:

Microsoft confirmed that these November patches are optional and can be safely uninstalled… Please ensure that there is no Group Policy (GPO) defined in the environment to automatically download and install Microsoft Windows Updates and please confirm the windows update status and disable auto updates for Microsoft products as otherwise the just uninstalled Microsoft Windows Updates might be installed again.

That advice is a bit surprising, because Microsoft distributed the offensive patches as part of security bulletin MS16-155, which is certainly not optional. Microsoft rated it “Important” with known active exploits.

 

The documentation, as usual, lags behind the reality. Neither KB 3210137 nor KB 3210138--both of which stand at version 3.0--nor the overarching description of MS16-155, KB 3205640, now at version 2.0, has been updated to warn of this known conflict.

 

The problems with the November updates that Veritas mentions (KB 3195382, 3195383, 3196684, 3196686, and others) are in fact bugs in the preview versions of this month’s bad patches.

 

There’s a reason why preview versions are only for corporate testers and developers. It’s distressing that none of them caught this problem before it rolled out to the world at large.

 

Ah well, another lump of coal in the update stocking.

 

Source: Microsoft yanks .Net security patches over conflict with SQL Server, Veritas Backup (InfoWorld - Woody Leonhard)

 

NET Security/Quality rollups KB 3210137, 3210138 pulled over conflict with SQL Server, Veritas backup (AskWoody)

[WALLONN7]

LOL

My dear @Karlston, considering the collection of jokes that you've presented to us lately, if you aren't yet a comedian, that's your career!!! 

[Karlston]

7 minutes ago, WALLONN7 said:

Double post already reported...

 

Oh!!!! Your reply double post.... you had me worried for a moment there...

 

And those jokes... while Microsoft keeps making them, I'll keep posting news about them.

[steven36]

I liked Windows 8.1  but most missed the boat  or still never left ship .. Windows 8 has been out for 4 years and  its been competing with Windows XP  since 2014 for 2nd and now  3rd place since the release of Windows 10  in the marketshare.  Something that never had any value to most on Windows and only holds 8.01 % marketshare lower than XP even dont really matter too Microsoft's  scheme of things no way they would just like to add that 17% both O/S  holds  together  to Windows 10 and they will almost be defeated Windows 7 . Windows 8x never had much market share value ever it was a bad mistake that made the old CEO  have too take the early retirement package. Windows 10 passed it  Feb 1, 2016 in  a little over a month it will passed it for a year now.

[Karlston]

Actually the latest 8.1 release is around 2 and a half years old. Enough time to become mature and stable, and only needs a (very cheap) Start Menu replacement. Am still as happy as a pig in the proverbial, 8.1 makes a good Windows 7 upgrade IMO.

 

I wonder what Windows 10 users are going to do when Microsoft has another Vista-moment or Windows-8-moment and changes Windows 10 dramatically and the users hate it. 'Bout the only options are to try and live with it, or stop the offending upgrade and updates permanently, or change to another OS.

[steven36]

2 hours ago, Karlston said:

Actually the latest 8.1 release is around 2 and a half years old. Enough time to become mature and stable, and only needs a (very cheap) Start Menu replacement. Am still as happy as a pig in the proverbial, 8.1 makes a good Windows 7 upgrade IMO.

 

I wonder what Windows 10 users are going to do when Microsoft has another Vista-moment or Windows-8-moment and changes Windows 10 dramatically and the users hate it. 'Bout the only options are to try and live with it, or stop the offending upgrade and updates permanently, or change to another OS.

I  never used Windows 8 to tell you the truth one of my PCs came with Windows 8  I got it cheap  because Windows 8.1 was out  it just was a free update trough the store and Windows 8.1  was just like SP1  its a service pack  that Microsoft dont call a service pack and that's all new  releases of Windows 10 is  . It's a young O/S it's already had 3 service pack. When I 1st installed Windows 7 it done been out for years  and was still full of bugs that was fixed in SP1 soon after .

 

The only reason I used Windows 8.1 was because my main PC i used Windows 7 on died on me and i bought  a new PC with windows 8 and windows 8.1 was a update trough the store. . The only reason I used Windows 10 was because it was free to me .My hard drive went out with TH1 installed so I bought another PC  that had Windows 8.1 on it new  and put another  hard drive in my old one both have Windows 10 on them now and i also had someone give me a old Vista upgraded to Windows 7 tower that can be upgraded to windows 10  but i have a lot of old software on it so i just rolled it back to Windows 7. tell Windows 7 runs out of updates  than i will reformat it to Windows 10 clean I'm sure it will still work it's hardly ever been used at all it was a old lady's PC  that they replaced with a laptop.. I dont buy windows and never have i just buy PCs with Windows on them.

 

The difference in Windows 7 , Windows 8.1  and Windows 10 too me is Microsoft gave me a free DVD and key with windows 7 for 1 PC and someone gave me a free retail key for it  ,Windows 8x I had too buy PCs to get it its not because i wanted it it's what shipped on it and I learned to like it. . Windows 10 was free to me on all 3 of my PCs  .You must be mad to think i would buy a Windows 8.1 key ever Microsoft don't even sell them no more  and i never buy Windows and got bored with Windows and learned Linux witch is always free .

 

I was a XP  diehard for 10 years  i bought a PC with  XP new in 2001 because Windows ME was so unstable  I bought one of them too before I did  XP and sold it after a few months .

 

PCs really have not got much better since Vista SP2  Vista was when they added native 1080p / x264 support in the processors the  1st real improvement in years is Kaby Lake  with native 4k and Hevc support  witch  will be out in 2017 witch will only support Windows 10 and Linux .

 

Windows 10  performance  varies with gaming  now older processes stuck on DX11  no better than Windows 7 or Windows 8.1  and the newer processors have a slight boost with DX 12 but  DX 12 was no reason to upgrade and soon these newer processors like Skylake  will be behind times  . Better Hevc  support will be for me but i will wait tell its been out for awhile and prices drop to upgrade to a windows 10 only processor. Adapt  or stay behind  .

 

 

[straycat19]

On 12/21/2016 at 2:37 PM, steven36 said:

Adapt  or stay behind  .

 

Sometimes you lead from the rear and the people in front are cannon fodder.  In the case of windows 10 this is definitely true.  We still refer to Windows 10 users as beta testers.  

 

I find windows 8.1 to be a very stable system and with the use of Classic Shell it works much the same as Windows 7.  

 

As far as gaming is concerned, before I went to Windows 10 just to play games on I would buy a PlayStation.  Then I don't have to worry about what Microsoft does or whether their next update is going to hose my games or the entire system.

[steven36]

1 hour ago, straycat19 said:

 

Sometimes you lead from the rear and the people in front are cannon fodder.  In the case of windows 10 this is definitely true.  We still refer to Windows 10 users as beta testers.  

 

I find windows 8.1 to be a very stable system and with the use of Classic Shell it works much the same as Windows 7.  

 

As far as gaming is concerned, before I went to Windows 10 just to play games on I would buy a PlayStation.  Then I don't have to worry about what Microsoft does or whether their next update is going to hose my games or the entire system.