Hey guys,
I hope you can help us with an issue with W10 and the inevitable update to 1709 they are trying to force down our throats.
We are using the W10 1703 version CB in our VDI enviornment but dont want to upgrade to version 1709. We did a few things to stop the update from happening.
We disabled the Windows Update and Windows Modules Installers service, removed all tasks related to update (which basically means everything in UpdateOrchestrator and Windows Update) but apparently Windows still wants to bypass that option. The Task Scheduler service has a self healing mechanism in which it recreates the entire tasks and starts the Windows Update service again. With writables and VDI this not really what we are aiming for..
So we went on our way to get around this virus called the Windows update and created a batch file that instantly removed the tasks and disabled the above services when an event is written that the update service is started. This seemed to work quiet well.
Now Microsoft ended up with yet another feature to shove 1709 down our throats. They designed the Update Assistent. This tool is being installed by Tasks that are created (my guess is the Task Scheduler itself does this) and it completely bypasses the Windows Update, better yet, the Windows Update service is disabled and off course the update fails. But we do have users with Windows Update Assistent installed on their machines
I saw some suggestions on the internet to just rename the installer but my guess is that I could use UEM (you see, I was getting somwhere) to just block this heavily annoying application.
Anyone else has had the same issue with updates and do you happen to know if this indeed does the trick??
If so, what do we need to set it up like exactly??