Breaking

Friday, April 17, 2015

Patch KB 3013769, Skype for Business, Windows 10 nagware

Several of this month's Black Tuesday patches ar already showing signs of bother


Microsoft typically releases an inventory of non-security patches many days before the Black Tuesday rollout, however this month there was no data till many hours once the patches hit. that is a tangle for users, significantly as a result of Microsoft's log with patches is thus dangerous -- and this month is not any exception.

Yesterday Microsoft free dozens of patches for Windows in eleven bulletins covering twenty six one by one known CVEs (common vulnerabilities and exposures), together with ten in net someone, four re-released security changes, and 9 changes to non-security patch installers. The .Net security bulletin alone provides rise to ten totally different downloadable patches.

Not to be outdone, the workplace team free a unclear array of updates for workplace 2013, together with thirteen security patches, 2 bulletins, and forty two non-security patches. Note that you just should have workplace 2013 SP1 before you'll install any of those patches.

There's conjointly a Security consultive regarding Public Key Cryptography User-to-User (PKU2U), known as K 3045755.

It's still early within the game, however here ar the issues I saw that cropped up long.

KB 3013769, the Dec 2014 update rollup for Windows eight.1 and Server 2012 R2, has been re-released as AN facultative update. many of us victimization Kaspersky Antivirus report that putting in the patch triggers a blue screen: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (kl1.sys).

k|1.sys may be a Kaspersky Antivirus network driver trace file.

This blue screen should not come back as a surprise to Microsoft. a similar drawback was rumored back in Dec with the initial update.

If you get a blue screen, the K article -- currently up to version vi.0 -- contains a advanced workaround that involves manually uninstalling Kaspersky Antivirus and applying the patch. interestingly enough, the piecemeal directions do not mention re-installing Kaspersky.

In theory, K 3013769 should not try and install itself if it absolutely was with success put in within the past. however i am  seeing reports that Windows Update is attempting to put in it once more, though it's listed in each put in Updates and Update History. that is significantly unwelcome news if you are running a problematic version of Kaspersky Antivirus.

Poster Andres P on the Answers forum theorizes that "binaries WERE updated on MS Update web site (this may be a true) and technologies hoping on WSUS/SCCM picked it up and deployed once more (since original readying point in time is passed)."

Microsoft conjointly re-re-re-released K 2990214, the high priority "update that supports you to upgrade from Windows seven to a later version of Windows." The last re-re-release was last Tuesday, thus Microsoft's churning through one thing. As i discussed last week, this patch is meant to form it easier to upgrade Windows seven systems to Windows ten. Again, i have not seen it offered on my Windows seven PCs, however i could simply be lucky. Or blocked.

Important note: K 2990214 contains a replacement version of the Windows Update engine. Buried within the K article, you'll see that the update applies not solely to Windows seven SP1, however conjointly to Windows Server 2008 R2. however the K article bewilderingly admonishes: "This update for Windows Server 2008 R2 doesn't support you to upgrade to a later version of Windows." We're therefore left with a patch to Server 2008 R2's Windows Update engine that, in keeping with Microsoft, does not do what the K article says it's planning to do. that is a distressing scenario, however not thus uncommon within the wacky world of Windows patches.

The Skype for Business rollout may be a bit odd. Microsoft has been warning Lync users for 6 months that Lync is dwindling, replaced by Skype for Business. Microsoft has a political candidate workplace journal regarding the transition. The software system rollout, strangely, comes within the style of AN facultative patch, KB 2889923, which says, "After you apply this April 14, 2015 update, Lync 2013 are upgraded to Skype for Business." additional down the page, the K article advises you to conjointly install K 2889853, KB 2863908, and K 2817430 once putting in K 2889923.

Here's wherever we tend to begin disappearing down the hollow, as a result of K 2889853 conjointly says, "After you apply this April 14, 2015 update, Lync 2013 are upgraded to Skype for Business." i believe that is inaccurate. If you chase your tail long enough, you'll come back to the conclusion that the previous patch, KB 2889923, will the upgrading, and also the latter patch, KB 2889853, "resolves a difficulty within which the 'Help is not working' error happens in Microsoft Skype for Business."

The second further patch, KB 2863908, installs a fix for Lync that was free last month. The third further patch, KB 2817430, is simply workplace 2013 SP1, that was free over a year past.

None of these patches seems within the official Windows Update/WSUS list.

Tobie Fysh has written an intensive guide to the batty and bolts of moving from Lync to Skype for Business, that has further recommendations for repair, together with a register modification.

For those of you running a WSUS server, there are reports of issues obtaining the Apr 2015 patches to set on Server 2012 R2. the matter hasn't been acknowledged by Microsoft, and it's not clear however widespread the matter may well be, however the foremost recent reports ar from early Wed morning.

The lack of advanced notification regarding non-security patches and missing K articles at the time the updates extended the chute has changed into a major drawback. Microsoft suddenly concluded advance notification of security patches in Gregorian calendar month. It looks that the sole people that get advanced notice of returning patches ar people who work for organizations that purchase Premiere Support. currently it's beginning to appear as if the unwashed plenty will not even get an opportunity to appear at patch details till hours once they have been applied through Automatic Update. that is not in anybody's best interests.

Source

No comments:

Post a Comment