none
Unacceptable policy to force users to upgrade Windows 10

    Question

  • This is not really a question, but a message to Microsoft. IT'S UNACCEPTABLE TO FORCE USERS TO UPGRADE WINDOWS 10 TO THE NEXT "GREAT" RELEASE. MICROSOFT, DID YOU GET IT? IT'S UNACCEPTABLE!!!

    It's bad enough that minor updates can be installed without user's permission (which can break things), but installing a major update without the user's permission is completely unacceptable. The minor updates can break things, but major upgrades are guaranteed to leave some scorched earth.

    For example, the 2018-01 cumulative update affected Symantec Endpoint Protection AV software that I'm using. After that update was installed on several machines the SEP icon has an exclamation mark on it and a message pop up indicates multiple issues. When SEP window is opened it says everything is OK. At least it's not seriously affected, but nevertheless the update caused some "damage". This is nothing compared to what the major upgrade can do though.

    For me version 1607 was the most compatible, followed by 1709 and then 1703 that wasn't that great. Unfortunately Microsoft is trying to force me to upgrade my 1607 machines and was even successful on one of them. I have a Thinkpad laptop that I access remotely. It's far away from me and actually in a different country. It's my way to go around the regional access restrictions that some sites impose. Anyway, I don't access it very often and a couple of weeks ago I've found it upgraded to the latest Windows 10 release. That happened completely without my permission. That's unacceptable! Luckily version 1709 has fixed what 1703 broke, so there was no negative impact. Still, this should have never happened without my explicit permission. It's my hardware and I decide what I want to run on it.

    Another example where upgrade from 1607 to 1709 broke things was on another remote machine. That one is actually closer and I visit that location several times a year. Last time I was there I actually upgraded that machine "manually" to version 1709, but upon discovering that it broke VirtualBox I had to go back to version 1607. I have to run VirtualBox version 4.3.30 (the last of 4.3.x) as the rewrite of some components they did in version 5.0 broke one of my VMs. There are actually 2 problems still present in the latest 5.2.x version which are not present in 4.3.30. After upgrading Windows to version 1709 VirtualBox 4.3.30 wouldn't even start. Instead, there was a popup pointing to log file VBoxHardening.log. So that machine is running version 1607 but Microsoft is trying very hard to push the upgrade to the latest version. I've blocked the upgrade in "Show or hide updates" diagcab, but now Windows 10 Upgrade Assistant seems to be trying hard to force the upgrade. I had to block this app in the SEP firewall, so for now that machine is safe, but for how long?

    Again, IT'S ABSOLUTELY UNACCEPTABLE TO FORCE USERS TO UPGRADE WINDOWS 10 WITHOUT THE USER'S EXPLICIT PERMISSION!!! THE OWNER OF THE HARDWARE IS THE ULTIMATE AUTHORITY ON WHAT VERSION HE WANTS TO RUN. GOT IT MICROSOFT?

    Thursday, February 8, 2018 6:05 AM

All replies

  • Each Windows 10 build comes with new features and bug fixes. You will need to have the latest build to protect yourself against new threats and use new features and bug fixes. You could try the latest build and if you see any error , then you may report it through Feedback Hub and revert back to previous version and you may postpone upgrade for a while.

    Issues you are referring should be fixed and not just ignore upgrade and you will also see version of programs which only run on the latest build.

     
    Saturday, February 10, 2018 3:50 PM
  • This is not really a question, but a message to Microsoft. IT'S UNACCEPTABLE TO FORCE USERS TO UPGRADE WINDOWS 10 TO THE NEXT "GREAT" RELEASE. MICROSOFT, DID YOU GET IT? IT'S UNACCEPTABLE!!!

    It's bad enough that minor updates can be installed without user's permission (which can break things), but installing a major update without the user's permission is completely unacceptable. The minor updates can break things, but major upgrades are guaranteed to leave some scorched earth.

    For example, the 2018-01 cumulative update affected Symantec Endpoint Protection AV software that I'm using. After that update was installed on several machines the SEP icon has an exclamation mark on it and a message pop up indicates multiple issues. When SEP window is opened it says everything is OK. At least it's not seriously affected, but nevertheless the update caused some "damage". This is nothing compared to what the major upgrade can do though.

    For me version 1607 was the most compatible, followed by 1709 and then 1703 that wasn't that great. Unfortunately Microsoft is trying to force me to upgrade my 1607 machines and was even successful on one of them. I have a Thinkpad laptop that I access remotely. It's far away from me and actually in a different country. It's my way to go around the regional access restrictions that some sites impose. Anyway, I don't access it very often and a couple of weeks ago I've found it upgraded to the latest Windows 10 release. That happened completely without my permission. That's unacceptable! Luckily version 1709 has fixed what 1703 broke, so there was no negative impact. Still, this should have never happened without my explicit permission. It's my hardware and I decide what I want to run on it.

    Another example where upgrade from 1607 to 1709 broke things was on another remote machine. That one is actually closer and I visit that location several times a year. Last time I was there I actually upgraded that machine "manually" to version 1709, but upon discovering that it broke VirtualBox I had to go back to version 1607. I have to run VirtualBox version 4.3.30 (the last of 4.3.x) as the rewrite of some components they did in version 5.0 broke one of my VMs. There are actually 2 problems still present in the latest 5.2.x version which are not present in 4.3.30. After upgrading Windows to version 1709 VirtualBox 4.3.30 wouldn't even start. Instead, there was a popup pointing to log file VBoxHardening.log. So that machine is running version 1607 but Microsoft is trying very hard to push the upgrade to the latest version. I've blocked the upgrade in "Show or hide updates" diagcab, but now Windows 10 Upgrade Assistant seems to be trying hard to force the upgrade. I had to block this app in the SEP firewall, so for now that machine is safe, but for how long?

    Again, IT'S ABSOLUTELY UNACCEPTABLE TO FORCE USERS TO UPGRADE WINDOWS 10 WITHOUT THE USER'S EXPLICIT PERMISSION!!! THE OWNER OF THE HARDWARE IS THE ULTIMATE AUTHORITY ON WHAT VERSION HE WANTS TO RUN. GOT IT MICROSOFT?

    Thank you for you voice on this subject. I run several custom made PC's that I personally built and I have all drivers and programs up to date with the exception of Windows 10. Build 1607 has proven to be the most stable version so far. I have tried updating to Build 1703/1709 numerous times only to have the PC crash less than 5 mins after starting. The update rendered my PC so nothing more than paperweights. After getting the computers back to build 1607, I was then assaulted with Windows interrupting my computer time every 10 mins asking to install the update and stopping all other programs in the process, once again making it almost impossible to use the computer.  I then also used diagcab to hide the update. I started installing a minor update labeled for build 1607 and walked to start preparing dinner. When I return I found Windows once again trying to install the most current build. After reading your post, I have now configured my firewall to block all Windows update processes from access the internet. 

    Microsoft, you need to stop shoving updates down our throats that we do not want. We are not here to beta test your software with our computers. If and when the current build stops crashing my computers, I will consider updating. You need to stop treating all of us like we are idiots about computers and software.

    Friday, March 9, 2018 3:40 AM