Microsoft insists, tries to force me to upgrade to 10. Based on comments here I do not want it. What can I do? It reminds me every few minutes to update. Almost did it without my permission overnight, but I declined the legal stuff. So now it takes up the whole screen every few minutes.

I need your help.

Thank you

---

There is a application called "GWX" which is very effective at getting rid of all the junk associated with the foreced Windows 10 "up/down" grade.
http://ultimateoutsider.com/downloads/

Install it, use it to get rid of the w10 install files etc. Then set it to prevent future w10 attempts and have the "monitor" running in the background to keep an eye out for any sneak attacks by the w10 spam-ware.

---

Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

And when done that, set DisableOSUpgrade = 1 in the registry as shown how to do at http://www.ghacks.net/2016/01/08/disableosupgrade-prevents-the-upgrade-to-windows-10/. That way, even with all the pre-Windows 10 updates installed, the installer will never try to install Windows 10 or bother you about it.

This is the method Microsoft tells companies is the way to stop bothering them about Win10 updates. It's very doubtful they'll change it so it'll be ignored, as MS doesn't want to be sued by them for infringement reasons.

---

From ZDNet.com
> How existing Windows users can refuse Microsoft's Windows 10 update

Also:
> Microsoft details how to block Windows 10 upgrade

From MS:
> How to manage Windows 10 notification and upgrade options

This one deals with the registry:
> How to disable the “Get Windows 10” icon shown in the notification area (tray)?

And also.. it's a little more involved, but don't forget about my handy list of updates to avoid.

You can either go through and search for the KB number in 'installed updates', or pull up an administrative command prompt and do

wusa /uninstall /kb:3035583 /norestart

..for every update that applies to your OS (7 or 8.1). Which will mean either all the blue and green updates, or all the red and green ones. There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK. I have found better luck if you go in reverse order for that list when removing them.

There are two caveats with this. 1) after removing all of them and rebooting afterward, the next check for updates will end up having a lot of them come back again. If you have your update settings set for "automatic download and install," you're just wasting your time by removing them. You should set it to "check for updates, but let me choose what to download and install" so that you have some control over which ones do and don't get installed. The ones in the avoid list.. right-click > hide update. Quite a few of them like to be re-re-re-re-re-released, so they'll keep showing back up every couple of weeks.

2) If you have 4GB or less RAM.. you'll end up with problems checking for updates because the system runs out of memory. The memory leak was fixed in 3102810/3102812, but personally, I don't trust any of the new update clients that were released after the public release of 10, simply because there have been a few instances where it has been proven that the new update clients will go behind your back and grab all the needed updates to upgrade to 10.. without your consent, nor telling you that it is doing so. I personally don't trust that update pair, but in the end, that's entirely your choice.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

And also.. it's a little more involved, but don't forget about my handy list of updates to avoid.

You can either go through and search for the KB number in 'installed updates', or pull up an administrative command prompt and do

wusa /uninstall /kb:3035583 /norestart

..for every update that applies to your OS (7 or 8.1). Which will mean either all the blue and green updates, or all the red and green ones. There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK. I have found better luck if you go in reverse order for that list when removing them.

There are two caveats with this. 1) after removing all of them and rebooting afterward, the next check for updates will end up having a lot of them come back again. If you have your update settings set for "automatic download and install," you're just wasting your time by removing them. You should set it to "check for updates, but let me choose what to download and install" so that you have some control over which ones do and don't get installed. The ones in the avoid list.. right-click > hide update. Quite a few of them like to be re-re-re-re-re-released, so they'll keep showing back up every couple of weeks.

2) If you have 4GB or less RAM.. you'll end up with problems checking for updates because the system runs out of memory. The memory leak was fixed in 3102810/3102812, but personally, I don't trust any of the new update clients that were released after the public release of 10, simply because there have been a few instances where it has been proven that the new update clients will go behind your back and grab all the needed updates to upgrade to 10.. without your consent, nor telling you that it is doing so. I personally don't trust that update pair, but in the end, that's entirely your choice.

I had a VM running Windows 7 were I enabled auto updates and just left it to see what would happen. I only just checked on it this weekend and found it to be running Windows 10. I installed the OS, activated it, set the power settings so it wouldn't sleep, made a snapshot, and enabled auto updates. Then left it to do whatever for a few months.
So unless one of my kitties figured out how to log into my VMware server the update was done with no user interaction.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Thank you every one for your suggestions.

---

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Upon further investigation, those switches (/qn, /qb) are only available with msiexec.exe, even in Windows 8.x and 10. /Quiet is the only wusa.exe switch available in 8.x and 10 as well.

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

