SFC cannot fix corrupted files in Windows 7 -- Windows Update for May 2015?

This morning, June 1, the Windows 10 nag began.  I can confirm that if you remove and hide KB3022345, KB3035583, and KB2952664, the nag goes away.

I am telling my Windows 7 (that's nearly all of them) clients that if they allow Windows 10 to be installed, they can no longer expect me to support them.  I told them that after a lot of investigation and examination, I may recommend it.  I have provided detailed instructions on how to eliminate the nag so they can not fall into this accidentally.

There is no reason that I know of to rush into this.  The "Free" is good for a year.  Windows 7 is a clear gold standard that will be supported until early 2020 -- that's a long time away. Unless I conclude Windows 10 has an awful lot of superiority, I will not recommend it. 

One of my concerns is what Microsoft means when it says it will be free during the time the system is supported.  What does that mean?

Another is whether the upgrade process actually works.  Years and years of experience scream at me that only a clean install is a reliable way to do this.

Then there are the mysterious -- some applications may disappear on upgrade???  Really!  Who thinks this is OK!

The vast majority of users have never upgraded an operating system and have ever paid for an upgrade.  They virtually all get a new OS when they buy a new PC.  So, in effect, they never paid for an OS.

I will recommend it to the few Windows 8 clients as it is clear Windows 10 can not be worse and probably is better. 

Some of my clients will need to buy new computers and will have Windows 10.  I will be looking very closely at these machines to gain a full understanding.  One of my big concerns is whether Windows 10 continues to hide, mis-name and just plain eliminate valuable Windows 7 tools.  For example System Image.   One really important feature of Windows 7 is the dramatic improvement in support requirements.  That came from a bevy of really good tools that are easy to find and use.  Most support people will tell you the move from XP to 7 resulted in a dramatic drop in support requirements.

Thanks Susan....any thoughts about what happened when I made the adjustment noted in my previous (May 20th) post...there did seem to be some interaction between 3022345 and 3035583.

(and for info I have checked my event-viewer logs and they are error-free.) - Ric.

https://support2.microsoft.com/default.aspx?scid=kb;en-us;3022345

KB3022345 does NOT cause file corruption.

Summary

This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

• telemetry.ASM-WindowsDefault.json
• utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.

I would be interested to see your Event Viewer System and Application logs.

I look after about 160 client Windows computers -- virtually all Windows 7 today.  I have been doing this for 13 years now.

On patch Tuesday, they get an email at about 1pm EST telling them that if they are using their computers today, they should immediately close all applications, start Windows Update, click Check for updates.  Then simply click Install. 

They are to never open either category.  Never check mark anything.  Never even open the Optional link.

Bottom line:  Only the updates categorized as "Important" get installed.  Even if there is one in the Important category and UNCHECKED, it is not installed.

I use remote control software and manage to log into each computer at least once per year.  When I do that one part of my routine is to examine these un-installed updates and install, hide or do nothing with them. 

Up until recently, Microsoft has been pretty good about this categorization.  Lately, with updates like KB3022345 and KB3035583, they have crossed the line.  These updates (and there are likely more) are not Important to their computers or the people themselves.  They are important to Microsoft in meeting its goals. 

I am currently re-thinking my policies.