Problems and Solutions for KB3035583
KB3035583 just showed up AGAIN on a plethora of my client's systems a few days ago after I had already removed it, unchecked it and hid it weeks earlier.
And doing this is the most outrageous and evil thing Microsoft has done in its history, namely re-releasing KB3035583 after I've had dozens of clients pay me to remove it and their other spyware (telemetry) updates.
Furthermore, it appears that the update option, "check for updates but let me choose whether to download and install them", has somehow been ignored with one of these re-released updates as I've found systems magically reset to "Install Updates Automatically", even on systems where the users don't even know how to access an administrator account.
Two days ago I found KB3035583 installed AGAIN on several systems I support and had to uninstall it AGAIN. I then had Update find it again, unchecked it and hid it, and lo and behold, the Windows 10 installer itself was STILL pending as the only available update! Looking at "view other updates", I found the Windows 10 installer itself included, and then unchecked and hid it, and that actually BROKE Microsoft updates! After I did the above, update would immediately fail with an error (I think 0x80240019: "WU_E_EXCLUSIVE_INSTALL_CONFLICT An exclusive update cannot be installed with other updates at the same time").
This happened on ALL the systems at one business I support!
Fortunately I had encountered this problem before when I had had to roll back to W8.1 from W10 for a client who was tricked into installing W10, so I knew what to do, namely apply the following .reg hack (it will solve the problem on both W10 and W8):
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade]
"AllowOSUpgrade"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\OSUpgrade\State]
"OSUpgradeState"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DisableOSUpgrade"=dword:00000001
[Note: copy the above in a file with .reg type, and execute the reg file by right-clicking and selecting "Merge".]
This reg hack can be applied at any time when removing, unchecking and hiding KB3035583 and the Windows 10 installer update itself, but the simplest way to use the reg hack is to first uninstall KB3035583, and then apply the above reg hack BEFORE rebooting, namely first use:
wusa /uninstall /kb:3035583 /norestart /quiet
wusa /uninstall /kb:2952664 /norestart /quiet
then apply the .reg reghack, and then reboot. I've found that if the reg hack is applied that way, the Windows 10 update installer itself will not come back, though you still have to recheck for updates after the boot, to find KB3035583 AGAIN and then uncheck and hide it.
Note KB2952664 comes back too, and if you want to make sure you've removed ALL the telemetry put the following in a .bat file:
@echo on
wusa /uninstall /kb:3035583 /norestart /quiet
wusa /uninstall /kb:3022345 /norestart /quiet
wusa /uninstall /kb:3068708 /norestart /quiet
wusa /uninstall /kb:3075249 /norestart /quiet
wusa /uninstall /kb:3080149 /norestart /quiet
wusa /uninstall /kb:2990214 /norestart /quiet
wusa /uninstall /kb:3012973 /norestart /quiet
wusa /uninstall /kb:2952664 /norestart /quiet
wusa /uninstall /kb:2976978 /norestart /quiet
pause
and run the above batch file, THEN do the .reg hack, and then reboot, and as I said before, you will then have to have update check for new updates, find KB3035583 and KB2952664 and uncheck and hide them.
At this point in the game, because of what Microsoft is doing to my clients with their outrageous, repeated attempts to force W10 onto my client's computers and thereby completely wreck their businesses if they succeed, my only choice is to turn automatic updates off altogether with "Never check for updates" and manually check once or twice a year and see if there's anything worth allowing to install.