How to stop
Has anyone found a reliable way to STOP the WIndows 10 FEATURE updates?? I have several clients that once the Creators update installs their business software no longer works. I have tried stopping the update service, setting a metered connection. They are on Build 1511 which is the one that works, anything higher than that and they have issues.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you have Windows 10 Home, I am not aware how to do it.
You need to be at V1607 at least and even it is getting old.
You can set updates to the Semi Annual which means the updates are in widespread use.
You need to have your clients update their software because the Windows 10 update wheel never stops ever again. No rest.
Update the software and keep Windows 10 up to date.
You can set updates to the Semi Annual which means the updates are in widespread use.
You need to have your clients update their software because the Windows 10 update wheel never stops ever again. No rest.
Update the software and keep Windows 10 up to date.
I'm right there with you v1709 always creates a problem for me. I have several in my network and it's getting worse!
V1607 is good, V1703 had lots of bugs, and V1709 fixed most of these.
So get to 1607 and set updates for widespread use and then update the software on the computer.
So get to 1607 and set updates for widespread use and then update the software on the computer.
Hi,
Please check these articles.
1- https://www.forbes.com/sites/gordonkelly/2015/08/26/windows-10-how-to-stop-forced-updates/#3c0f53d446f6
2- https://4sysops.com/archives/disable-windows-10-update-in-the-registry-and-with-powershell/
Haven't tried personally though
BR,
Please check these articles.
1- https://www.forbes.com/sites/gordonkelly/2015/08/26/windows-10-how-to-stop-forced-updates/#3c0f53d446f6
2- https://4sysops.com/archives/disable-windows-10-update-in-the-registry-and-with-powershell/
Haven't tried personally though
BR,
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.
I have recommended this question be closed as follows:
Accept: Joe Fulginiti (https:#a42462367)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
I have recommended this question be closed as follows:
Accept: Joe Fulginiti (https:#a42462367)
If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.
seth2740
Experts-Exchange Cleanup Volunteer
You have three options:
1) keep their business software up to date so it stays compatible with windows, 98% of the time, compatibility issues with newer windows feature updates is because the program is out of date. No, running quickbooks 2001 on windows 10 is not exceptable (for example.) Investing in a version of quickbooks less than 5 years old is not an extreme position.
2) In rare instances where the vendor is out of business or really does fail to offer uodate software, time to switch to a different application. Yes, IBM quit making Lotus 123. Time to invest in Excel.
3) In cases where 1 and 2 are absolutely not possible, that's what the windows LTSB offering is for. It's been available for volume licensing since windows 10 first shipped and is intentionally geared for those oddball edge cases. It is locked, stable code, with long term support without feature updates. It has its pros and cons so should be evaluated to see if it meets the user's needs.