There were several "required" updates that IE installed when I was testing to see if updating IE 9 to 11 solved an issue I was having. Turns out it didn't help. There are just some emoji characters I am just destined to never see while using Windows 7.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet. The first parameter after any Start switches is the name of the new window (if we weren't doing a quiet script). The double quotes tells it to not give the new window a name. Alternatively you can enter a name for the window that won't show up, such as start /wait "Uninstall KB2731771" wusa /uninstall /kb:2731771 /norestart /quiet.

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet. The first parameter after any Start switches is the name of the new window (if we weren't doing a quiet script). The double quotes tells it to not give the new window a name. Alternatively you can enter a name for the window that won't show up, such as start /wait "Uninstall KB2731771" wusa /uninstall /kb:2731771 /norestart /quiet.

I believe the title attribute only applies when you are opening another command prompt or application that runs in a command line/console. When running a windowed app, like wusa, the title should be set by the application. http://i.imgur.com/mGsbj2E.png

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet. The first parameter after any Start switches is the name of the new window (if we weren't doing a quiet script). The double quotes tells it to not give the new window a name. Alternatively you can enter a name for the window that won't show up, such as start /wait "Uninstall KB2731771" wusa /uninstall /kb:2731771 /norestart /quiet.

I believe the title attribute only applies when you are opening another command prompt or application that runs in a command line/console. When running a windowed app, like wusa, the title should be set by the application. http://i.imgur.com/mGsbj2E.png

You'd think so, but after much experimentation I've found that the title attribute is required, at least during scripting, therefore if you don't want to use a title, you should use the double quotes.

Try it. You'll see.

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet. The first parameter after any Start switches is the name of the new window (if we weren't doing a quiet script). The double quotes tells it to not give the new window a name. Alternatively you can enter a name for the window that won't show up, such as start /wait "Uninstall KB2731771" wusa /uninstall /kb:2731771 /norestart /quiet.

I believe the title attribute only applies when you are opening another command prompt or application that runs in a command line/console. When running a windowed app, like wusa, the title should be set by the application. http://i.imgur.com/mGsbj2E.png

You'd think so, but after much experimentation I've found that the title attribute is required, at least during scripting, therefore if you don't want to use a title, you should use the double quotes.

Try it. You'll see.

Odd I never use the title attribute in any of my scripts. Functionally title won't have any effect on applications or functions unless you have something specifically looking for a window with that title. I wouldn't mind seeing an example of where the title attribute is relevant or required when launching windows apps. However as displayed in the image I added previously it has no effect on the wusa application.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet. The first parameter after any Start switches is the name of the new window (if we weren't doing a quiet script). The double quotes tells it to not give the new window a name. Alternatively you can enter a name for the window that won't show up, such as start /wait "Uninstall KB2731771" wusa /uninstall /kb:2731771 /norestart /quiet.

I believe the title attribute only applies when you are opening another command prompt or application that runs in a command line/console. When running a windowed app, like wusa, the title should be set by the application. http://i.imgur.com/mGsbj2E.png

You'd think so, but after much experimentation I've found that the title attribute is required, at least during scripting, therefore if you don't want to use a title, you should use the double quotes.

Try it. You'll see.

Odd I never use the title attribute in any of my scripts. Functionally title won't have any effect on applications or functions unless you have something specifically looking for a window with that title. I wouldn't mind seeing an example of where the title attribute is relevant or required when launching windows apps. However as displayed in the image I added previously it has no effect on the wusa application.

Agreed, it doesn't have any affect on the window title. I never claimed the title function was relevant. I simply said if you omit it, when scripting you need to include the double quotes for start /wait to work correctly, otherwise you will see the behavior you mentioned you saw previously: it doesn't actually uninstall anything and it doesn't work in the background.

Did you try it in a batch script and did you try it with /quiet?

There's nothing wrong with just making a batch file that has ALL of the KBs on that list, since if it isn't installed, it will tell you "could not find update" and you just click OK.

If you don't want to have to click OK all the time for every update not found, you can always add /qb on your command line, which provides a "quiet/basic" UI (basic meaning just a progress bar). Or you can do /qn for "quiet/no UI" (no progress bar at all, completely silent).

Unfortunately those are not valid switches in Windows 7. There is only an option for /quiet. Which is the same as /qn in Windows 8.x.

Yes, adding /quiet does make it no interaction needed, but I have found that if you make a batch file with.. say.. 20 wusa commands with /quiet, you throw so much at the system all at once that it basically just gridlocks and does nothing. It doesn't freeze the system, just nothing happens.

You might need to add a timeout command ever few lines in that case. You could go for a more advanced script that uses something like wmic qfe list brief or wmic qfe get hotfixid to check if the update has been removed before continuing to the next.

You can also add START /WAIT "" ["command"] to make sure that each individual line is processed before the next.

I wasn't sure if that was actually waiting when I tried it on my HTPC system. As when I would run start /wait wusa /uninstall /kb:2731771 /norestart /quiet it came back nearly immediately. I thought it might be running the removal process in the background. However running the same commands on an older system showed it did wait for the updates to be removed.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet. The first parameter after any Start switches is the name of the new window (if we weren't doing a quiet script). The double quotes tells it to not give the new window a name. Alternatively you can enter a name for the window that won't show up, such as start /wait "Uninstall KB2731771" wusa /uninstall /kb:2731771 /norestart /quiet.

I believe the title attribute only applies when you are opening another command prompt or application that runs in a command line/console. When running a windowed app, like wusa, the title should be set by the application. http://i.imgur.com/mGsbj2E.png

You'd think so, but after much experimentation I've found that the title attribute is required, at least during scripting, therefore if you don't want to use a title, you should use the double quotes.

Try it. You'll see.

Odd I never use the title attribute in any of my scripts. Functionally title won't have any effect on applications or functions unless you have something specifically looking for a window with that title. I wouldn't mind seeing an example of where the title attribute is relevant or required when launching windows apps. However as displayed in the image I added previously it has no effect on the wusa application.

Agreed, it doesn't have any affect on the window title. I never claimed the title function was relevant. I simply said if you omit it, when scripting you need to include the double quotes for start /wait to work correctly, otherwise you will see the behavior you mentioned you saw previously: it doesn't actually uninstall anything and it doesn't work in the background.

Did you try it in a batch script and did you try it with /quiet?

What behavior are you referring to? The fact that one of my machines is much faster and uninstalled the updates so fast I thought the /wait command wasn't working? After I said it worked your statement was.

Your command would have to be start /wait "" wusa /uninstall /kb:2731771 /norestart /quiet.

Can you explain why my command would have to be that?

There were 6 updates I removed from the IE 11 install. Which I tossed in a .bat.
Installing IE 11 again and removing the updates works exactly the same if start /wait wusa or start /wait "" wusa is used in the .bat

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[