Automatic updates [Archive]

SC Tom[_3_]

March 2nd 15, 11:38 AM

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!
--
SC Tom

John Szalay

March 2nd 15, 01:23 PM

"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..

critcher

March 2nd 15, 03:38 PM

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

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

Andy Burns[_3_]

March 2nd 15, 04:21 PM

john szalay wrote:

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

Win8.1

Power-on to windows logo 10 seconds; windows logo to windows sign-in
screen 5 seconds.

March 2nd 15, 06:10 PM

On 03/02/2015 08:21 AM, Andy Burns wrote:
> john szalay wrote:
>
>> 41 secs , power-up to ready to go...
>
> Win8.1
>
> Power-on to windows logo 10 seconds; windows logo to windows sign-in
> screen 5 seconds.
>

W8 and w10 are not powered off when it says shutdown. It is
in suspension.

Retest by shutting down, pulling out your power plug and any
battery for 30 second, then firing back up. If you don't
see your bios screen, you did didn't get it right.

March 2nd 15, 06:13 PM

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?

Andy Burns[_3_]

March 2nd 15, 06:27 PM

T wrote:

> Andy Burns wrote:
>
>> Power-on to windows logo 10 seconds; windows logo to windows sign-in
>> screen 5 seconds.
>
> W8 and w10 are not powered off when it says shutdown. It is
> in suspension.

I thought I had fast startup disabled, but I cheecked and I hadn't, so
disabled it, now windows logo to sign-in 7 seconds.

> Retest by shutting down, pulling out your power plug and any
> battery for 30 second, then firing back up. If you don't
> see your bios screen, you did didn't get it right.

The 10 seconds /was/ the BIOS screen

DevilsPGD[_4_]

March 2nd 15, 08:19 PM

In the last episode of >, T
> said:

>On 03/02/2015 08:21 AM, Andy Burns wrote:
>> john szalay wrote:
>>
>>> 41 secs , power-up to ready to go...
>>
>> Win8.1
>>
>> Power-on to windows logo 10 seconds; windows logo to windows sign-in
>> screen 5 seconds.
>>
>
>W8 and w10 are not powered off when it says shutdown. It is
>in suspension.
>
>Retest by shutting down, pulling out your power plug and any
>battery for 30 second, then firing back up. If you don't
>see your bios screen, you did didn't get it right.

Better yet, don't do that. Test based on how you actually use the
machine, which typically means you get the hybrid shutdown and nearly
instant startup.

--
Like a lot of husbands throughout history, Mr. Webster
would sit down and try to talk to his wife.
As soon as he'd say something though, she'd fire back with,
"And just what the hell is THAT supposed to mean?"
Thus, Webster's Dictionary was born.

critcher

March 2nd 15, 08:28 PM

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

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

March 2nd 15, 08:37 PM

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?

March 2nd 15, 09:00 PM

On 03/02/2015 10:27 AM, Andy Burns wrote:
> T wrote:
>
>> Andy Burns wrote:
>>
>>> Power-on to windows logo 10 seconds; windows logo to windows sign-in
>>> screen 5 seconds.
>>
>> W8 and w10 are not powered off when it says shutdown. It is
>> in suspension.
>
> I thought I had fast startup disabled, but I cheecked and I hadn't, so
> disabled it, now windows logo to sign-in 7 seconds.
>
>> Retest by shutting down, pulling out your power plug and any
>> battery for 30 second, then firing back up. If you don't
>> see your bios screen, you did didn't get it right.
>
> The 10 seconds /was/ the BIOS screen
>

I have noticed W10 more snappy too versus W8.1 on my
virtual machines too. W10 is more snappy in general.
(They still need to fix A LOT of bugs).

SC Tom[_3_]

March 2nd 15, 11:45 PM

"john szalay" <john.szalayatatt.net> wrote in message
31...
> "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..
>
>
You should have started your own thread instead of hijacking mine.
--
SC Tom

Paul

March 3rd 15, 12:52 AM

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/archive/2006/02/17/patchreboot.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

SC Tom[_3_]

March 3rd 15, 12:14 PM

"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/archive/2006/02/17/patchreboot.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 don't have that registry key, or the others listed in the article or the
linked articles. I guess the registry seems to think everything is
hunky-dory :-(

I looked in the event viewer and found a couple of possibly related entries.
I've been working through that with the suggestions here:
<http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/windows-update-errors/6e7fa721-2a77-41be-b28e-ebdc6c82862e>

From there and other related links, it looks like a common problem. I'll
play with these suggestions for a while and see if that makes a
difference/fixes it. It seems to be pointing to Microsoft Reader and
microsoft.windowscommunicationsapps (whatever that is). I have run the
PowerShell commands listed, changing the package names to what are current
on my PC, and will try a reboot to see if the "scheduled reboot" message
returns.

Since it is a preview version, and it's not my main PC, I probably won't be
spending a lot of extra time on it since it doesn't seem to be affecting
anything else. But then again, my AR/OCD behavior probably won't let me let
it go right away <wink wink nudge nudge>.
--
SC Tom

SC Tom[_3_]

March 3rd 15, 12:43 PM

"SC Tom" > wrote in message ...
>
>
> "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/archive/2006/02/17/patchreboot.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 don't have that registry key, or the others listed in the article or the
> linked articles. I guess the registry seems to think everything is
> hunky-dory :-(
>
> I looked in the event viewer and found a couple of possibly related
> entries. I've been working through that with the suggestions here:
> <http://answers.microsoft.com/en-us/insider/forum/insider_wintp-insider_update/windows-update-errors/6e7fa721-2a77-41be-b28e-ebdc6c82862e>
>
> From there and other related links, it looks like a common problem. I'll
> play with these suggestions for a while and see if that makes a
> difference/fixes it. It seems to be pointing to Microsoft Reader and
> microsoft.windowscommunicationsapps (whatever that is). I have run the
> PowerShell commands listed, changing the package names to what are current
> on my PC, and will try a reboot to see if the "scheduled reboot" message
> returns.
>
> Since it is a preview version, and it's not my main PC, I probably won't
> be spending a lot of extra time on it since it doesn't seem to be
> affecting anything else. But then again, my AR/OCD behavior probably won't
> let me let it go right away <wink wink nudge nudge>.

I installed the latest version of Reader and the Mail, Calendar, and People
app (microsoft.windowscommunicationsapps) from the Store. Maybe that will
take care of it, or it may just make it worse, looking for an update that's
already (somewhat) there LOL.
--
SC Tom

SC Tom[_3_]

March 3rd 15, 07:02 PM

"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/archive/2006/02/17/patchreboot.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

critcher

March 3rd 15, 07:50 PM

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

SC Tom[_3_]

March 4th 15, 09:09 PM

SC Tom[_3_]

March 9th 15, 12:04 PM

"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

March 9th 15, 06:44 PM

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!