You can of course install the big rollup, and then run Win Updates normally to catch anything further. So, the upside to it all is, it makes doing a clean install and updating it much easier, but the downside is, you can't be too sure of what they're putting into the monthly rollup updates going forward, unless they list them of course. Those are the only 3 I know of that some folks seem to object to. CEIP is OFF by default here in my Win 7, and I don't really think it's an issue. The 3 "telemetry" related updates are apparently just CEIP file updates, so I ignored them. There are 123 updates in the big rollup I believe. Perhaps someone else knows of some way to do it. So there isn't any way to uninstall individual ones from that vantage point. When I installed the big rollup update, it just shows up in the update history as 1 update, no detail. You'll have to Google/search a bit and see I guess, I'm just not sure. So, thank you very much, once more, for pointing out that telemetry content.Ĭlick to expand.To be honest, I'm not sure if there is any way to de-select any of the individual updates. Another one about which opinions may differ.Īnyhow, if one (like me) considers those updates as important, it is important to be aware of the telemetry content. It is not truly essential, but I still think it is rather important. a fix for an issue introduced by KB3068708!), but you are right, it is essentially a telemetry update, with some fixes wrapped inside it. Regarding KB3080149, I consider it as rather essential because of the fix for System File Checker tool (N.B. Therefore, for Windows 7, I think KB3068708 is a security update wrapped in a telemetry update.īecause of the security update content for Windows 7, I consider KB3068708 as probably an essential security update, despite the telemetry content. "The Windows 7 offering also supports the kernel updates that were deployed separately to Windows 8.1 through security update 3045999." Yes, it's a telemetry update, but the knowledge base article also mentions: Regarding KB3068708, that's a really pesky one.
0 kommentar(er)
