Killl Automatic Win10 Pro Updates

W10 Tweaker · 10 Dec 2021

Matthew Wai said:

Both of the above links go to page 25.
The following link goes to the first post on the first page.

Using CMD script and VBScript to control Windows Update

The reason is that the URL ends in "-25.html". See below:

https://www.tenforums.com/tutorial-submissions/148203-using-cmd-script-vbscript-control-windows-update-25.html

Yes, I had observed this "-25.html" feature. I also made an effort to fix it by tweaking the url yet regardless of the actual url in my post, it is redirected to page 25 again. Check this out, this is a screen capture of my post using the same url as you've posted and it still gets redirected to page 25.

Killl Automatic Win10 Pro Updates-1210-url-redirect-issue.jpg

As much as I find it fascinating I just don't have sufficient time to chase down this issue at this time. I'm trying to get all my firewood moved inside asap instead of piled under a tarp next to the woodshed.

Matthew, can you explain the resulting url difference between your post & mine?

Paul Black · 10 Dec 2021

You Right-Click the Post Number [ top right of a particular post ] and Copy Link Address.

Matthew Wai · 11 Dec 2021

W10 Tweaker said:

it still gets redirected to page 25.

Copy and paste the following URLs onto your browser and press "Enter". See whether it will go to page 1 or 25.

www.tenforums.com/tutorial-submissions/148203-using-cmd-script-vbscript-control-windows-update.html
www.tenforums.com/tutorials/148203-using-cmd-script-vbscript-control-windows-update.html
www.tenforums.com/showthread.php?t=148203

All of them go to page 1 on my Chrome, Firefox, and Edge. Perhaps they take only the author to page 1 and take all others to page 25.

W10 Tweaker said:

Matthew, can you explain the resulting url difference between your post & mine?

Post #12 above has explained it. Different posts have different URLs, as each post has a specific post number. The post number of post #12 is "post2344069" as shown below:

www.tenforums.com/windows-updates-activation/188677-killl-automatic-win10-pro-updates-post2344069.html

However, I don't know who/why/how "-25" was added before ".html" in your URL.

W10 Tweaker · 12 Dec 2021

Matthew Wai said:

Use it only after Windows has been activated. Assuming unactivated Windows will not be updated automatically, there is no need to control Windows Update before activation.

Both of the above links go to page 25.
The following link goes to the first post on the first page.

Using CMD script and VBScript to control Windows Update

The reason is that the URL ends in "-25.html". See below:

https://www.tenforums.com/tutorial-submissions/148203-using-cmd-script-vbscript-control-windows-update-25.html

Hi Matthew

Let me try to explain again.

As usual, I used a pre-saved bookmarked shortcut for your tutorial in my post #3 and have captured the same along with the mouse-over destination. I have been successfully using this same shortcut for ages and you can see from the image, there is no -25.html in this url.

My shortcut = https://www.tenforums.com/tutorials/...ws-update.html

Killl Automatic Win10 Pro Updates-1212-my-tutorial-shortcut.jpg

When I use this shortcut in my browser it loads page 1.
When I edit my post #3, it still contained the same url I copied from my shortcuts.
After I saved post #3 and do a mouse-over on the link, it has been redirected to page 25, according to what I see in the taskbar.

In order to beat this horse into submission, I copied the url from your post #8 and replaced the url in my post #3.
After saving the post and performing the mouse-over test, I again see a redirection to page 25.
When I go back & edit my post, I still see the url from your post. This url directs to page 1 when used in my browser.

W10 Tweaker · 12 Dec 2021

Urls copied from post #13.

www.tenforums.com/tutorial-submissions/148203-using-cmd-script-vbscript-control-windows-update.html

www.tenforums.com/tutorials/148203-using-cmd-script-vbscript-control-windows-update.html

www.tenforums.com/showthread.php?t=148203

All 3 of these urls direct to page 1 when used in my browser or from this new post.

The first url was the original I used in my post #3.

From post #3, it was redirected to page 25.

Update

Matthew, the mystery is over. I replaced the link in my post #3 using my shortcuts (same as originally used) and it now magically directs to page 1.

The only evidence we have is from your post #8 where it shows my link pointing at page 25.

John must be messing with our heads just for sport.

