Revised and later released Windows Updates March 2017

Topic

New Reply

There has been some movement in Windows Update in the last 24 hours, some important and some with little impact and normally not noticeable.

5 new patches were released late and this was mentioned in few other posts:
KB3150513 was re-released for Windows 10 1511 32/64 bits, Windows 10 1607 32/64 bits and a first time for Windows Server 2016, in total 5 patches.

The server patch is a surprise to me, as KB3150513 require the functionality equivalent to what KB2952664 brings to Windows 7, but KB2952664 was never released for the server version Windows 2008 R2, although I think the patch for Windows 7 64-bit can be installed manually on the server if desired.

The releases of KB3150513 for Windows 10 and Windows 2016 makes me think again about the recommendation for KB2952664 for Windows 7.
I have to say that I am not interested at all in what a lot of people consider snooping when doing this analysis. The fact is that by installing KB2952664/KB3150513 on Windows 7, the functionality of Windows 7 in this area is brought at the same level with the functionality of Windows 10, desirable or not.

The other evolution on Windows Update is that 14 patches, all of them related to .NET Framework different versions and different OS from November and December 2016 have been revised. It is likely that all have had metadata revised in relation to supersedence, which is a regular occurrence and most people would not notice anything being changed.

4 users thanked author for this post.

Sailor, woody, walker, PhotM

Reply | Quote

Replies

Your on top of it CH100,

Went a checked my W 10.0 1607 RR IP partition and sure enough there is “KB3150513”.

Woody is on it too:
http://www.infoworld.com/article/3065380/microsoft-windows/mystery-solved-kb-3150513-is-another-windows-10-update-enabling-patch.html

Microsoft is not:
https://support.microsoft.com/en-us/help/3150513/latest-compatibility-definition-update-for-windows

Installed on my Release Ring(RR) Beta partition. No Restart required, no issues so far.

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

Microsoft is not:
https://support.microsoft.com/en-us/help/3150513/latest-compatibility-definition-update-for-windows

I think this article was updated since you checked it.

Update detail information

Prerequisites

This update will be offered only if the following prerequisite updates are installed:

On Windows 10 Version 1607: the March 14, 2017, cumulative update (KB4013429)
On Windows 10 Version 1511: the August 9, 2016, cumulative update (KB3176493 )
On Windows 8.1 and Windows 8: update 2976978
On Windows 7 Service Pack 1 (SP1): update 2952664
On Windows 7 RTM: update 2977759

Article ID: 3150513 – Last Review: Mar 16, 2017 – Revision: 7

1 user thanked author for this post.

walker

Reply | Quote

I am talking about, what is in it, what it is about? Not what it applies to…..

--------------------------------------

1. Tower Totals: 2xSSD ~512GB, 2xHHD 20 TB, Memory 32GB

SSDs: 6xOS Partitions, 2xW8.1 Main & Test, 2x10.0 Test, Pro, x64

CPU i7 2600 K, SandyBridge/CougarPoint, 4 cores, 8 Threads, 3.4 GHz
Graphics Radeon RX 580, RX 580 ONLY Over Clocked
More perishable

2xMonitors Asus DVI, Sony 55" UHD TV HDMI

1. NUC 5i7 2cores, 4 Thread, Memory 8GB, 3.1 GHz, M2SSD 140GB
1xOS W8.1 Pro, NAS Dependent, Same Sony above.

-----------------

Reply | Quote

You will never see that info, unless something completely exceptional happens at Microsoft 🙂
Until then, you may be able to find something by going through the files contained in the update.
It is generally believed that this update is similar to definition updates, this time for the functionality included in KB2952664 in Windows 7 or equivalent in other operating systems.
Think about an antivirus engine and definition updates for a loose analogy.

Reply | Quote

ch100 wrote:

I have to say that I am not interested at all in what a lot of people consider snooping when doing this analysis. The fact is that by installing KB2952664/KB3150513 on Windows 7, the functionality of Windows 7 in this area is brought at the same level with the functionality of Windows 10, desirable or not.

I think I understand.

The problem with KB 2952664 has to do with telemetry. Not sure if there’s enough reason to install in Win7, if you aren’t moving to Win10.

1 user thanked author for this post.

walker

Reply | Quote

🙂

Reply | Quote

Wow a frenzy of updates this week.

WUShowHide now sees this available for a Win 10 system that was updated 2 days ago:

I suppose I’ll give it a whirl and see if anything interesting happens…

Done.

Didn’t even require a reboot.

-Noel

Reply | Quote

My Windows 7 test system, up to date as of 2 days ago, saw this one just now. A blast from the past!!! 🙂

-Noel

Reply | Quote

CheckSUR offered by Windows Update?
I have never seen it offered by Windows Update but I “installed” it many times.
WU must “think” that there is major CBS corruption on that system.
It is worth looking through the logs and see what this is about, as I think it is very rare to catch an instance of CheckSUR being offered. 🙂

Reply | Quote

There was no corruption by any means I could see. In fact, per PhotM’s advice I completed a DISM /Online /Cleanup-Image /ScanHealth just yesterday on it and it passed with flying colors.

Nor did the same command today after the above update turn up any problems.

This one is just weird.

-Noel

Reply | Quote

Do those DISM commands work in Windows 7?
I thought they were just experimental or early and incomplete implementation in Windows 7.
There are the master logs for CBS under C:\Windows\Logs and may be another location specific to CheckSUR, but I think that one is created only after the scanner is run.
Could you please check if you don’t have logs above 2GB under C:\Windows\Logs\CBS which cannot be compressed by the 32-bit makecab.exe which may have triggered the offer of CheckSUR?
Normally the big log files would be associated with a large amount of temporary files under C:\Windows\Temp.
Just thinking about some common issues.
I am sure that you have already checked those issues which are unlikely to happen on your systems anyway.

Reply | Quote