The normal state is un-rem'd. I rem-ed it by mistake is all. When I'm working on the script I don't want the uninstaller to delete the files I'm working on.
I hope that the silence here is because both v2.7.2 and v2.7.3 RC1 are functioning well and no changes are required. That being said, I continue to use v2.7.3 RC1 without any issues whatsoever, but was just curious, is a final of v2.7.3 going to be produced?
Just take a short brake from laziness, package the wub fix and the 2.7.3 RC into a new installer. Then, you can you can become lazy, again.
I'm running 2.7.3 RC1 on Windows 10, 1909. I had reason today to use the "E" response (first time ever) to allow me to get an app from the Windows Store. Did not work. The Store kept giving me an error warning that Windows Update was not turned on (or words to that effect). Tried a number of times, same result. So, after making an image backup via Macrium Reflect I did a total uninstall of Sledgehammer. Got to download the app from the Store just fine. Anyone else have this issue, or is it just me? Edit: You can only use the Windows Store with Edge, not with Firefox as I was trying to do. Used the "E" response, launched Edge, and the Store works just fine. Sorry, my error.
Question. Lately, I have been having strange issues with Task Scheduler service not running. In Services, I can attempt to start it, then it stops soon after. Opening Task Scheduler shows a window that reveals its certainly not working. Anyway. I am trying to get it sorted out. So my question is. Is this an issue for Sledgehammer? Does it rely upon the Task Scheduler? UPDATE: Ok. I think I just answered my own question when I opened Sledgehammer. Here's the message I get. And I have no idea why this is suddenly happening. "creating windows defender update WDU task errored" "Press any key to exit"
Sledgehammer relies on 3 tasks : Windows Defender Update Windows Update Blocker Auto-Renewal Lock system update hijacker files When sledgehammer starts, its deletes and creates these tasks. If the creation fails, sledgehammer sends an error message and stops.
@JJM789, I just moved from v2.7.0 to v2.73 rc1, and among the file copying, installing, and uninstalling of Sledgehammer files, I happened to generate the same error you did: "creating windows defender update WDU task errored." That error was caused by wdu.cmd not being in the \Sledgehammer\bin folder. (I had accidentally left it out.) You might want to check to make sure all the files are in the bin folder. Edit: For anyone stumbling on this, I probably jumped to the wrong conclusion as to the missing wdu.cmd being the cause.
I don't know how on God's green earth I missed (or just had a complete "senior" moment) the fact that "Matthew's Preferences" disables the same hijackers files that Sledgehammer does. So, when I ran the "Sledgehammer" recovery.cmd, the reason the sfc/scannow errors went away was that the recovery.cmd was undoing the same changes put in place by "Matthew's Preferences" as it would have had I still been using "Sledgehammer."
Thanks for your conclusion and clarification. Also, thanks for expanding horizons and awareness of these tools and others. I think exploring, learning, and sharing is always a good thing. And that includes alerts when there may be a need to check out and fix potential problems.
I totally agree, but I should have known better to start with. Felt like a total idiot once I realized what was going on.