-
The delay continues to next Patch Tuesday
https://blogs.technet.microsoft.com/msrc/2017/02/14/february-2017-security-update-release/
UPDATE: 2/15/17: We will deliver updates as part of the planned March Update Tuesday, March 14, 2017.
-
-
D**n
the boredom continues …1 user thanked author for this post.
-
-
Make no mistake, Windows contacts a lot of other servers online all on its own. There are more than you listed that indirectly spill the beans.
Just a few examples:
- iecvlist.microsoft.com
- ieonline.microsoft.com
- r20swj13mr.microsoft.com
- spynet2.microsoft.com
- spynetalt.microsoft.com
And many more.
There is nothing simple about Windows’ online chattiness. It’s been developed over decades. To be fair, that’s what a “cloud-integrated” system is about. But the simple fact is that some people prefer NOT to be “cloud-integrated”.
-Noel
Of course it is
but i’m not discussing all Windows phone-home contacts, the topic is specific about telemetry patchesmising thing with so-called “snooping” that precede telemetry era doesn’t help except in feeding the FUD
1 user thanked author for this post.
-
I still see the dust over the script 😀
GWX KB3035583 is ended/removed, likewise KB3123862
KB3068708/KB3075249/KB3080149 are already covered by Monthly rollup, no point of uninstalling/hiding them1 user thanked author for this post.
-
-
only extends bult-in WDI Client and adds a Performance Power Tracker
i highly doubt it sends any telemetry dataanyway, it’s related to this task:
“\Microsoft\Windows\PerfTrack\BackgroundConfigSurveyor”1 user thanked author for this post.
-
That’s not what i ment or want to discuss, the type/amount of data they send is debatable
what i mean, for Windows 7/8.1 it’s very easily to isolate or prevent these KBs effects without all those FUD-type steps
Compatibility Appraiser (aka KB2952664/KB2976978)
it only add/interact with these schedule tasks:
“\Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser”
“\Microsoft\Windows\Application Experience\ProgramDataUpdater”
“\Microsoft\Windows\Application Experience\AitAgent”Diagnostics Tracking (aka Unified Telemetry Client / Asimov)
not avoidable for Monthly Quality Rollup model, but it only adds these components:
“DiagTrack” service
“AutoLogger-Diagtrack-Listener” event trace session
“HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Diagnostics\DiagTrack” registrythe other updates (aka telemetry points) are not affective without active DiagTrack/AutoLogger
1 user thanked author for this post.
-
Very likely RS2 = Creators Update
the build lab string rs_fun_compat_dev1_apr:
rs = redstone
fun = fundamentals
compat = compatibility
dev = develpoment
apr = appraiser1 user thanked author for this post.
-
Another bad practice guide
most of these “aggressive” steps are not required in Windows 7/8.1
they belong to paranoial Windows 10, which have built-in telemetrya real “deep diver” into Appraiser/Diagtrack patches would have found a simpler walkthrough
and why a very old pre-telemetry era patch like KB971033 is related?
well, i guess the “confusion” must be fed to keep it going 🙂
-
On a related matter, they finally acknowledged this problem 🙂
-
Apparently they finally acknowledged the problem they caused for some devices
1 user thanked author for this post.
-
The first version was released on April 22, 2014
https://web.archive.org/web/20140425072337/http://support.microsoft.com/kb/29526641 user thanked author for this post.
Author
