Thanks @BAU , the devkit and tools I installed to build Retroarch might be the culprit then, I'll uninstall them and see how it goes. Any way to fix this manually in case uninstalling those programs doesn't fix the issue ?
hopefully using symlinks and not actually replacing find.exe & etc. if still bad after uninstall and reboot, sfc /scannow, dims /restorehealth blah google-it blah it's the one thing that those commands can fix
Hi, Thanks for this tool. It helps a lot. Just wish to know if this tool also works reliabaily on Windows 11? I tried it in a virtual machine on Windows 11 and all I found is rotating circle when I access Updates in settings.
The script actually blocks Windows Update. You need to install updates through the script itself. Latest Windows 11 dev builds require the fixed WMIC-less PS version to work.
I don't know when this started, but as of now with Windows 11 (I didn't check with windows 10 and it doesn't really matter), when you enable the windows update service with the configurator to use the store, you have to also manually start the BITS service or the store won't work. In the next update I plan to automatically start the BITS service when you enable the windows update service with the configurator. I'm saying this now in case there is any objection to me doing this. I would completely enable/disable bits with the script through WUB, but I feel this could cause problems for those who need BITS set to manual or automatic. Any thoughts would be appreciated.
Leave it on Manual. It can be used for many other other purposes, too (including usage by the user over Powershell/bitsadmin). When being idle, BITS shuts down itself.
Yeah, that's what I was thinking. I don't like changing things that windows does unnecessarily and just starting BITS and letting it stop itself later would be the least intrusive thing to do.
I haven't read to the bottom of the thread yet but saw this almost as soon as I accessed the thread. I'm using Windows 11 - Insiders Edition. With the latest update, wmic has been removed. The .cmd scripts need to be updated to PowerShell. I was going to work on doing that for myself (PowerShell is what I do in my job) but it's been so long since I messed with batch language I figured I'd wait for version 3.0.
Install 2.7.3-rc1 linked to from this post: https://forums.mydigitallife.net/th...-10-update-control.72203/page-93#post-1680852 Then, replace the main script with the Powershell version found here: https://forums.mydigitallife.net/th...-10-update-control.72203/page-95#post-1701588 (use the Powershell variant).
Sure. For now, 2.7.3-rc1 works well. For special Windows 11 information (missing WMIC) read this post: https://forums.mydigitallife.net/th...-10-update-control.72203/page-98#post-1719904 And, please, don't full-quote the first post.
I thought I'd give an an overdue update. Sledgehammer 3.0 is nearing release and testing is almost done taking longer than I thought. Other than the obvious deprecated wmic fix, and I've mentioned something about this before, one of the biggest improvements that will be done is starting BITS when enabling wuauserv before using the store with the Configurator, and starting it and keeping it running while checking and downloading and installing updates. It makes the Store work a lot better, and it fixes the same windows update problem whether using the script or a clean OS that the script has never been used on, so it's definitely not the script causing it, but starting it makes updating a lot more reliable in my experience. I've tried this change on two pc's that were having problems updating and it completely fixed the problems they were having. Keep in mind that those pc's didn't have any other issues with windows update. And I'm considering adding the option in the Configurator in a future release to reset windows update to further fix issues if you guys think that would be a good idea.