Discussion in 'MDL Projects and Applications' started by pf100, Nov 28, 2016.
It stuck out like an erection on a donkey
See my edit: https://forums.mydigitallife.net/th...-10-update-control.72203/page-67#post-1534551
Sledgehammer Complete Update Termination and Negation
'edgy' but PC:
Sledgehammer CUTN pronounced "Sledgehammer Cut'n"
There is a funny video of a couple of girls sunbathing on a beach one one of them notices a nearby love-struck donkey. Worth a view, me thinks.
You need to login to view this posts content.
The Sledgehammer Toolkit For Usurping Windows Update (backronym: STFU WU).
Thanks everybody. Great responses (STFU WU, lol). I'm going to leave the name as it is. It is what it is, as the saying goes.
Now an update about not updating the project lately:
1) It works.
2) I haven't had any free time.
Having said that, there are preliminary plans in place to make a gui for Sledgehammer. Somebody/some people have offered to help with this. That's all I know right now. I'm just a dumb batch script guy and don't know how to make a proper gui (all you kids with your fancy mice and clicking things, heh). Also, I don't want to litter up this thread with everybody arguing over the best gui programming language.
I never felt a need before to learn a proper programming language because I've always been able to accomplish my goals with batch script. As I've mentioned before, I never really planned or thought this project would become as big it is. It just started out as a stupid batch file that disabled wuauserv, then re-enabled it (wow, that sure didn't work for long).
So, v2.6.0 works fine. Anybody who wants the advanced options already knows about that, I guess; that's the 2.6.1RC version posted a few pages back that I really need to finish but it works, so whatever.
I have not abandoned the project. Quite the contrary, I have big plans for it in the works. It'll basically do exactly what it does now, it'll just look nicer.
use 2.6.1rc4 since you published it -> again, great work @pf100 !!! no suspections it could be "mitigated" in sight.
amoung other things happend, i remember very well how ms forced users to install featureupdate 1803 to 1809 around 11 sept. 2018 using autoit scripts and authenticode certificates..
back then the difference between optional and security updates was not clearly made public.
then, thinking enough million users were effectively forced on 1809: "This update has been re-released because of a missing solution. If you installed build 17134.319, please install this newer version of OS build 17134.320" an update for an update because of a mysterious missing solution... just wow
sledgehammer keeps systems running
So glad your still updating this! May i ask where did you get WuMgr v0.9b because according to github latest it WuMgr v0.9a ?
Not sure, but unlike basically every other third-party project I've ever tried to build using Visual Studio, WuMgr actually just-builds. Just check out from git, open the .sln file, make some coffe while the ridiculous GUI loads, press the build button, and moments later you've cut yourself a usable pre-release build.
BULL You know your onions
GUI is extra work for something you do free of charge, i would rather you concentrate on the real nuts and bolts of sticking it to ms.
Thanks for the link, wonder why he never updated GitHub with latest release
Thank you @rpo.
Never mind, was blocked by security software.
I don't know if you can help but any suggestions appreciated. I'm trying to use your script on Windows 10 Enterprise 2015 LTSB and all I get is a, empty blue window that opens briefly followed by an empty black window that opens briefly, then closes. No options or actions offered.
Edit: Okay, you're saying security software was blocking the script.
I don't know why it wouldn't work. Have you tried right clicking and running the script as administrator? You shouldn't have to do that, but it sounds like a permissions problem, just a guess. Did you install from an unmodified iso and are allowing powershell and vbscript? I've never actually tried the script on ltsb 2015 before. If I'm not mistaken, unless they've changed it, on the Pro version in 2015 you could just disable wuauserv (Windows Update service) in "services.msc" and it would stay off. I'd be glad to help you troubleshoot the problem, so you're welcome to private message me if you want.
New question,do you get Office updates with this also?
This is true for Office 2016 and previous versions, but not for Office 2019 which is not updated by ms updates.