For those of you wondering whether you have the latest version of the Windows Update Servicing Stack — the part of Windows Update that actually does
[See the full post at: The most recent Servicing Stack Updates]
|
Patch reliability is unclear. Unless you have an immediate, pressing need to install a specific patch, don't do it. |
-
The most recent Servicing Stack Updates
- This topic has 108 replies, 23 voices, and was last updated 6 years, 6 months ago.
AuthorViewing 28 reply threadsAuthor-
-
I think Karl’s point is less about bugs and more about the fact that if the SSU is required in order to apply a Security Update, then the SSU itself is also a Security Update.
1 user thanked author for this post.
-
-
What’s the speciality of 1507 KB4132216?
1 user thanked author for this post.
-
-
-
-
If KB3172605 was previously installed, no need to reinstall it.
The SSU KB3177467 -v2 issued this month has a classification change to “security,’ which the original did not have. SSUs are exclusive. That means they will only show up in the Windows Update “important” queue if there no other pending updates. In other words, the queue must be cleared by either installing the other updates or hiding them.
1 user thanked author for this post.
-
HTH for other readers of this blog like me. An early post above referred to KB2172605. It is an anon post above no. 214478. After searching DuckDuckGo and M$ update Catalog, it appears there is ~no~ such KB; apparently the Anon writer meant to refer to KB3172605 (note that he or she posted a link re 3172605, in that post). People: It is ****** confusing enough making sense of these M$ escapades sometimes; don’t make it worse with your own easy-to-fix typos. Proofread before you post!
1 user thanked author for this post.
-
-
-
…I have two questions: 1) was V2 of KB3177467 introduced in September 2018 for those who had never installed KB3177467 when introduced back in 2016?
Yes.
, and 2) what is the significance of KB3172605 in relation to KB3177467 that was mentioned? If I never installed it back in 2016 and is in my list of hidden updates should I unhide and install the update?
Yes, unhide and install the update since it does contain two important security enhancements.
KB3172605 was simply re-released in September 2016. I too have had KB3172605 hidden since it was noted that it could break Intel Bluetooth drivers. Lenovo computers were seeing this issue. The solution was to uninstall the drivers, install the updates, and then reinstall the drivers. See these two links about the Bluetooth issue:
https://www.askwoody.com/tag/kb-3172605/
https://news.thewindowsclub.com/please-uninstall-kb3172605-88008/
NOTE: I just finished installing KB3172605 on this Win7 test computer. It installed with no issues, with the caveat that this computer does not have a Bluetooth card and is not a Lenovo computer. I have also removed KB3172605 from my list of updates to avoid whenever I reinstall Windows 7, since there is an easy workaround for the Bluetooth issue where appears to have affected only Lenovo computers???
The article says that KB3172605 should be installed after KB3177467. However, what is unclear is whether I had installed KB3177467 – V1 or KB3177467 – V2 on September 12, 2018.
KB3177467 v1 and v2 contain the exact same Windows Update servicing stack files. The only difference is that KB3177467 v2 will now be listed as a Security Update in “View installed updates” in Programs and Features under Control Panel. When viewing the installed updates, copy and paste KB3177467 into the search box. If the search result shows “Security Update for Microsoft Windows (KB3177467)”, then you installed v2 since a v1 installation will not include the word “Security”.
Therefore, it is also unclear whether it is safe/necessary to install KB3172605 after KB3177467 – V2 only.
Not necessary, since the actual servicing stack files, which Windows Update uses, are identical in v1 and in v2.
I did notice that the MS support article for KB3172605 indicates that the support article was updated on August 22, 2018 even though KB3172605 was introduced in July 2016 – 2 months before the 2016 initial release of KB3177467 – V1. Perhaps this indicates that KB3172605 was also reclassified as a security update in August 2018 with no other changes to the update.
KB3172605 did not get reclassified as a Security Update. Instead this update was simply re-released on or about 2016-09-12.
I am assuming that there is no resolution yet as to whether KB3177467 – V2 is required if V1 is installed. I am also assuming that it is not resolved yet whether it is safe to install KB3177467 – V2 “on top of” V1 since KB3177467 – V1 is a permanent update that cannot be uninstalled.
Both v1 and v2 are permanent SSU updates which can not be uninstalled. As mentioned, the actual servicing stack files in v2 are identical to v1. Yet the key thing which changed with v2 is that the word “Security” was added to the beginning of the installed name for KB3177467. It appears that going forward, Windows Update will check whether the installed name for KB3177467 is “Security Update for Microsoft Windows (KB3177467)”. If the word “Security” is missing from the name, then Windows Update might not present new updates until v2 of KB3177467 is installed.
-
Why would anyone hide a servicing stack critical update?
1) KB3177467-v2 is for all, whether you have KB3177467-v1 or not
it’s just a security important update, install it and move on
2) KB3172605 fixes the slow WU scan permanently (at the time it was released)
however, currenlty latest Monthly Rollup or KB3138612 have the same fix
so, don’t install itSSUs are always safe, and users should not overthink about installing them or not
KB3177467-v1 can be uninstalled if KB3177467-v2 is installed, but you will need DISM tool
https://www.askwoody.com/forums/topic/cant-get-the-win7-monthly-rollup-to-install-error-0x8000fff-again-theres-a-reason-and-you-arent-gonna-like-it/#post-2238805 users thanked author for this post.
-
So as to not facilitate MS’s ability to update my machine without my approval. Each time you update the servicing stack you give away more control over your machine. There are ways to block MS reaching into your machine. Their telemetry detects that. They modify the servicing stack to do away with those blocking techniques. You lose more control over your machine.
They are security updates alright – Security for MS.
-
224870
@CanadianTech. Another plus for your zero updates strategy?
1 user thanked author for this post.
-
-
-
-
-
-
-
-
-
If KB3172605 (Win7) or KB3173424 (Win8.1) are already installed, they simply won’t re-install.
The verdict is still out on kb3177467 -v2. It may be offered through WU after all other updates are either installed or hidden from the “important” update queue.
-
-
KB3177467 v2 is completely safe to install. All of the actual servicing stack files within v2 are identical in every way to v1 from 2016 and which I installed on all of my Win7 computers in September 2016. All of the other files were simply modified to include the word “Security” as part of the installed name for the v2 version of KB3177467. I spent an hour yesterday evening comparing everything between the unpacked v1 and v2 versions of KB3177467, and I do mean absolutely everything — calculated MD5 checksums included.
-
KB3177467 v2 is completely safe to install. All of the actual servicing stack files within v2 are identical in every way to v1 from 2016 and which I installed on all of my Win7 computers in September 2016. All of the other files were simply modified to include the word “Security” as part of the installed name for the v2 version of KB3177467. I spent an hour yesterday evening comparing everything between the unpacked v1 and v2 versions of KB3177467, and I do mean absolutely everything — calculated MD5 checksums included.
in other words, if 2016 version is installed already, there is no need to install v2, as they are identical…
PC: Windows 7 Ultimate, 64bit, Group B
Notebook: Windows 8.1, 64bit, Group B -
-
-
-
-
-
-
-
Win 7 Group B, 3172605 installed since Sep 2016, 3177467 since Oct 2016, and since starting some 2 months after they bundled them (would that make it just Oct 2016?) I’ve just been using WU for .NET updates and I gather that if you hide a rollup the one before it will show up instead after checking again (is that right?), I’d need to hide them all one by one and keep checking for it to even be able to see whether 3177467 v2 would show up once it’s all cleared, so yeah, I’ll echo previous posters and ask for some definitive word whether this should be downloaded from catalog and installed manually even if v1 is installed (seems to have been said clearly that 3172605 shouldn’t be, and won’t even work, if it is already installed).
— Cavalary
1 user thanked author for this post.
-
The Servicing Stack is “exclusive” and will not show up in the “important” queue in WU until all pending updates (checked and unchecked) are removed, either installed or hidden.
1 user thanked author for this post.
-
-
-
-
-
-
If you are in Group A
+ Hide the Rollup
+ Install everything else in the “important” queue (hiding the ones you don’t want)
+ Reboot
+ Search for updates – install KB3177467 (reboot if asked)
+ Unhide the Rollup and install it.
+ RebootBut mostly, WAIT for the DEFCON number to go to 3 or above and Woody’s instructions in ComputerWorld!!!!
Edit to include “important” queue.
-
+ Install everything else (and/or hide the ones you don’t want)
By this, I believe @PKCano means to install and/or hide the updates listed on the “Important” page/tab of Windows Update. After all, the vast majority of us don’t install updates listed on the “Optional” page, such as Preview rollups.
+ Unhide the Rollup and install it.
I have already installed the latest version, V2, of 3177467. I had already installed its predecessor on January 4th of 2017. After installing V2, I wasn’t immediately presented with October’s rollup but, instead, with the September Preview rollup which was listed in the “Optional” page (tab, if you will) of Windows Update. Upon hiding that, and rechecking for updates, I was then presented with the October rollup, unchecked. I have not installed it, nor will I until AFTER we get the go-ahead later this month, provided we get it in the first place! After all, with MS’s latest shenanigans, you never know!
-
The fact that the Rollup is unchecked is a good reason to WAIT for the DEFCON rating to change!
1 user thanked author for this post.
-
-
-
The Rollup is now an unchecked important update, so it will not install on automatic updates (Joe User). But that may not help since it will still be in the WU important queue.
We are just waiting to see if MS straightens things out. They could bundle it with the Rollup, (even it’s a separate update), and set it to install first like they do in Win10.
But that’s logical, and we are talking about Microsoft….
1 user thanked author for this post.
-
-
-
As far as I can tell, you can leave that update hidden.
1 user thanked author for this post.
-
-
-
@PKCano: I am understanding that No updates at all for the month of October are to be touched. Is this correct? I think it is, and wouldn’t think of attempting to DL & install anything from October (plus whatever else is hiding out there just waiting for one of us to make a mistake). Thank you, as always for reminding us all to be “super vigilant”.
-
I am understanding that No updates at all for the month of October are to be touched. Is this correct?
Not yet. We are still on DEFCON-1. Wait till Woody gives the go-ahead with DEFCON-3 or more.
1 user thanked author for this post.
-
-
-
-
The get-hotfix command reports the following on my Windows 7 Pro x64 computer:
Source Description HotFixID InstalledBy InstalledOn ------ ----------- -------- ----------- ----------- <USER>-PC Update KB3172605 NT AUTHORITY\SYSTEM 9/17/2016 ... <USER>-PC Update KB3177467 NT AUTHORITY\SYSTEM 10/17/2016...
I hid the MRT for Oct 2018 (KB890830) in Windows Update, re-checked for updates, and now the 2018-10 version of KB3177467 appears as an important checked update in Windows Update.
GoneToPlaid wrote above that the 2018-10 version of KB3177467 is safe to install. Do the AskWoody MVPs concur?
-
The AskWoody MVPs say “We are still at DEFCON-1” which means WAIT. Things are still not settled. Woody will give instructions along with the go-ahead at DEFCON-3 (or more). Why are you in such a hurry?
If (as reported) the files that make up the “new” KB3177467 are exactly the same as the version I already have installed, I figured I could install it and have things ready for when Woody does change the DEFCON level.
-
-
-
The DEFCON number applies to ALL the October updates.
OK. Based on some of the later replies, this KB3177467 situation is more complicated than I thought. I will do as you recommend and wait for further instructions.
-
-
-
-
-
-
For the first time in Sept, KB3177467 became a prereq for the Rollup. It was throwing 0x8000FFF for those who did not have it installed (probably hid it) – big hoorah. (See this thread).
Also, many people hid it and KB3172605 as well
1 user thanked author for this post.
-
-
-
I am going to say this for the final time. KB3177467 v2 is completely safe to install, and should be installed by all Win7 users in order to make sure that all future Windows Updates do properly get displayed as available updates. KB3177467 v2 does NOT install any new or changed servicing stack files which are used by Windows Update! Yet KB3177467 v2 DOES change the name of this installed SSU to include the word “Security” in front of the word “Update”, when you view the list of installed updates on your computer. And KB3177467 v2 DOES change the file version numbers of the installation files, even though and in fact, and as just mentioned, the actual installed servicing stack files are identical to what the v1 of this update installed in September of 2016!!!
PKCano — I love you man since your wisdom most frequently hits the nail right on the head. Yet I think that you have jumped a little bit overboard in terms of this KB3177467 v2 update which is now going to be a requirement for all Win7 users, going forward.
With all of the above said, all other updates are so totally on hold since we correctly are at Defcon 1. I so totally agree with Woody’s assessment of the lay of the land for all Windows Updates, aside from Win7 users going ahead and installing KB3177467 v2 which now and now matter what, will be a requirement for receiving all future Windows Updates. I was going to test the past two months of Win7 Security Only updates this weekend, yet I decided to hold off. And I am not touching the latest .NET rollup since we presently have a forum member who is dealing with IE issues, and who all but swears that his IE issues only showed up after installing the latest OS and .NET Rollups.
I wholeheartedly recommend NOT installing any OS Rollup and .NET Rollup at the same time. Why? Because if you do so, it becomes much harder to figure out if one or the other actually is the cause of any update issues.
-
-
My suggestion with KB3172605 is this:
When the time comes to update (DEFCON-3 or above), unhide it, then search for updates.
If your system DOES NOT require it, it will NOT show up in the WU “important” queue.
If your system DOES require it, it will show up as a CHECKED important update and can be installed. -
-
KB3172605 has nothing to do with KB3177467 v2. It is mentioned in this thread because the quote in the original post mentioned its install order (which is still valid if you install it) and people assumed it had something to do with the SSU.
Now, I have to ask you why you have a two year old update still hidden? Unhide it. It either disappears because it is not needed, or if it is checked important and needed it is installed. WU knows best, and either way you have one less update hidden!
-
-
-
-
KB3172605, when it was originally released, was avoided by many since it was quickly discovered that it broke Intel Bluetooth drivers. I hid it at the time and forgot about it. Later, it turned out that it apparently broke the Bluetooth drivers only on Lenovo computers which had some sort of related scheduled task which would run. Lenovo’s recommended solution was to uninstall their Bluetooth drivers, install KB3177467 and KB3172605, and then reinstall their Bluetooth drivers.
It is kind of a good thing that KB3172605 was mentioned along with KB3177467 in the old installation notes since a lot of people hid KB3177467 back in 2016. KB3172605 does contain two somewhat important security fixes. If you don’t have KB3172605 installed, I do recommend installing it, but only if you already have either version of KB3177467 installed.
1 user thanked author for this post.
-
-
PKCano — I love you man since your wisdom most frequently hits the nail right on the head. Yet I think that you have jumped a little bit overboard in terms of this KB3177467 v2 update which is now going to be a requirement for all Win7 users, going forward.
I don’t see any problem waiting to install KB 3177467 v2 until the DEFCON number is 3 or above. I have offered instructions for both Group A and Group B as to how to get the SSU first (now or later, it is the same).
My recommendation to wait (beside the DEFCON status) is in the hope that MS will come up with a way for Windows Update to automatically handle the sequence of installation so that the SSU precedes the Rollup without all the finagling (like it does in Win10). Perhaps that is one reason why the Rollup is now unchecked and/or not offered.
If that doesn’t happen, heaven help Joe User whose WU is on automatic and who has no clue what’s going on!
-
PKCano is absolutely right: help on this website should be clear, simple and useful to any Joe User out there. Rush is often a bad adviser.
More experienced users who are minimally able to figure out what’s going may, of course, provide further help or feedback: IMHO (and GoneToPlaid and others) it’s okay to go ahead and install KB3177467 (and probably KB890830, too) but readers should (please) keep in mind I’m not a MVP (just another dude here trying to help others) and (quoting PKCano’s wise words) MVPs say “We are still at DEFCON-1” which means WAIT.
3 users thanked author for this post.
-
-
-
-
-
If you install through Windows Update, the system will handle the installation order, so you don’t have to worry about it. Microsoft is still working on the patches, so WAIT until the DEFCON number is 3 or above.
There is no rush to install yet, and more information may be available with time.
2 users thanked author for this post.
-
-
-
KB2952664, the MS telemetry patch, used to be a standalone update. As of the October Rollup, the telemetry patch has been included as part of the update. So, installing 2018-10 Rollup also in effect installs KB2952664.
KB3150513 is related to KB2952664 and telemetry. It will only show up in the Windows Update important queue if the latter is installed. My recommendation is to hide KB3150513. But there is now no way to uninstall KB2952664 as it is part of the Rollup.
Edit: to correct KB number 3150515 -> 3150513
-
-
-
-
Remember that old saying: Good things come to those who wait!
We are at MS-DEFCON 1, it’s best not to install any October Patches and the v1/ v2 SSU confusion will be clearer once we hit MS-DEFCON 3 or more. The patches aren’t going to disappearWindows - commercial by definition and now function...
-
-
-
Unhide KB3138612. Check for updates.
If it is NOT required by the system, it will simply not show up.
If it IS required, and is checked in the “important” updates, let it install.Windows Update knows more than you do. It will do the right thing and not overwrite something that is newer.
-
-
No really, KB3138612 is completely superseded by KB3172605 or Monthly Rollups
but due the mess in Win7’s WU between metadata supersedence, CBS supersedence, most updates prior April 2016 being dual-branches (GDR/LDR), updates post April 2016 are all LDR.. due all that they cannot supersede important update easilyWindows 8.1 equivalent KB3138615 was superseded
-
-
-
-
My head’s about to explode: hide this, unhide that, install Y before X but only if conditions 2b or 5.c(3) apply to your PC during a full moon, etc. etc. etc.
I know that this is a developing situation, so instead of doing anything I am waiting for MS-Defcon 3. However…
…When that time comes, is it too optimistic to hope that Topic 2000003 will provide clear and specific instructions regarding these various SSU’s for Group B? This is the go-to page for Group B patching, and I’m hoping that it (and not some other random page) will include all the steps that are needed, and in the correct order, for all of the patches that have come out since September’s Patch Tuesday.
1 user thanked author for this post.
-
AKB200003 is about telemetry. The .NET Security-only patches don’t belong there nor do the SSUs. At this point we know the SSU needs to be installed first before the update (either Rollup or SO). But I believe that however MS is going to handle this situation so it doesn’t create problems/errors for everyone (Joe User especially) is still up in the air.
Please be patient.
-
Cybertooth, I agree with you that the SO updates do need to be added to that site. I have asked this in the past but it won’t happen.
My friends and I have our own list of SO updates for Group B. We discuss among ourselves and eventually post the update method for Group B that we used and had success or mention any issues we encountered here at Woody’s.
Others here, I think Elly does the same and that is very helpful to others.
3 users thanked author for this post.
-
@anonymous 224842, what I’m thinking is that it would be mighty helpful to have ALL of the instructions for ALL of the updates located in ONE consistent place month after month, rather than having to look for this bunch of patches “here” and that bunch “over there”. It’s becoming an unwieldy process, trying to keep track of where the instructions are for each subset of patches. It would simplify things considerably if they were all posted to the same topic every month that we could keep in a single bookmark.
Microsoft has made such a mess of things that even Group A “do whatever you want to me” patching is no picnic any more. We are (or, at least, I am) approaching the limits of comprehensibility and practicality.
1 user thanked author for this post.
-
Cybertooth again I agree with you. In the past getting a windows update was easy. Today with all the problems and half tested updates, it is a pain. I feel sorry for the Windows 10 user that has the updates on and can not turn it off. I would suggest getting windows 10 PRO or Enterprise. The poor HOME users have the least of any options.
My friends and I are all getting tired of this worry of what to do for our windows 7 Group B machines. I finally told one friend that “I didn’t care what was being said, I was waiting for Woody, then I would start to look at what to do”. I tell them to wait for Woody to change the defcon and read what he says.
It would be nice to have a single place that has all the Group B updates to load for that month. I would think that if Microsoft has a Security Only patch available that all those Security Only patches for that month could be listed.
I do remember Group A people saying how easy it was, and now they are wailing too.
No I will not go to Windows 10 and Canadian Tech’s approach of not installing patches but do have backups may pan out in the future. Especially when EOL happens to Windows 7.
3 users thanked author for this post.
-
@cybertooth and various @anonymous – It’s really the nature of the beast that makes having a single “tell-all” link difficult to come to fruition.
However, in some sense there’s not really that much to keep track of at least for a single operating system.
For what it’s worth, here’s what I do. Every patch Tuesday Woody posts a summary of the updates that have been issued. For example here’s October’s: https://www.askwoody.com/forums/topic/the-most-recent-servicing-stack-updates/#post-224941. There are several useful links that Woody usually includes such as the MS master list, the Catalog list and Martin Brinkman’s summary. I go through these various links and cull out the updates I need for my Win 7 system. I end up with a list for IE11, Rollups and Security Only patches for Win 7 and .NET, Office 2010, etc. Of course you seem to be aware of PKCano’s Group B list, and Susan Bradley posts the Master Patch List. (I haven’t intentionally left anyone’s list out; if I have, no offense intended.)
It seems to always take a few weeks for things to shake out. There are always bad patches, workarounds, temporary solutions, etc. It’s up to me to decide how much attention to pay to all the posts here. Sometimes I read every post relevant to my machines, and sometimes I get so disgusted I blow it off until Woody posts a Defcon3 or higher. Regardless of what I’m in the mood for, though, by the time Defcon 3 comes around Woody will have pretty specific instructions for ALL the updates in a Computerworld article, which article will usually contain links back to AskWoody about various special or out of the ordinary situations or simply if you wan/need more info. Fairly often, by the time Defcon 3 comes around, MS will have gotten it’s act together so that no special instructions are needed; some times, of course, MS doesn’t get it’s act together and such is life with Windows.
The whole thing is often frustrating, seems to take forever, is a black hole for time and mental energy, etc. But, for Windows, it’s just the way it is. Seemingly the only way out is to change to a non-Windows operating system.
While I’m at it, I’d like to put in a plug for the MVPs. They do a fantastic job of sorting through all the confetti, seem to be almost infinitely patient with folks like me who don’t have their techie chops, and do it all for zero remuneration.
-
DrBonzo, thank you. I read your posts and like them.
What you said is the exact way I and others here feel about windows updates.
Yes, we currently do look at Woody’s articles and references. We do get frustrated with the “black hole” of data. We do throw our hands up and stop, then wait for Woody to change the defcon number and give his suggestions.This is why I have asked and agree with cybertooth that a single website of the suggested installs for all SOs for Group B should be available. Even if that site is updated a day before the next patch Tuesday. Of all the very competent MVPs here it seems possible.
As it stands now, we that are tech savvy can look at the Microsoft Catalog, find the Security Only updates offered for that month, and after Woody says proceed, we do.
I and my friends have been doing this examination and selective installs for years, and more so since the new method of CU and SO updates appeared way back in October 2016.
Thanks to all.
1 user thanked author for this post.
-
-
-
-
The SSUs are available through Windows Update. The SOs and IE11 CUs listed in AKB2000003 are not available through Windows Update. That’s why the latter (related to telemetry) are there. If you can get the patch through Windows Update, you don’t need a special link (beside the fact the SSUs are not related to telemetry).
-
-
-
-
KB317746 v6 was released 10/10/2018. You have v1 it would appear if you installed 10/1/2018.
1 user thanked author for this post.
-
-
-
-
-
I think you meant KB3150513, as this is the additional telemetry update which can only install if KB2952664 is installed. Obviously if KB3150513 is presented in Windows Update, then this is a red flag that KB2952664 (or multiple versions thereof) are installed on the user’s computer.
In my case Win 7 is offering KB3150513 but KB2952664 is definitely not on my system. Make that ‘was’ offering. while group A, I hide compatibility or telemetry updates.
Group A (but Telemetry disabled Tasks and Registry)
1) Dell Inspiron with Win 11 64 Home permanently in dock due to "sorry spares no longer made".
2) Dell Inspiron with Win 11 64 Home (substantial discount with Pro version available only at full price)1 user thanked author for this post.
-
KB2952664 (or its functionality) has been incorporated into the Rollups, beginning with with the 2018-09 Preview Rollup and continuing with KB4462923 2018-10 Monthly Rollup. If you have installed either of those updates, you will see KB3150513 in the important update queue because you have essentially installed KB2952664 (although it is no longer listed as a separate update).
1 user thanked author for this post.
-
KB2952664 (or its functionality) has been incorporated into the Rollups, beginning with with the 2018-09 Preview Rollup and continuing with KB4462923 2018-10 Monthly Rollup. If you have installed either of those updates, you will see KB3150513 in the important update queue because you have essentially installed KB2952664 (although it is no longer listed as a separate update).
In plain English, the upshot is that Microsoft appears to be doubling down on installing telemetry on all Win7 computers. What the heck? Can Microsoft still not figure out why so many Win7 users refuse to upgrade to Win10? Can Microsoft not figure out why so many Win7 users do not wish to have everything which they do on their computers, computers which are these users’ personal property, being tracked by Microsoft?
KB3150513 dates back to 2016-05-04 or thereabouts. The upshot is that KB3150513 installs additional telemetry on top of the telemetry which is installed by KB2952664. The additional riot is that the original MS description for KB3150513 is that it is the “Latest compatibility definition update for Windows”. Do any of you see any mention in this update description that it installs telemetry? Were any of you, when installing KB3150513, presented with a EULA which mentioned that this update would install telemetry? Of course not, since Microsoft’s lawyers have decided that if you choose to install any Windows Update, then you have inherently chosen to do so — regardless of any Microsoft obligation to present any kind of legal stuff. This is the legal loophole in action.
KB3150513 can only be installed if KB2952664 is installed, whether or not KB2952664 is listed as an installed update! This is the big change which PKCano has been trying to tell all of us — that KB2952664, as of the October Rollup, is silently bundled within the October Rollup and is no longer offered as a separate update package!
PKCano, thank you from the bottom of my heart for figuring this out, as this is a game changer for all who are on Group A yet who also have avoided installing KB2952664 AKA the “Infamous Telemetry Update.” By the looks of it, this might be a game changer going forward.
And perhaps I might suggest that the October Rollup is now unchecked, and not because of any potential issues with the V2 of KB3177467. I instead suggest that perhaps Microsoft’s attorneys have realized that silently bundling KB2952664 into the October Rollup was a really bad thing and that this is potentially now a legal can of worms? I potentially suggest this line of reasoning since Microsoft must adhere to regulations and settlement agreements which are applicable not only within the US, but also in the EU and possibly elsewhere.
1 user thanked author for this post.
-
-
I think you meant KB3150513, as this is the additional telemetry update which can only install if KB2952664 is installed. Obviously if KB3150513 is presented in Windows Update, then this is a red flag that KB2952664 (or multiple versions thereof) are installed on the user’s computer.
In my case Win 7 is offering KB3150513 but KB2952664 is definitely not on my system. Make that ‘was’ offering. while group A, I hide compatibility or telemetry updates.
Let me guess. You installed the October Rollup which silently includes KB2952664, yet KB2952664 will not show up as an installed update.
1 user thanked author for this post.
-
Let me guess. You installed the October Rollup which silently includes , yet KB2952664 will not show up as an installed update.
Away from that machine for a while so the checking will have to wait. However I was rushed with my update processes this month. By now I thought they would have given up on KB2952664. It seems they finally snuck it past me!
Group A (but Telemetry disabled Tasks and Registry)
1) Dell Inspiron with Win 11 64 Home permanently in dock due to "sorry spares no longer made".
2) Dell Inspiron with Win 11 64 Home (substantial discount with Pro version available only at full price)1 user thanked author for this post.
-
-
-
@SteveTree, @PKCano, @GoneToPlaid. @AskWoody et al
Thank you all. Non-tech users like me would be nothing more than lambs led to M$ slaughter without your knowledge and willingness to share it.
That’s why I’m here and why I read AW every day.
HF
1 user thanked author for this post.
Viewing 28 reply threads
Plus Membership
Donations from Plus members keep this site going. You can identify the people who support AskWoody by the Plus badge on their avatars.
AskWoody Plus members not only get access to all of the contents of this site -- including Susan Bradley's frequently updated Patch Watch listing -- they also receive weekly AskWoody Plus Newsletters (formerly Windows Secrets Newsletter) and AskWoody Plus Alerts, emails when there are important breaking developments.
Get Plus!
Recent Topics
-
Cox Communications and Charter Communications to merge
by 4 hours, 17 minutes ago
-
Help with WD usb driver on Windows 11
by 3 hours, 24 minutes ago
-
hibernate activation
by 7 hours, 10 minutes ago
-
Red Hat Enterprise Linux 10 with AI assistant
by 10 hours, 58 minutes ago
-
Windows 11 Insider Preview build 26200.5603 released to DEV
by 14 hours, 2 minutes ago
-
Windows 11 Insider Preview build 26120.4151 (24H2) released to BETA
by 14 hours, 4 minutes ago
-
Fixing Windows 24H2 failed KB5058411 install
by 17 hours, 14 minutes ago
-
Out of band for Windows 10
by 18 hours, 47 minutes ago
-
Giving UniGetUi a test run.
by 1 day, 1 hour ago
-
Windows 11 Insider Preview Build 26100.4188 (24H2) released to Release Preview
by 1 day, 9 hours ago
-
Microsoft is now putting quantum encryption in Windows builds
by 1 day, 7 hours ago
-
Auto Time Zone Adjustment
by 1 day, 13 hours ago
-
To download Win 11 Pro 23H2 ISO.
by 1 day, 11 hours ago
-
Manage your browsing experience with Edge
by 16 hours, 6 minutes ago
-
Fewer vulnerabilities, larger updates
by 4 hours, 32 minutes ago
-
Hobbies — There’s free software for that!
by 10 hours, 56 minutes ago
-
Apps included with macOS
by 8 hours, 48 minutes ago
-
Xfinity home internet
by 5 hours, 35 minutes ago
-
Convert PowerPoint presentation to Impress
by 1 day, 6 hours ago
-
Debian 12.11 released
by 2 days, 10 hours ago
-
Microsoft: Troubleshoot problems updating Windows
by 2 days, 14 hours ago
-
Woman Files for Divorce After ChatGPT “Reads” Husband’s Coffee Cup
by 1 day, 18 hours ago
-
Moving fwd, Win 11 Pro,, which is best? Lenovo refurb
by 14 minutes ago
-
DBOS Advanced Network Analysis
by 3 days, 7 hours ago
-
Microsoft Edge Launching Automatically?
by 2 days, 22 hours ago
-
Google Chrome to block admin-level browser launches for better security
by 19 hours, 43 minutes ago
-
iPhone SE2 Stolen Device Protection
by 3 days, 2 hours ago
-
Some advice for managing my wireless internet gateway
by 2 days, 10 hours ago
-
NO POWER IN KEYBOARD OR MOUSE
by 1 day, 12 hours ago
-
A CVE-MITRE-CISA-CNA Extravaganza
by 3 days, 19 hours ago
Remembering Woody
