Microsoft releases 24 optional Windows patches

[Karlston]

Documentation for the updates was a day late, but it's worth scanning the list to see if there's anything of interest for your setup

The official Windows Update list says 24 patches were released on April 19. But  it seems only two of them -- KB 3138378 and 3140245 -- were released that day, and the rest came out on April 20. The list itself wasn't updated until April 20. Documentation is kind of an afterthought for Microsoft these days.

 

Three of the patches fix problems with earlier security patches.

 

Here's what's on tap with this latest batch of fixes:

 

KB3103616 fixes a memory leak in the Wmiprvse.exe process that causes WMI queries not to work in Windows Server 2012 R2 or Windows Server 2012, for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3103709 fixes several issues with Windows Server 2012 R2-based domain controller, for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3125424 fixes Local Security Authority Subsystem Service (LSASS) deadlocks on Windows Server 2012 R2 or Windows Server 2012 that cause the server to stop responding to login requests from Exchange email clients such as Outlook, ActiveSync, and Outlook Web App as well as Remote Desktop connections, remote administrative commands through PowerShell, and local console logins. Issued for Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows Embedded 8 Standard, and Windows Server 2012.

 

KB3134179 adds performance counters for Remote Desktop (RD) Connection Broker in Windows Server 2012 R2.

 

KB3138378 is an update for Windows Journal. It's one of the mystery patches released without documentation on April 19. Intended for Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows Embedded 8 Standard, Windows Server 2012, Windows 7, Windows Server 2008 R2, Windows Server 2008, and Windows Vista

 

KB3139921 fixes a problem that affects operating systems using the "Windows Kerberos Security Feature Bypass." After you install security update 3126041, when you try to change your password through an untrusted domain, you may receive an error message that looks something like this: The security database on the server does not have a computer account for the workstation trust relationship. Intended for Windows Server 2008 and Windows Vista.

 

KB3140245 is the other mystery patch that was released without documentation on April 19. It adds a DefaultSecureProtocols registry key in Windows that allows users to change system-wide default protocols for WinHTTP and hardcodes Webio default protocols to include TLS 1.1 and TLS 1.2. Once the key is enabled, you have to set it manually. Intended for Windows Embedded 8 Standard, Windows Server 2012, Windows 7, and Windows Server 2008 R2.

 

KB3143777 addresses two issues, firstly when a critical error occurs when you shut down the cluster service. For example, the "[Shutdown] Groups failed to terminate in a timely manner. Cluster service will exit." error message is logged when you shut down the cluster service. And secondly, when data deduplication doesn't work on a BitLocker-encrypted cluster shared volume (CSV) provisioned by using a tiered storage space. It fails even if the drive is unlocked, and the following error message is logged: "This drive is locked by BitLocker Drive Encryption. You must unlock this drive from Control Panel." Intended for Windows Server 2012 R2.

 

KB3144474 addresses a problem that occurs after you install  security update 3081320 and the Team Foundation Server (TFS) application pool and the Certreq.exe process crashes when you run customized scripts with NcryptOpenStorageProvider involved. This issue occurs if the CNG key isolation service is disabled. Intended for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3144850 enables downgrade rights between Windows 10 IoT and Windows Embedded 8.1 Industry. The operating system is not activated when it downgrades from Windows 10 IoT to Windows Embedded 8.1 Industry. This update provides the required Product Keys that bridges Windows 10 IoT Enterprise and Windows Embedded 8.1 Industry. The change is made to the Windows Embedded 8.1 license file to accept the Product Keys that has been issued to the Windows 10 IoT Enterprise edition. Intended for Windows 8.1 and Windows Server 2012 R2.

 

KB3145126 addresses an issue in which a Windows Server 2008 R2 Service Pack 1 (SP1)-based DNS server that has Active Directory-integrated zones takes a long time to load DNS zones. The problem occurs after installing security update 3100465 or hotfix 3022780. Intended for Windows Server 2008 R2 x64 Edition.

 

