New
#1
Seems now that a forced check for updates is updating to 1809
Had one client call and so I went to check on my unupdated 1803 install and checked for updates and there it was.
Had one client call and so I went to check on my unupdated 1803 install and checked for updates and there it was.
This is to be expected now that the rollout has restarted. At present only a few machines will find 1809 when manually checking for updates. As MS gather more telemetry that number will increase. MS said that was the way it would happen here...
Windows 10 October 2018 Update version 1809 Now Re-Released - Windows 10 ForumsMicrosoft said:
I have a "gut" feeling that MS opened the faucet up some more today.As MS gather more telemetry that number will increase.
I think you are right, I'm increasingly seeing Ten Forum members reporting they got it by manually checking. As yet I've only seen a couple of reports that may have got it automatically. I'm leaving a couple of machines on 1083, one running 24/7, to check when automatic delivery starts. So far neither see 1809 automatically (last automatic check was less than an hour ago).
I had done a test clean install of 1803 yesterday on my Test-Bed machine, and after the last few 1803 updates, it turned around almost immediately and offered 1809 on a Check for Updates.
fyi wushowhide.diagcab does not work anymore, it is not able to block 1809 permanently... afaik WuMgr should work on