My apologies to the OP for this diversion.

anaron · 02 Feb 2022

W10Tweaker. the diversion is not an issue. However my last question was not addressed.

What would possibly be resetting the update settings?

After a considerable amount of research, I think I have found the problem - “Windows Update Medic Service”.
The following is my procedure to disabled auto updates and keep them disabled until I enable it to do my manual update checks. So far it seems to be working perfectly.

1. Local Group Policy Editor>Computer Configuration>Administrative Templates>Windows
Component>Windows Update>Configure Automatic Update>Edit Policy Settings>Disable>Apply>OK
2. Windows Services>Windows Update>Properties>Disable>Stop
3. Disable WaaSMedicSvc:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WaaSmedicSvc
Right click "Start" in right column. select "Modify" and change the value from 3 to 4. Click OK.
Right click WaaSmedicSvc in the left column and rename it. Restart the computer
4. Enable #2 to do a manual update. When completed, set #2 to Disable>Stop.

Any suggestions would be appreciated!

steve108 · 02 Feb 2022

You may find this useful
What is Windows Update Medic Service (WaaSMedicSVC) and How to Disable It

anaron · 02 Feb 2022

Nice article. What I have done is pretty much as they suggested,
Thanks

steve108 · 02 Feb 2022

Have you run "sfc /scannow" since making your changes? Curious if it runs without finding corruption.

BLaZiNgSPEED · 02 Feb 2022

anaron said:

W10Tweaker. the diversion is not an issue. However my last question was not addressed.
After a considerable amount of research, I think I have found the problem - “Windows Update Medic Service”.
The following is my procedure to disabled auto updates and keep them disabled until I enable it to do my manual update checks. So far it seems to be working perfectly.

1. Local Group Policy Editor>Computer Configuration>Administrative Templates>Windows
Component>Windows Update>Configure Automatic Update>Edit Policy Settings>Disable>Apply>OK
2. Windows Services>Windows Update>Properties>Disable>Stop
3. Disable WaaSMedicSvc:
Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WaaSmedicSvc
Right click "Start" in right column. select "Modify" and change the value from 3 to 4. Click OK.
Right click WaaSmedicSvc in the left column and rename it. Restart the computer
4. Enable #2 to do a manual update. When completed, set #2 to Disable>Stop.

Any suggestions would be appreciated!

This is not going to work for the simple fact that there's an UpdateOrchestrator and WaaSmedic Task Schedulers that by default scan for updates even if automatic updates are set to disabled.

For example if you try to disable Windows Update and WaaSmedic services then the WaaSmedic Task Scheduler that runs on a weekly basis will revert those services back to Manual (Start).

Windows 10 doesn't let you disable those task schedules as you get permission issues.

However, I have good news! Windows Update Blocker v1.7

You need Windows Update Blocker tool. This takes care of both the task schedules related to Update Orchestrator, Windows Update and WaaSmedic.

With a click of a button the blocker tool will set all those task schedulers to disabled as well as the services. That way with task schedules being set to disabled, these will no longer trigger to revert the services back to Manual.

If you then want to use Windows update again with a click of a button you can revert the changes back to how you wanted.

For the benefit of the doubt, you can also set Target Release Version to a specific version How to Specify Target Feature Update Version in Windows 10

Like for example I'm on final build version of 1903. I have set

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"ProductVersion"="Windows 10"
"TargetReleaseVersion"=dword:00000001
"TargetReleaseVersionInfo"="1903"

What this does is fool Windows 10 to think you are up to date. In essence you are only up to date with final build version. Windows 10 will still be scanning for updates periodically by default due to those stupid task schedules.

For this as I said, you use Windows update blocker tool to disable task schedules. That way at least there wouldn't be further system resources being using for searching updates.

I've been using it that way for over 2 years now without an issue. I recently reinstalled Windows 10 1903 from my old USB and followed same procedure on a clean install with Ethernet cabled unplugged so that way I can configure Target Release to 1903 before I reconnect cable. Now Windows 10 updates will only update to final build and not force me to latest feature updates.

I still need to re-enable Windows Update for driver updates when I buy for example a new gamepad, mouse, keyboard, phone, etc. Then after device drivers are installed you can then disable the blocker tool again!