KB3145384 increases the MinDiffAreaFileSize registry key value limit from 3GB to 50GB. You may encounter the event ID 25 error because of heavy I/O. To fix this issue, install the update and then set the MinDiffAreaFileSize registry to an appropriate size depending on the I/O amount. Intended for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3145432 fixes an issue where cluster nodes or virtual machines (VMs) go into failed state on a Windows Server 2012 R2 host and may not be migrated automatically to other cluster nodes.

 

KB3146600 fixes problems that occur when a backup is taken on a GUID partition table (GPT) formatted drive in Windows Server 2012. Wbengine.exe crashes when you run a backup on a GPT formatted drive in Windows Server 2012. Intended for Windows Embedded 8 Standard and Windows Server 2012.

 

KB3146601 addresses issues when you use Group Policy Management Console (GPMC) to import a backed up GPO. The import may fail if a file is held open in one of the temporary directories that is created during the import process. When this issue occurs, you receive the following error message: "The process cannot access the file because it is being used by another process" and the GPMC will then roll back the import process, which may result in the target policy being deleted. Intended for Windows 8.1 and Windows Server 2012 R2.

 

KB3146604 fixes Windows Management Instrumentation (WMI) service crashes. When this issue occurs, users may find that every functionality that uses the WMI interface will fail. For example, Virtual Machine Manager (VMM) uses the WMI interface to show the status of virtual machines (VMs) on a Hyper-V host. If the WMI service on that Hyper-V host crashes, VMM can't show the status of the VMs on that host. In addition, all services that share the same service host process with the WMI service will also become unavailable, and users may experience other problems that are not related to WMI service itself. Intended for Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, and Windows Server 2012.

 

KB3146621 fixes an issue where the iSCSI target service crashes randomly. This occurs when the Windows Server 2012 R2-based computer has the iSCSI Target Server role installed and the iSCSI target server encounters random I/O error. Intended for Windows Server 2012 R2

 

KB3146627 addresses a problem where mapped network drives to a DFS share don't work for subsequent users. This issue occurs when User Account Control (UAC) is enabled and the EnableLinkedConnections registry value is set to 1. Intended for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3146751 fixes a problem that occurs with  App-V logon in Windows Server 2012 R2. When you log on to App-V and then log off, the next time you try to log on using Mandatory User Profiles (Ntuser.man), you can't log on and receive a "Logon is not possible" error message. When you use Roaming User Profiles (NTuser.dat), a temporary profile will be created on the next logon. Intended for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3146978  fixes issues when connecting with Remote Desktop Services (RDS) and working on any redirected resources (drives, printers, and ports) becomes very slow. Intended for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

 

KB3148146 fixes a problem that occurs when not all the printer queues settings are restored correctly after you restore a backup by using the Printbrm.exe command-line tool. To be specific, the settings that are not restored are in the PrinterDriverData structure. The corresponding settings are not in the backup file itself, meaning that it never even got backed up in the first place. Intended for Windows Server 2012 R2.

 

KB3148217 fixes a problem that occurs on a Windows Server 2012 R2-based Work Folders sync server. High network usage may occur when the File Server Resource Manager (FSRM) file screening is implemented on the Work Folders sync server to block certain file types. For example, audio or video files, image files, executables, system files, and Outlook data files. The FSRM file screening blocks the files when they are transferred to the Work Folders sync server. The Work Folders service then tries to re-sync the files, which causes increased network usage. Intended for Windows Server 2012 R2.

 

KB3148812 enables Windows Server Update Services (WSUS) to natively decrypt Electronic Software Distribution (ESD). See "Known issues with KB 3148812" for important details. Intended for Windows 8.1, Windows Server 2012 R2, and Windows Server 2012.

 

KB3149157 fixes various network and computer issues that occur when TCP ephemeral ports are exhausted in Windows 8.1 or Windows Server 2012 R2. The update includes additional reliability improvements. Intended for Windows 8.1, Windows RT 8.1, and Windows Server 2012 R2.

Source: Microsoft releases 24 optional Windows patches (InfoWorld - Woody Leonhard)

[steven36]

A lot  of hot fixes on Windows 8.1 here lately  noting much for windows 7 at all  they  dont even want to fix update times for it  OOOO ...

[Actarusse]

[oliverjia]

24 update sounds a lot to me. Could they possibly get some solid QC personnel? 

