Automatic updates

"Paul" wrote in message
...
SC Tom wrote:
I'm running the latest preview of Win10 (Build 9926) on an Acer V731
laptop, and it runs quite well. A little slow to boot, even with Fast
Startup enabled, but not any worse than Win8.1, and I can live with that,
so no big deal.

For the past week, I get a pop-up about an auto-reboot at 12:00AM to
install updates. I've set the Win10 drive as the primary boot drive in
BIOS, and left it turned on all night so it could do it's thing, but I'm
still getting the message every day. If I manually check for updates,
there are none. My update history shows 5 were installed on 2/23, 1 on
2/13, 2 on 2/11, etc., all the way back to 1/25.

Anyone have any ideas on how to let the system know that's it's already
been rebooted numerous times, and to clear the message? It doesn't show
up in the "New Notifications" app (or whatever it is) in the systray, so
there's not even anything there to change. It doesn't seem to hurting
anything, just gets to be a little annoying after a while.

Thanks!

There's a hint here. A whole lot to digest, but you
can at least use Regedit to see if something is set.

http://blogs.msdn.com/b/hansr/archiv...tchreboot.aspx

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\
WindowsUpdate\Auto Update\RebootRequired
mumble...

Rather than the registry key being the end of the
story, that article seems to suggest that various
subsystems can scan and determine a reboot is
required. So don't be surprised if that bit
comes back, if something is amiss in some store state.
While you would hope that bit only gets set the one
time (by the postamble of the update installation),
it may not work that way in practice.

HTH,
Paul

Well, the installation of the two apps didn't help. I rebooted a while after
the installation, and within 5 minutes of booting up, the popup returned.

I ran MBSA v2.3 and it found no incomplete or missing updates, although in
all fairness, I think it only checks for Important security updates, and not
Recommended or Optional ones. After running the PowerShell script, and
installing the two apps, that entry in the event logs has not returned, so
I'm lost again on what the hell it's looking for.

Thanks for your help. I'm taking a rest on it for a while while I let my
brain cool :-)
--
SC Tom

On 02/03/2015 20:37, T wrote:
On 03/02/2015 12:28 PM, critcher wrote:
On 02/03/2015 18:13, T wrote:
On 03/02/2015 07:38 AM, critcher wrote:
On 02/03/2015 13:23, john szalay wrote:
"SC Tom" wrote in :

I'm running the latest preview of Win10 (Build 9926) on an Acer V731
laptop, and it runs quite well. A little slow to boot, even with Fast
Startup enabled, but not any worse than Win8.1, and I can live with
that, so no big deal.


Interesting, running 9926 on a Acer 5336 and am really impressed
as to how much faster it boots over Win7

41 secs , power-up to ready to go...

do have an issue with one update, it will not install
and there is no option to refuse it or hide it..



try this page http://support.microsoft.com/kb/971058


Did this work for you?



yes worked perfectly but I've got win 8, dont know if it will work with
win 10

Did you do all of the "regsvr32.exe" steps?



no just run the auto part as is shown. worked a treat on win8

---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com

"Paul" wrote in message
...
SC Tom wrote:
I'm running the latest preview of Win10 (Build 9926) on an Acer V731
laptop, and it runs quite well. A little slow to boot, even with Fast
Startup enabled, but not any worse than Win8.1, and I can live with that,
so no big deal.

For the past week, I get a pop-up about an auto-reboot at 12:00AM to
install updates. I've set the Win10 drive as the primary boot drive in
BIOS, and left it turned on all night so it could do it's thing, but I'm
still getting the message every day. If I manually check for updates,
there are none. My update history shows 5 were installed on 2/23, 1 on
2/13, 2 on 2/11, etc., all the way back to 1/25.

Anyone have any ideas on how to let the system know that's it's already
been rebooted numerous times, and to clear the message? It doesn't show
up in the "New Notifications" app (or whatever it is) in the systray, so
there's not even anything there to change. It doesn't seem to hurting
anything, just gets to be a little annoying after a while.

Thanks!

There's a hint here. A whole lot to digest, but you
can at least use Regedit to see if something is set.

http://blogs.msdn.com/b/hansr/archiv...tchreboot.aspx

HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\
WindowsUpdate\Auto Update\RebootRequired
mumble...

Rather than the registry key being the end of the
story, that article seems to suggest that various
subsystems can scan and determine a reboot is
required. So don't be surprised if that bit
comes back, if something is amiss in some store state.
While you would hope that bit only gets set the one
time (by the postamble of the update installation),
it may not work that way in practice.

HTH,
Paul

I'm beginning to think it's some kind of "ghost" message. Although it says
it needs to reboot as scheduled at 12:00AM, it doesn't reboot. Not worth the
effort anymore. I'll wait and see what the next build brings.
--
SC Tom

"SC Tom" wrote in message ...
I'm running the latest preview of Win10 (Build 9926) on an Acer V731
laptop, and it runs quite well. A little slow to boot, even with Fast
Startup enabled, but not any worse than Win8.1, and I can live with that,
so no big deal.

For the past week, I get a pop-up about an auto-reboot at 12:00AM to
install updates. I've set the Win10 drive as the primary boot drive in
BIOS, and left it turned on all night so it could do it's thing, but I'm
still getting the message every day. If I manually check for updates,
there are none. My update history shows 5 were installed on 2/23, 1 on
2/13, 2 on 2/11, etc., all the way back to 1/25.

Anyone have any ideas on how to let the system know that's it's already
been rebooted numerous times, and to clear the message? It doesn't show up
in the "New Notifications" app (or whatever it is) in the systray, so
there's not even anything there to change. It doesn't seem to hurting
anything, just gets to be a little annoying after a while.

Thanks!

I think I figured it out- Windows Time service was on manual (as it is on my
Win7 and Win8.1 machines). I noticed that my clock hadn't changed for DST,
so I put Time on auto, and the update it was trying to install downloaded,
installed, then prompted for either "Restart now" or "Schedule a restart." I
restarted now, and after 2 hours of up time, no message about rebooting at
12AM. Don't know why manual works for my previous versions of Windows, but
isn't acceptable on my Win10 :-(
--
SC Tom

On 03/09/2015 05:04 AM, SC Tom wrote:

I think I figured it out- Windows Time service was on manual (as it is
on my Win7 and Win8.1 machines). I noticed that my clock hadn't changed
for DST, so I put Time on auto, and the update it was trying to install
downloaded, installed, then prompted for either "Restart now" or
"Schedule a restart." I restarted now, and after 2 hours of up time, no
message about rebooting at 12AM. Don't know why manual works for my
previous versions of Windows, but isn't acceptable on my Win10 :-(

Thank for the update!