KB3083324 Any Info please

groze said:

UsernameIssues said:

On the other side of the coin:

There are users and companies that are intentionally allowing all Windows 7 telemetry to be gathered in the hopes of creating a better Windows product line.

Microsoft owns the operating system. They can do whatever they want with it* (within applicable laws). You are only licensed to use Microsoft's operating system.

*sure MS can upset some users. Doing so has not significantly hurt their market share - yet.

UserNameissues,
That is like changing a rule in the middle of the game. You don't do that. You buy a devices to use the operating system with the current eula, not with what the eula will be years later. Just my opinion.

I do have KB3083324 installed. No issues that I am aware of. I don't have a monitoring program to see if KB3083324 is contacting Microsoft for telemetry. Anybody know a good free monitoring programs for windows 7 to see if it contacts Microsoft when not using Microsoft services?

Take a look at the EULA that you agreed to. Specifically section 7 where you agreed to allow the KB being discussed here to be installed without notification. Also, that entire section is subject to change:

7. INTERNET-BASED SERVICES. Microsoft provides Internet-based services with the software. It may change or cancel them at any time.

· Windows Update. To enable the proper functioning of the Windows Update service in the software (if you use it), updates or downloads to the Windows Update service will be required from time to time and downloaded and installed without further notice to you.

...but I'm not a lawyer

Layback Bear said:

UsernameIssues said:

Layback Bear said:

I would suggest their would be less tin foil hats if Microsoft gave complete description of all Updates.

You are correct; however, I doubt that documenting/explaining the updates creates revenue. Given the choice between spending money on better documentation and spending it on better testing before releasing it to the public, I'll pick the later every time

Looking into my crystal ball, I foresee less and less documentation on the horizon... or maybe it is just cataracts.

I see no reason M/S can't spend money on both documentation of KB's and testing.
Because of M/S new methods of doing Updates we need information. We/I can no longer trust M/S on such matters.

They can indeed do both - but my preference was to spend all of that money* on testing. A well documented bad update is still a bad update.

*the issue is moot since it seems that more documentation does not cost more: Painter

I can assure you all these updates to the Windows update agent are legit and I would recommend you all apply them to improve efficiency of the Windows update agent. Around 5-6 months ago a bug in the Windows update agent caused windows update scans to crash on 90% of machines in our enterprise environment resulting in none being able to be patched. We were not the only ones and these WUA releases are Microsoft's fix to the issue. It mostly affected 32-bit Win 7 clients running out of memory because of 32-bit limitations with memory addressing but the improvements in these updates do speed things up and improve scan efficiency for 64-bit clients as well.

Lady Fitzgerald said:

cm4coc said:

I can assure you all these updates to the Windows update agent are legit and I would recommend you all apply them to improve efficiency of the Windows update agent. Around 5-6 months ago a bug in the Windows update agent caused windows update scans to crash on 90% of machines in our enterprise environment resulting in none being able to be patched. We were not the only ones and these WUA releases are Microsoft's fix to the issue. It mostly affected 32-bit Win 7 clients running out of memory because of 32-bit limitations with memory addressing but the improvements in these updates do speed things up and improve scan efficiency for 64-bit clients as well.

And we should take your word for it why?

You can believe me or not I'm just trying to help clear up the confusion based on what I know to be the reason for these updates

cm4coc said:

Lady Fitzgerald said:

cm4coc said:

I can assure you all these updates to the Windows update agent are legit and I would recommend you all apply them to improve efficiency of the Windows update agent. Around 5-6 months ago a bug in the Windows update agent caused windows update scans to crash on 90% of machines in our enterprise environment resulting in none being able to be patched. We were not the only ones and these WUA releases are Microsoft's fix to the issue. It mostly affected 32-bit Win 7 clients running out of memory because of 32-bit limitations with memory addressing but the improvements in these updates do speed things up and improve scan efficiency for 64-bit clients as well.

And we should take your word for it why?

You can believe me or not I'm just trying to help clear up the confusion based on what I know to be the reason for these updates

If it helps, here's a link describing the original issue these updates are a result of:
Support Tip: ConfigMgr 2012 update scan fails and causes incorrect compliance status - The Official Configuration Manager Support Team Blog - Site Home - TechNet Blogs

Callender said:

groze said:

Anybody know a good free monitoring programs for windows 7 to see if it contacts Microsoft when not using Microsoft services?

Well I use ThreatCheck's ThreatStop to get a list of ip addresses that my machine has communicated with over any given period. Sometimes I leave ThreatStop running overnight just to see if my onboard security missed anything and if there are any suspicious ip addresses listed in the results.

The problem is - ThreatStop is no longer available from the manufacturer.

I'd also be interested to know of any similar software that's currently available - something you can leave running in the background that produces a log of all ip addresses communicated with.

TcpLogView - Creates TCP connections log

There are also huge perception and trust issues going on. With all that has been happening many people I know have just switched off updates completely. The point is that what MS says is happening isn't always the truth. Look at all the systems that have downloaded 6GB of windows 10 and have attempted to install it even when the user hasn't even reserved a copy. I've had this on the majority of my win7 systems before I removed the relevant KB's, and friends and colleagues have had exactly the same. The fact that this update has now switched from optional to important also muddys the water.
The rush to release these telemetry updates is proving to be a nightmare now to have to check what each KB is doing and wait for feedback from others on the web. This can only do harm to MS reputation.

@ThrashZone I believe it was KB3022345 that was the original update that screwed the system file checker so that was one that needed removal.

I like many others hadn't intentionally joined CEIP but found my task scheduler full of these tasks without my knowledge (now deleted).