Windows Update is controlled by the Technical Preview install and set to automatic.
I noticed that it is only partially automatic now.
There were two updates that did not download and install, one I noticed during the Preview Build Update (PBU) and one after the machine had been updated to 9926.
Pre PBU:
I'll need to review some notes, the WU history was wiped with the PBU
Post PBU: kb 3034229
The error might only be that a restart is required. I'll post after I restart the VM.
There are 2 settings, auto and notify. Check yours again. Unless I`m mis reading you.
It won't install updates when a restart is pending.. so you will have to restart, then it will once again install the updates when it's scheduled (2am usually) or if you manually check for new updates.
Sorry, I didn't mention that I checked - it was automatic.There are 2 settings, auto and notify. Check yours again. Unless I`m mis reading you.
I just blew off the notify pick - didn't think about it or select it. That will be another test.
This behavior isn't new to 9926, there were some updates "hanging" in previous releases too. Defender updates always got through.
Do me a favor and take a look at installed updates on your machine, if 3034229 is not there, check for updates to see if it is offered.
Different boxes and all that aside, I can't think of any reason why an update would not be downloaded and installed with an automatic setting. Well, maybe on reason: I didn't wait long enough for WU to process the offer.
maybe two reasons - it's a preview release
Thanks Brian,
Bill
.
Right, the machine had just been started, no pending restart except for the one after I ran WU manually.It won't install updates when a restart is pending.. so you will have to restart, then it will once again install the updates when it's scheduled (2am usually) or if you manually check for new updates.
Chronology:
Start machine
check for updates
accepted offers
download and install
posted screen shot
restarted.
Given that, there shouldn't have been an update in between. But who knows, maybe the auto snuck one in - doubtful though - the update history doesn't reflect that. I'm not concerned at this point - the thread was started to alert people about running Windows Update.
I just skimmed some of the MS lit and WU is the recommended 1st try solution if people are having issues with the 9926 install.
I think I saw it on the Insider hub app, but I've been reading a lot and testing too much.
+editFigured I'd check just in case. Only two updates in history.-edit
The failed to install 'error' was in fact due to a restart req'd as I thought.
The wording should be changed to Restart Req'd so normal users don't get upset by a erroneous failed install msg - it didn't fail, it just hasn't completed.
Check history after the reboot that was needed, scheduled, and expected. Emphasis on expected.
There was no in between update or prior update that would fit the scenario Mystery described. So.... it's a mystery.
