Sledgehammer - Windows 10 Update Control

Discussion in 'MDL Projects and Applications' started by pf100, Nov 28, 2016.

  1. dkn849

    dkn849 MDL Novice

    May 31, 2021
    3
    0
    0
    #1821 dkn849, Jun 2, 2021
    Last edited: Jun 2, 2021
    Does the script disable the files that Microsoft Update Health Tools (MUHT) uses, and hence can we just rely on the script to handle it or should we uninstall MUHT? Are there any plans for the script to lock the files in "C:\Program Files\Microsoft Update Health Tools", or make and lock the folder to prevent MUHT from installing in the first place, like what's done with Update Assistant?
    @pf100
     
  2. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,899
    3,032
    60
    I gave up on that. I'm not going to spend a whole day fixing it every time something changes when people can just go to askwoody and check for themselves.
    I'll have more info on this later.
     
  3. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,899
    3,032
    60
    Hi everybody!
    So, I've been having serious problems with a paradoxical drug reaction. Exactly the same thing that happened to Jordan Peterson.
    A well-meaning doctor tried to help me and the drug he gave me (clonazepam) basically gave me a frontal lobotomy while I got off of it.
    I'll be fine.
    Obviously I haven't been here in a while and haven't kept up with things.
    The plan is update the script first, then study the latest version windows 10 update hijackers for anything new.
    Stay frosty.
     
  4. Carlos Detweiller

    Carlos Detweiller MDL Spinning Tortoise

    Dec 21, 2012
    4,459
    4,455
    150
  5. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,899
    3,032
    60
    I did some digging around about Microsoft Update Health Tools (MUHT) installed by KB4023057.
    It installs some files in "C:\Program Files\Microsoft Update Health Tools" which do effectively the same thing as an older version of the same KB4023057 which installed files in "C:\Program Files\rempl"
    The script already locks the rempl folder, but it's not really necessary because every method it calls to force an update is already disabled by the script downstream from that.
    So if you're using the script you can uninstall "Microsoft Update Health Tools" or not, it doesn't really matter, although being a control freak I'd rather it be gone.
    KB4023057 can't force an update with the script, so it's nothing to be concerned about.
    I'll probably force an uninstall of MUHT, or lock the folder, in a future update just because I enjoy killing this worthless crap with fire.
     
  6. Homer712

    Homer712 MDL Member

    Oct 22, 2018
    117
    43
    10
    @pf100 Wishing you well with the "paradoxical drug reaction" recovery. I actually had to Google what it was. Weird stuff to be sure!

    As for KB4023057, on my system, it is sitting quietly in the "hidden" folder in WuMgr, which is where it will continue to reside. This must be the fifth or sixth time that MS has re/re/re/released this particular update. If nothing else, they are persistent.
     
  7. dkn849

    dkn849 MDL Novice

    May 31, 2021
    3
    0
    0
    Wishing you well
    Any plans to do that in the next release? I'm aware WUB was "open sourced" previously in this thread, but I think it's worthwhile replacing it to make the script more explicitly open source, especially for the benefit of users who haven't seen the posts about reverse disassembling WUB.
     
  8. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,899
    3,032
    60
    @dkn849 Thank you for the thoughts. I've only reverse disassembled wub 1.0, not 1.1 which I'm still not sure if I'm going to use it in the next release or not.
    Wub works by blocking and unblocking permissions for registry entries, when I like to do it by locking files and folders instead.
    I can lock files in the script and disable wuauserv and usosrvc, and unlock them so they'll work at will with a toggle and I may do that, eliminating the need for anything wub does, but I need to do more testing.
    Windows 11 is near so I need to check for any changes that need to be made to the script for that, and time spent reverse engineering wub 1.1 is time taken away from that.
    I really need to put this project on github or somewhere and I plan to do that eventually after it's 100% open source.

    TLDR; I may drop wub and what it does altogether leaving only WUMT as closed source which is entirely optional to use in the script and I would have removed it but I had requests to leave it in there. I will never reverse engineer WUMT because I never use it.
     
  9. pf100

    pf100 MDL Expert

    Oct 22, 2010
    1,899
    3,032
    60
    #1829 pf100, Jun 21, 2021 at 16:32
    Last edited: Jun 21, 2021 at 19:50
    (OP)
    I went through the thread to find suggestions and this is what I came up with.
    If anyone sees anything I missed let me know. Thanks.

    1. The uninstaller doesn't display "Sledgehammer uninstalled. Press any key to exit . . ." when unins000.exe exists. - @Whistler4

    2. Warn against enabling wuauserv in configurator, then just leaving that window open which will defeat the script if you leave it like that long enough. (Not a suggestion, I threw this in here)

    3. Do something about KB4023057's uhssvc service and C:\Program Files\Microsoft Update Health Tools. - @dkn849

    4. Fix schtasks error message not being displayed - @rpo
    https://forums.mydigitallife.net/th...-10-update-control.72203/page-90#post-1656445

    5. Fix redundancy with LockFiles.cmd and script. - @rpo
    https://forums.mydigitallife.net/th...-10-update-control.72203/page-91#post-1656709
     
  10. Homer712

    Homer712 MDL Member

    Oct 22, 2018
    117
    43
    10
    #1830 Homer712, Jun 21, 2021 at 21:41
    Last edited: Jun 21, 2021 at 22:10
    Don't think this was missed, just thought I'd throw it in to see if it might be a possibility (I don't code, so, I have no idea if this would be a "sure, lets do it" type of thing, or a "are you kidding me!" type of thing).

    So, what are the chances that when a new version comes out, you could do an "install over existing install" update?