KB3095681 caused: "SSMS Has detected a problem that may significantly degrade product functionality" (solved)

Question

KB3095681 caused: "SSMS Has detected a problem that may significantly degrade product functionality" (solved)

bas de zwart

Ten Centuries

Points: 1117
More actions
February 28, 2017 at 4:15 am

#319149

Since this weekend my SSMS 2016 is extremely slow and gives a popup message that there is a 'problem' with the installation.
SSMS Had detected a problem that might significantly impact functionality:
SSMS info:
Microsoft SQL Server Management Studio                        13.0.16106.4
Microsoft Analysis Services Client Tools                        13.0.1700.441
Microsoft Data Access Components (MDAC)                        6.1.7601.17514
Microsoft MSXML                        3.0 6.0
Microsoft Internet Explorer                        9.11.9600.18537
Microsoft .NET Framework                        4.0.30319.42000
Operating System                        6.1.7601
(Updates and patches from MS were installed, no third party software was installed, looks like this is the culprit).
My 'tech team' assures me no significant changes to Group Policies etc.. have taken place that could explain this sudden error.
I've done the following to fix the issue but have not solved it yet.
- Ran Repair, no errors or warnings.
- Deinstalled completely then reinstalled
- Searched BING, DuckDuckGo & Google for this error but all three had 'no results', which is nifty in it's own right.
I'm a bit stuck as to what else I might try. Has anyone else ever run into this issue, or anyone have ideas how I can solve it?
SMSS Is indeed a lot slower, especially when starting up.
Any help is appreciated!
(ps: The one saying 'reinstall windows' should cut up their IT card and find a job as PE teacher).
pps: Solved the culprit was KB3095681

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

bas de zwart Ten Centuries Points: 1117 More actions · Answer 1

During 4 days of absence, windows updates for VS2015 were installed. I have just done a system restore and it looks like all errors are gone.
I'm now doing investigation into which update it was exactly that (basically) wrecked my system.

bas de zwart Ten Centuries Points: 1117 More actions · Answer 2

System Restore worked for about 3 minutes, then the company policies repushed all updates to my machine and it broke again.

*eats frustration*

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 3

Reinstall Windows 😀

Seriously now. Is SSMS usable, or does is close after displaying that dialog?
Is that the latest version of SSMS?

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Phil Parkin SSC Guru Points: 246695 More actions · Answer 4

bas de zwart - Tuesday, February 28, 2017 5:42 AM
System Restore worked for about 3 minutes, then the company policies repushed all updates to my machine and it broke again.
*eats frustration*

That's a pain. If you find out which updates cause this, please post back, as it may be useful for others.

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.

bas de zwart Ten Centuries Points: 1117 More actions · Answer 5

GilaMonster - Tuesday, February 28, 2017 5:50 AM
Reinstall Windows 😀
Seriously now. Is SSMS usable, or does is close after displaying that dialog?
Is that the latest version of SSMS?

It's the latest version. One of the first steps for me was to deinstall, download and reinstall.
SSMS Also 'said' there was an update available, which I installed, hoping it would fix this error.

Absolutely latest version available from MS.

It's slow and seems sluggish. A bit worried that it would send unstable commands to my production servers so I'm not using it until I'm sure it's 100% fixed. Logging into remote servers for SSMS access until it's figured out.

bas de zwart Ten Centuries Points: 1117 More actions · Answer 6

Phil Parkin - Tuesday, February 28, 2017 5:51 AM
bas de zwart - Tuesday, February 28, 2017 5:42 AM
System Restore worked for about 3 minutes, then the company policies repushed all updates to my machine and it broke again.
*eats frustration*
That's a pain. If you find out which updates cause this, please post back, as it may be useful for others.

Yes will do!

I've identified the offending windows update. After deinstalling it my problem is gone.
The culprit is KB3095681 (Update for MS Vistual Studio) with version 14.0.23317.

Please note. It could very well be that some kind of weird combination thing is going on. Not all updates are approved via our WSUS, meaning that this KB could have a dependancy missing on another KB. I can't really dig deeper because I have no real control over which updates I'm seeing at work. But it could very well be that this KB in itself is fine, but that I'm missing another pre-requisite which causes this warning, which is why uninstalling this KB seems to fix things.

Phil Parkin SSC Guru Points: 246695 More actions · Answer 7

bas de zwart - Tuesday, February 28, 2017 11:16 PM
Phil Parkin - Tuesday, February 28, 2017 5:51 AM
bas de zwart - Tuesday, February 28, 2017 5:42 AM
System Restore worked for about 3 minutes, then the company policies repushed all updates to my machine and it broke again.
*eats frustration*
That's a pain. If you find out which updates cause this, please post back, as it may be useful for others.
Yes will do!
I've identified the offending windows update. After deinstalling it my problem is gone.
The culprit is KB3095681 (Update for MS Vistual Studio) with version 14.0.23317.
Please note. It could very well be that some kind of weird combination thing is going on. Not all updates are approved via our WSUS, meaning that this KB could have a dependancy missing on another KB. I can't really dig deeper because I have no real control over which updates I'm seeing at work. But it could very well be that this KB in itself is fine, but that I'm missing another pre-requisite which causes this warning, which is why uninstalling this KB seems to fix things.

Thanks for posting the follow-up. I checked my system and I have that update installed & do not experience the behaviour you are seeing, so I do think that there must be more going on. Happy hunting!

If you haven't even tried to resolve your issue, please don't expect the hard-working volunteers here to waste their time providing links to answers which you could easily have found yourself.