Kb3102810 windows 7 x64 для чего
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I see that two updates were released recently, KB3102810 and KB3102812, which resolve the following issue on Windows 7/Server 2008 R2 and Windows 8.1/Server 2012 R2 respectively:
When you install updates by using System Center Configuration Manager, the installation takes a long time, and System Center Configuration Manager becomes overloaded.
Are there any further technical details available about this issue? Is Windows 8 unaffected, or is there simply no update being made available for it?
Answers
All replies
Microsoft required an upgrade to 8.1 two years after GA of Windows 8. See here: http://support2.microsoft.com/gp/lifewinfaq?wa=wsignin1.0#Microsoft-Windows-81
So, update to 8.1 and apply all the latest updates, including the referenced hotfix. Then you will be at a supported version of that OS.
It appears to be, unless it does a lot more than this, a rather idiotic update for no apparent good reason. Of course, what’s idiotic, is to think we are going to continue blindly accepting updates from Microsoft, when it is clear to me, that without a lot more visibility on what EACH update does, eventually they will release a really destructive update. I found this elsewhere on a Microsoft forum, and so, I am certainly NOT installing this. FYI, I have Windows 8.1 and this showed up on my updates:
KB3102812 breaks Windows Update user interface on Windows 8.1
Thursday, November 12, 2015 7:44 AM
Before the KB update manual windows update behaves as expected:
3. Reports Downloading updates stage
4. Reports Preparing to install stage
5. Reports Installing updates stage
After the KB3102812 is installed the stage 5 no longer exists. It installs updates correctly (typically Windows Defender definitions) but still reports «Preparing to install» stage and after a while «Done» stage. I can reproduce it on two different Windows 8.1 machines. Removing the KB3102812 solves the issue and brings back expected behavior.
Kb3102810 windows 7 x64 для чего
This forum has migrated to Microsoft Q&A. Visit Microsoft Q&A to post new questions.
Answered by:
Question
I see that two updates were released recently, KB3102810 and KB3102812, which resolve the following issue on Windows 7/Server 2008 R2 and Windows 8.1/Server 2012 R2 respectively:
When you install updates by using System Center Configuration Manager, the installation takes a long time, and System Center Configuration Manager becomes overloaded.
Are there any further technical details available about this issue? Is Windows 8 unaffected, or is there simply no update being made available for it?
Answers
All replies
Microsoft required an upgrade to 8.1 two years after GA of Windows 8. See here: http://support2.microsoft.com/gp/lifewinfaq?wa=wsignin1.0#Microsoft-Windows-81
So, update to 8.1 and apply all the latest updates, including the referenced hotfix. Then you will be at a supported version of that OS.
It appears to be, unless it does a lot more than this, a rather idiotic update for no apparent good reason. Of course, what’s idiotic, is to think we are going to continue blindly accepting updates from Microsoft, when it is clear to me, that without a lot more visibility on what EACH update does, eventually they will release a really destructive update. I found this elsewhere on a Microsoft forum, and so, I am certainly NOT installing this. FYI, I have Windows 8.1 and this showed up on my updates:
KB3102812 breaks Windows Update user interface on Windows 8.1
Thursday, November 12, 2015 7:44 AM
Before the KB update manual windows update behaves as expected:
3. Reports Downloading updates stage
4. Reports Preparing to install stage
5. Reports Installing updates stage
After the KB3102812 is installed the stage 5 no longer exists. It installs updates correctly (typically Windows Defender definitions) but still reports «Preparing to install» stage and after a while «Done» stage. I can reproduce it on two different Windows 8.1 machines. Removing the KB3102812 solves the issue and brings back expected behavior.