Block Windows 10 Upgrade Assistant

I am looking to block or stop the install of the Windows 10 Upgrade Assistant.

We are currently running Windows 10 1511 and a number of the computer have the Windows 10 Upgrade Assistant. The upgrade assistant is failing due to a conflict with our encryption software.

I have tried to set the Group Policy "Select when Feature Update are received" to Enable with the following settings. (Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Updates > Defer Windows Updates)

Select the branch readiness level for the feature updates you want to receive: Current Branch
After a feature update is release, defer receiving it for this many days: 365
Pause Feature Update starting : 2018-01-01

I have also tried to set the registry setting DisableOSUpgrade to 1 but some sources say that setting only works on Win 7.1/8.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"DisableOSUpgrade"=dword:00000001

Thank you for any help.
maemckayIS ManagerAsked:
Who is Participating?
 
maemckayConnect With a Mentor IS ManagerAuthor Commented:
Thank you for your help. The only way I found to stop the update assistant is to turn off automatic updates.

Otherwise I will be updating my encryption software and Windows to 1709.
0
 
JohnBusiness Consultant (Owner)Commented:
The registry fix only works on Windows 7 and 8, not 10.

You are on a really old version of Windows 10 - almost the first.

Why do you upgrade?  You should and that is why you are getting the hassles.
0
 
Cliff GaliherCommented:
1511 is WAY out of support.  You can't defer it anymore.  1607 is even past that 365 day release.  

If you have encryption software that isn't supported by 1607, you should look into LTSB for those needs, but that's still a manual deployment at this late stage of the game.  Regardless, you shouldn't be running 1511 in production.  Its very bad security practice to do so.  Why bother encrypting data on disk when hackers can just steal it from memory...seems like a cart-before-the-horse scenario to me.

-Cliff
1
 
JohnBusiness Consultant (Owner)Commented:
And in addition, upgrade Legacy software to something that works today (V1709).
0
 
maemckayIS ManagerAuthor Commented:
It was the only solution that worked.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.