Microsoft, please don't release something in a rush, then patch it to death along the way. That's waste of a lot of bandwidth and computing power. 

[Sylence]

That's why they created "cumulative updates"  2 years ago

[vibranium]

No cumulative updates or rollups are planned for 7, 8 and 8.1

 

[humble3d]

 

KB3140245 is the other mystery patch that was released without documentation on April 19. It adds a DefaultSecureProtocols registry key in Windows that allows users to change system-wide default protocols for WinHTTP and hardcodes Webio default protocols to include TLS 1.1 and TLS 1.2. Once the key is enabled, you have to set it manually. Intended for Windows Embedded 8 Standard, Windows Server 2012, Windows 7, and Windows Server 2008 R2.

 

MYSTERY MEAT ! 

[davmil]

6 minutes ago, humble3d said:

 

KB3140245 is the other mystery patch that was released without documentation on April 19. It adds a DefaultSecureProtocols registry key in Windows that allows users to change system-wide default protocols for WinHTTP and hardcodes Webio default protocols to include TLS 1.1 and TLS 1.2. Once the key is enabled, you have to set it manually. Intended for Windows Embedded 8 Standard, Windows Server 2012, Windows 7, and Windows Server 2008 R2.

 

MYSTERY MEAT ! 

Were any instructions on how to set it manually included in the (not) documentation?  Thanks for the info.

[steven36]

14 hours ago, vibranium said:

No cumulative updates or rollups are planned for 7, 8 and 8.1

 

How is this any news?  there's not been no update roll ups for  since  January 2015 onwards .

 

When i done patch Tuesday Windows 8.1 April  most of  the recommenced  updates were fixes to do with running  a VM on windows 8.1  a lot fixes  not about windows

 

14 hours ago, oliverjia said:

24 update sounds a lot to me. Could they possibly get some solid QC personnel? 

Microsoft, please don't release something in a rush, then patch it to death along the way. That's waste of a lot of bandwidth and computing power. 

 

There is no 24 updates out  over  on woody's site  some lady on enterprise windows 8.1 only has 11 fixes

 

 

http://www.askwoody.com/2016/microsoft-releases-24-optional-windows-patches/comment-page-1/

 

On my OEM Windows 8.1 I only  have 11 optional  updates

 

 

So there's only 11 patches  on windows 8.1  and on windows 7  I'm not going  to check for updates on it  tell patch Tue May because its so slow checking for updates its not worth it.

 

 

 

[D1v1n3D]

I don't get why they just cant fix what is broken and stop breaking what isn't

[straycat19]

Seems like there are a lot of patches to fix crashes in WMI, obviously not a problem until lately, which means they patched something that had a tendency to break WMI on some systems.  Notice that some of them are related to the use of VMs of which I am a huge user.  Personally none of my Windows 8.1 systems have exhibited any of these WMI problems, probably because I quit patching them last year.

[steven36]

29 minutes ago, straycat19 said:

Seems like there are a lot of patches to fix crashes in WMI, obviously not a problem until lately

This is just a problem with  enterprise, on Windows 8.1 OEM i've not had no problem with nothing  in months . I would get strange  errors sometimes when i  1st set the pc up after doing windows updates it went away so what ever it was they fixed it . So doing patches could botch something or it could fix something . On Windows 8.1  or Windows 7 you can uninstall a botched update . So not patching at all is procrastination or you're  just overly  paranoid .

 

Its seems like most the patches are to fix bugs for people who run VM  in windows 8.1 or Windows Server 2012 . I never bothered to install VM on this one i have on my other pc though .  

[straycat19]

14 minutes ago, steven36 said:

This is just a problem with  enterprise, on Windows 8.1 OEM i've not had no problem with nothing  in months . I would get strange  errors sometimes when i  1st set the pc up after doing windows updates it went away so what ever it was they fixed it . So doing patches could botch something or it could fix something . On Windows 8.1  or Windows 7 you can uninstall a botched update . So not patching at all is procrastination or you're  just overly  paranoid .

 

