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?

You said:

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.

I read that you weren't sure in your first sentence. I read that you tried something in your second sentence, still implying uncertainty. You mentioned a hypothesis in your third sentence, then in your fourth sentence you added a "however", which suggested to me a contrary finding to your hypothesis. [Edited to add] I see now that the "however" was supposed to be confirmation of the removal, but I still read it as only working on the older system.

I saw nothing in your statements confirming it worked or that it was because it was so fast. You only mentioned that it was successful on older systems. Obviously I misread your post. Sorry about that.

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?

You said:

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.

I read that you weren't sure in your first sentence. I read that you tried something in your second sentence, still implying uncertainty. You mentioned a hypothesis in your third sentence, then in your fourth sentence you added a "however", which suggested to me a contrary finding to your hypothesis. [Edited to add] I see now that the "however" was supposed to be confirmation of the removal, but I still read it as only working on the older system.

I saw nothing in your statements confirming it worked or that it was because it was so fast. You only mentioned that it was successful on older systems. Obviously I misread your post. Sorry about that.

Ah I see what was going on. I was rather confused. As I had thought I had explained the command was working as expected. Not that I was stating the command worked on one system and did not work on the other.

---

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

With Cosmic_Ocean list of updates to avoid I made a quick script that could be used to purge the undesired updates.

I highlighted the list, copied, pasted it into notepad, and then saved as bad_updates_list.txt in a folder where I planned to place the removal script.

Then made this simple batch file.
bad_updates_removal.bat

pushd %~dp0
FOR /F "tokens=2 delims= " %%a in ("bad_updates_list.txt") do start /wait wusa /uninstall /kb:%%a /norestart /quiet

Rather than tell the system to remove updates, even if they are not installed. I was shooting to use wmic qfe get hotfixid > updates_installed.txt then check if an update was installed and only run the command if it was found. But the FOR command doesn't seem to like reading the output file generated by wmic commands. I also tried wmic qfe get hotfixid /format:csv > updates_installed.csv. Both the updates_installed.txt & updates_installed.csv are human readable & excel can import them, but the FOR command just isn't having it right now.

---

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