In theory, KB 3013769 shouldn't try to install itself if it was successfully installed in the past. Funnily enough, the step-by-step instructions don't mention re-installing Kaspersky. If you get a blue screen, the KB article - now up to version 6.0 - has a complex workaround that involves manually uninstalling Kaspersky Antivirus and applying the patch. The same problem was reported back in December with the original update. This blue screen shouldn't come as a surprise to Microsoft. K|1.sys is a Kaspersky Antivirus network driver trace file. Many people using Kaspersky Antivirus report that installing the patch triggers a blue screen: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (kl1.sys). KB 3013769, the December 2014 update rollup for Windows 8.1 and Server 2012 R2, has been re-released as an optional update. It's still early in the game, but here are the problems I saw that cropped up overnight. There's also a Security Advisory about Public Key Cryptography User-to-User (PKU2U), called KB 3045755. Note that you must have Office 2013 SP1 before you can install any of these patches.
Not to be outdone, the Office team released a bewildering array of updates for Office 2013, including 13 security patches, two bulletins, and 42 non-security patches. Net security bulletin alone gives rise to 10 different downloadable patches. Yesterday Microsoft released dozens of patches for Windows in 11 bulletins covering 26 individually identified CVEs (common vulnerabilities and exposures), including 10 in Internet Explorer, four re-released security changes, and nine changes to non-security patch installers.
That's a problem for users, particularly because Microsoft's track record with patches is so bad - and this month is no exception.
Microsoft usually releases a list of non-security patches several days before the Black Tuesday rollout, but this month there was no information until several hours after the patches hit.
0 kommentar(er)