I mainly run Enterprise versions, though I do have some Pro versions also.  I think paranoid is drinking the kool-aid and thinking you need to patch a stable operating system just because Microsoft told you to do it.  They cry 'Wolf' so many times that they have people in constant fear that if they don't patch their systems some 'hacker' is going to take over their system.  When in reality it is the user themselves who are the critical flaw in the system that is exploited and until Microsoft makes Windows secure against users they can patch all they want but it isn't doing any good.  Microsoft's track record with patches isn't good enough for me to put my trust in anything they say or do anymore.  Their engineers must be smoking some of that stupid weed Reefa posted about.  

http://www.nsaneforums.com/topic/267267-does-marijuana-make-you-stupid/

 

[steven36]

2 hours ago, straycat19 said:

 

I mainly run Enterprise versions, though I do have some Pro versions also.  I think paranoid is drinking the kool-aid and thinking you need to patch a stable operating system just because Microsoft told you to do it.  They cry 'Wolf' so many times that they have people in constant fear that if they don't patch their systems some 'hacker' is going to take over their system.  When in reality it is the user themselves who are the critical flaw in the system that is exploited and until Microsoft makes Windows secure against users they can patch all they want but it isn't doing any good.  Microsoft's track record with patches isn't good enough for me to put my trust in anything they say or do anymore.  Their engineers must be smoking some of that stupid weed Reefa posted about.  

http://www.nsaneforums.com/topic/267267-does-marijuana-make-you-stupid/

 

Drinking the Koolaid ? Everyone on my network does updates except for get windows 10 updates. for years we just kept them on auto updates . tell windows 10 came out.  I only  uninstalled a botched update a few times because i read it  on here they were . And really we never had any troubles because of updates its better to be safe than sorry . If  Microsoft never made patches  every PC would still be catching virus like they was before XP SP2 came out and every O/S would be so unstable  no one could stand windows. .

 

Most of the time it takes Microsoft  a few years to get all the bugs out of them . Windows 7 SP1  was nothing  but hot fixes  of bugs that they found in windows 7 i remember  being on windows 7 right before SP1 came out hunting down  hotfixes to fix bugs in it .  there is no O/S that dont have some bugs or security holes that need plugged or fixed and that's just reality... If Windows were safe  and bug free you  think  they would waste all that money giving you updates month after month year after year? No they wouldn't.

 

Old article  on XP Average time to infection: 4 minutes

http://blog.chron.com/techblog/2008/07/average-time-to-infection-4-minutes/

 

If  you not patched since June 2015 you're vulnerable to windows kernel  exploits , IE exploits  , Badlock bug  and no telling what else  so you're smoking  better weed than Microsoft DEVs  are  . It's not cool  to spread a message that  is dangerous  like this.  

 

[vibranium]

13 hours ago, steven36 said:

How is this any news?  there's not been no update roll ups for  since  January 2015 onwards .

 

 

I was replying to the post on top of mine, if you must know.

 

 

 

[steven36]

6 hours ago, vibranium said:

 

I was replying to the post on top of mine, if you must know.

 

 

 

People want to complain about hotfixes  on windows updates that its you're  choice  to install or not?  When it use too be you had too hunt all over Microsoft or go to the  hotfix forum to find them or  you're pc would stay full of bugs tell a service pack came out if you didn't hunt down a fix  for you're problem. But forcing people to take updates  is a good way to  mess up everything  and one day  on windows 10 it's most likely  going mess up millions and millions of pcs and Microsoft will learn there lesson  at  the end users expense,   but i guess people not patching at lest there security updates and complaining about bugs caused them to be this way..

[vibranium]

12 hours ago, steven36 said:

People want to complain about hotfixes  on windows updates that its you're  choice  to install or not?  When it use too be you had too hunt all over Microsoft or go to the  hotfix forum to find them or  you're pc would stay full of bugs tell a service pack came out if you didn't hunt down a fix  for you're problem. But forcing people to take updates  is a good way to  mess up everything  and one day  on windows 10 it's most likely  going mess up millions and millions of pcs and Microsoft will learn there lesson  at  the end users expense,   but i guess people not patching at lest there security updates and complaining about bugs caused them to be this way..

 

What are you talking about? You're making no sense.

 

[steven36]

16 minutes ago, vibranium said:

 

What are you talking about? You're making no sense.

 

If i didn't make any sense to you