The problems of Microsoft Black Tuesday continues to accumulate. Yesterday brought to light problems with KB 2952664, the seventh patch with that name, which cannot be installed on a large number of machinesto Windows 7 Nowthere are reports of four other patch defective. It’s too early to say exactly what is causing the problems, but ifyou have a headache, you're not alone- and there are no solutions.
KB 3000061, my choice in advance to "more likely than splat," is an update of kernel-mode drivers, MS 14-058. And 'one of the patches zero-day Microsoftthis month - there are very limited attacks, butidentified in naturethat use this security hole. A thread on the failure to install on Server 2012 machines. Posters jcs916describes a problem with the installation of KB 3000061 8.1 on a Windows machine:
After the restart began designingand then gave an "Errorconfiguring Windows updates, restoring the changes" errorafter restarting Windows update still showed the same 18updates. I have run the troubleshooter updatefrom http://support.microsoft.com/kb/949358and showed that fixed3 errors. Thesame thing happened when I tried toinstall all the updates from the control panel. I then installedall the updates one at a time and everything worked fine, except KB3000061. I have run thetroubleshooter again and manually installed KB3000061. Same error on reboot.
On Tuesday, Microsoft has released seven security patches separately identifiedthat were not associated with security bulletins. One of them, KB 2984972, is not going well. According to Microsoft:
[Patch] allows the client to Remote Desktop Connection to perform limited administrative access. It also enables remote desktop service running on a host RDto run the administration restricted.
AndrewKelly, posting on TechNet forum, says he has had problems with packagesAutodesk after applying the patch:
AutoCAD itself was not affected, but Revit, Navis, and DWG TrueView all were. It is not evengot to the bottom of why (the explanation for the upgrade does not sound as makes no difference), but simply removing the update from the PC clienthas set packages that will do me for now.
Another post on that thread (nzdude) says that theApp-V package ofFrontRange Solutions HEAT 7.2.2 crashesafter applying KB 2984972, and uninstall the patch has solved the problem. Other (aeg684) says that Trillian Astra, FileMakerPro 12, SnagIt and V11have the same symptoms. Other (P4PPY) says that the interaction of client ININ has the same problems.
Harjit Dhaliwal, PatchManagement on the forum, quotes a colleague as saying:
Heads up, KB2984972on the server 2008R2RD caused problems with our Wyse thin clients -has caused all of them to cover the desktopacross multiple monitors, multiple monitors rather than submitto the host operating system. After uninstalling and rebooting clients are presented with multiple monitors again.
Following KB 2949927, which adds support SHA-2 hashing for Win7and Server 2008 R2.Roy Adams, posting on the forum Patch Management,says:
All 3 of my assistants Win2008R2SP1 stuck ina triple auto-restart Windows Update Failure this morning. All had 16 updates ... in the end they did recover after 2 or 3 auto-rollback restart ... Checking for updates on them all now shows this still to install: Security Update for Windows Server 2008 R2x64 Edition (KB2949927)
KB2949927 will installand restore the changes at the next boot if you have BitLocker off. The "fvevol" must be started, and must be recorded in the value "LowerFilters" in this registry key: HKEY_LOCAL_MACHINE \SYSTEM \ CurrentControlSet \ Control \ Class \ {71a27cdd-812A-11D0-bec7-08002be2092f}. If you do not, KB2949927will fail!
Finally, a rollup no security update, KB2995388 - Tuesday also handed out - is causing problems with VMware.After installing the patch, every time you try to start a virtual machine, you get a message: "It is not enough physical memory is available to power on this virtual machine with the settings." People should not install VMware KB 2995388; if you have, you may want to uninstallit.t / h SB
No comments:
Post a Comment
Note: only a member of this blog may post a comment.