Windows 10: Windows Update Alert

usikpa's solution in post #78, particularly the 'trustedinstaller start= auto' part seems to have been the key. I've not suffered your problems, but I've found other threads where that turned out to be the cure.

Well done, now you can relax - at least, until the Spring Creators Update *Smile

 

This morning on checking for update I received the following alert:
<Your device is at risk because it's out of date and missing important security and quality updates. Let's get you back on track so Windows can run more securely. Select this button to get going:>
The only button available is to check for updates, and doing so result in to giving the same warning again.

?

OS 1709 Build 16299.192

:)

 

Update Alerts and Computer Waking

I have disabled the windows update service on my windows 10 system but I still keep receiving alerts asking me to schedule updates, and alerts saying updates weren't installed.

All kinds of alerts relating to windows update also wake my computer up, which keeps waking me up in the middle of the night.

I want windows update disabled completely, so no update alerts either. How can i do this?

 

Fake (?) Request to run update

This message is just a Windows 10 feature update notification:



The newest Windows feature update is here: How to remove the alert

 

Well, it's correct - you are out of date.
Your build number is the one for January 3, 2018 - KB4056892 (OS Build 16299.192)

Looks like your windows update hasn't been working these past three months. The first step in trying to fix that is to run the Windows Update Troubleshooter.

Troubleshoot Problems in Windows 10 with Troubleshooters

If that doesn't fix your problem, then see this tutorial.

Reset Windows Update in Windows 10

 

@Bree
Many thanks. I'll report the outcome.

 

The second fix did reset WU. But updates fail to install:

Note that the past few updates did install but gave same message:

I'll download that update manually and see if it does install that way.

 

This may help with the 0x80070bc2 error...

Cumulative Update KB4074588 Windows 10 v1709 Build 16299.248 - Feb. 13

 

Manual install successful as per Control Panel. But receiving a similar failed message, saying it need a restart to complete.
Done that with no avail. Same need a restart to complete showing up.
KB4074588 kept giving the same messages. until excluded with wushowhide.
As you can notice from control panel WU files those updates are there but no installing date showing.
BTW Still showing OS build as per my first post.

 

The Control Panel is the definitive source, if it says 'installed' then it is. Run Winver to check, KB4093112 puts the build up to 16299.371.

Reporting a failed install in Update History has been a known issue for cumulative updates for a while now...

Cumulative Update KB4093112 Windows 10 v1709 Build 16299.371 - Apr. 10

The perpetual 'a restart is required' is another matter though. A few other have reported this problem. In this thread a cure was to uninstall the update then reinstall it.
Windows Updated(16299.309).KB4088776 Restart is required to complete.

 

@Bree
Tried @usikpa #78 fix. It did help to get upgraded to OS build 16299.248 then 334
Now KB4093112 is taking so many restarts to update. Windows keep restarting before all stages are completed. Started 19 of 19, one by one now down to 2 of 13.
The funny thing is that now on WU settings KB4093112 check as installed, but not on Control Panel.
Spent the best of Sunday working on it. Well it was a miserable day outside so I guess I should not complain.
I may calling it a day, go to sleep and start all over tomorrow.
I'll keep you posted.
Thanks.

 

Finally after a ridiculous amount of restarts, check for update on WU then restart, mission complete.
KB4093112 shows both on Control Panel and on Settings. OS build is now 16299.371.

Thanks again @Bree for the help and the link.
Thanks @usikpa #78 that somehow got the ball rolling (Cumulative Update KB4093112 Windows 10 v1709 Build 16299.371 - Apr. 10.)

I'm not sure if I should mark the thread solved as it was a miss and hit for almost 24 hours. Too long to explain what I had to do.