Originally Posted by cookieboyeli
Yup, working now.
I didn't check to see if you used the icon I posted or not before. Can we actually use this one? It's a lot cleaner. I want to make sure it's compatible with large icons as well so high DPI users and large icon users can have a nice looking icon too.
(Is there any to use PNG or must we use ICO? ICO is huge!)
I also just realized the wording on failed updates is incorrect. If updates fail it still says they have been uninstalled.
EDIT: (When I don't read I post incorrect things
The script ran but didn't hide two updates.
This is already a known issue, but perhaps it can still be solved with new information.
I noticed they're recommended updates listed in the optional section. (The slanted ones). I checked all the others, they're fine to install.
The only thing I can really think of is the fact that these updates have been REISSUED recently. At one point I had two of the same update listed, though with different sizes, release dates, and priorities. These two updates USED TO be optional, but were rereleased as RECOMMENDED in October. (May have been September).
Does hiding updates work the same no matter the category or status of it? I think there are some combinations where it doesn't which is why we are seeing these particular unusual updates not hiding.
I had included that icon as an optional icon, it is now the only icon.
Fixed the issue with the failed uninstall wording. There was a misspelling that was causing the failed flag to not be triggered.
Hiding updates is the same regardless of priority. It's a simple boolean setting: IsHidden.
The results you're seeing are not from failure to hide the update (it would actually say it failed if that was the case). The 3035583 update is returning as already hidden, which means the setting IsHidden is already set to true. Why that isn't actually hidden in Windows Update is beyond me. The other one, it actually returning that the update was not found. Which means that the KB is not coming up in the search results for whatever reason. There is supposedly a way to include potentially superseded updates in the search results, but that will require some more testing before I can implement it. I'm not sure that will solve the problem either.
BatchUpdateUninstallerv4.3.2.zip 158k .zip file
- Final icon added.
- Fixed issue with failed flag not being triggered on failed attempts to uninstall an update.
You may want to add the following to #3 in the How to Use section of the first post:
KB's must start on line 3 of the text file as the script skips the first two lines as instructional/informational lines.
Also, you should be able to delete #3 from known issues. The script should now kill itself if ran with no arguments (which is what would happen if double clicked).
Originally Posted by ASUSfreak
And that's why i want tolearn SOFTware as I build stuff and know "everything" from HARDware...
Damn I'm jealous
Anyway I started a theread a few weeks ago about asking stuff like this:
1) can someone make a .exe to do this automatically
2) if not, anyone has Win 7 with KB's uninstalled (like V-Lite stuff)
So this thread answered BOTH! (tho not sure where to findt Murphy86 or whatever ISO's)
Great stuff guys!
BUT worst case scenarion? Can it cause PC not to boot or run into trouble or something? (as I did format C 3 weeks ago
EDIT: OP, shall I install your Post 1 4.2 version, or the 4.3.1 version in latest post?
I'd love to compile this into an .exe, but the free batch to exe converters are for personal use only, so I'd not be able to distribute it. I may eventually rewrite as an actual windows application, but I'm just doing this in my spare time (which I don't have a lot of) so who knows when/if that will happen.
As for the worst case, we've had no issues like that brought to our attention. But, I will disclaim: Use this script at your own risk. Overclock.net, Cookieboyeli, nor agawthrop are responsible for any damages caused to your PC from the use of this script.Edited by agawthrop - 10/25/15 at 1:15pm