170 important updates available

On 08/28/2017 06:08 PM, Stan Brown wrote:
On Mon, 28 Aug 2017 09:32:30 -0700, Ken Blake wrote:
What you do is of course up to you, but let me point out that whenever
any new version comes out, what you hear is almost always negative.



I don't really think that's true. It's true (to a first
approximation) when every _second_ version comes out: Windows ME,
Windows Vista, Windows 8, Windows 10. But there were general sighs of
relief at Windows XP and Windows 7 and Windows 8.1, as I recall.




XP was one of the best received operating systems since Win95.


I don't recall too many good things being said of ME, Vista or Win8.


Once SP1 came out for Vista I thought it was pretty good, but too many
people were turned off by it for it to have been a great success.

On Mon, 28 Aug 2017 18:03:21 -0500, philo wrote:

The mandatory reboot is the main complaint I have with Win10.

Unless things have changed, after an update that requires a reboot, the
maximum it can be put off for is 24 hours.

That's insane for anyone who is in the middle of a job.

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

--

Char Jackson

In alt.windows7.general, on Sat, 26 Aug 2017 20:30:27 -0400, micky
wrote:

Wow, I just held the cursor over the Update icon in the systray and up
poppeed a screen that said 170 important updates available

11 optional update available.

And this after I just installed some. (I know from experience it does
this in tiers)

Anything other than installing them all that I should do?

Thanks


This is what happens when someone either lets a win7 laptop sit for
months or upgrades from Vista and doesn't do the updates.

Follow-up.

It did about 30 of them the first night, though after that, there were
probably 300 lines in the update log, all for that day, many listed as
failure to install. I haven't looked but some of them must have
appeared more than once.

Then it said there were 130 updates available (170 - 39), so i said
Install and it took hours to download them all (800megs).

I don't get it. I thought they were all dl'd the first time. Does it
think they failed to install because the file was corrupt?

But that finished after I went to bed and now it says
"130 updates not needed".

That's cute, after it said they were important and spent hours
downloading them.

But it installed them after all. Only 8 optional ones left

In alt.windows7.general, on Mon, 28 Aug 2017 23:04:32 -0500, Char
Jackson wrote:

On Mon, 28 Aug 2017 18:03:21 -0500, philo wrote:

The mandatory reboot is the main complaint I have with Win10.

Unless things have changed, after an update that requires a reboot, the
maximum it can be put off for is 24 hours.

That's insane for anyone who is in the middle of a job.

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

It was called noreboot.exe .

And it works.

micky wrote:
In alt.windows7.general, on Sat, 26 Aug 2017 20:30:27 -0400, micky
wrote:

Wow, I just held the cursor over the Update icon in the systray and up
poppeed a screen that said 170 important updates available

11 optional update available.

And this after I just installed some. (I know from experience it does
this in tiers)

Anything other than installing them all that I should do?

Thanks


This is what happens when someone either lets a win7 laptop sit for
months or upgrades from Vista and doesn't do the updates.

Follow-up.

It did about 30 of them the first night, though after that, there were
probably 300 lines in the update log, all for that day, many listed as
failure to install. I haven't looked but some of them must have
appeared more than once.

Then it said there were 130 updates available (170 - 39), so i said
Install and it took hours to download them all (800megs).

I don't get it. I thought they were all dl'd the first time. Does it
think they failed to install because the file was corrupt?

But that finished after I went to bed and now it says
"130 updates not needed".

That's cute, after it said they were important and spent hours
downloading them.

But it installed them after all. Only 8 optional ones left

All it needs to do, is check the signature, and it should
accept them. Computing a hash (fingerprint) on a file like
that, the odds of accepting a "duff" file are exceedingly low.

The optionals should have at least one TimeZone patch suited
to your own country.

At least one of the Windows OSes, mixes both the desktop and
server products, into the same batch of updates. If you read
the patch descriptions carefully, you can reject the ones that
are server-specific. That would only be a "win", if your allowed
download cap is tiny (you're on Satellite Internet). Even dialup users
have a higher cap than Satellite users do.

Paul

On 8/26/2017 5:30 PM, micky scribbled:
Wow, I just held the cursor over the Update icon in the systray and up
poppeed a screen that said 170 important updates available

11 optional update available.

And this after I just installed some. (I know from experience it does
this in tiers)

Anything other than installing them all that I should do?

Thanks


This is what happens when someone either lets a win7 laptop sit for
months or upgrades from Vista and doesn't do the updates.

you should not install any of them. Its all rigged.
for that is what Communist Gates is,commy thief.
We never let Windows update itself. To many reasons.
What you need to do, is eliminate the services, shut down some of them
that run in the background and do not show their face to you. Yet, they
are still running their mouth eating up your internet. And if
you do not have a network meter, then you need to get one so you can
watch when your machine is opening its big mouth for stupid reasons.
you can also use the Resource Monitor to figure what kind of crap is
calling for updates from MS thief.
As I said, you should not install any of them, unless you want to bog
down your machine with false security services.

It would be best, if you open up the Administration Services and
comprehend just what MS is doing behind your back with all that ****
they run that talks to many other companies on the net, without your
permission. First thing I would do if I were you, is get rid of
the Windows Firewall. And put in a real one.

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.

--
Stan Brown, Oak Road Systems, Tompkins County, New York, USA
http://BrownMath.com/
http://OakRoadSystems.com/
Shikata ga nai...

On Tue, 29 Aug 2017 06:21:22 -0400, Stan Brown
wrote:

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.

I'd be surprised if that works for Win 10. They use a different
mechanism there.

--

Char Jackson

In alt.windows7.general, on Tue, 29 Aug 2017 10:04:57 -0500, Char
Jackson wrote:

On Tue, 29 Aug 2017 06:21:22 -0400, Stan Brown
wrote:

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.

I'd be surprised if that works for Win 10. They use a different
mechanism there.

I got mixed up what group I was reading. What I just posted and what
Char referred to, noreboot.exe, was for win10. The file I posted is not
a simple registry tweak. It's an on-going, hourly registry retweak. And
not of a flag but of what hours are the active hours.

I think win10 was rewritten so that the simple retweak wouldn't work,
and so someone wrote a more complicated tweak. Sort of the inverse of
the saying, If you make something idiot-proof, people will invent a
bigger idiot.

On 08/28/2017 11:04 PM, Char Jackson wrote:
On Mon, 28 Aug 2017 18:03:21 -0500, philo wrote:

The mandatory reboot is the main complaint I have with Win10.

Unless things have changed, after an update that requires a reboot, the
maximum it can be put off for is 24 hours.

That's insane for anyone who is in the middle of a job.

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?




Oh I know how to tweak it , but for the average user it might be a PITA

thank yoy

On 08/29/2017 10:04 AM, Char Jackson wrote:
On Tue, 29 Aug 2017 06:21:22 -0400, Stan Brown
wrote:

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.

I'd be surprised if that works for Win 10. They use a different
mechanism there.




To change the forced reboot, as I thought I had mentioned previously, I
use Policy Editor

On Tue, 29 Aug 2017 16:48:26 -0500, philo wrote:

On 08/29/2017 10:04 AM, Char Jackson wrote:
On Tue, 29 Aug 2017 06:21:22 -0400, Stan Brown
wrote:

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:

Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?

A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.

I'd be surprised if that works for Win 10. They use a different
mechanism there.




To change the forced reboot, as I thought I had mentioned previously, I
use Policy Editor

What do you do, exactly?

--

Char Jackson

Char Jackson wrote:
On Tue, 29 Aug 2017 16:48:26 -0500, philo wrote:

On 08/29/2017 10:04 AM, Char Jackson wrote:
On Tue, 29 Aug 2017 06:21:22 -0400, Stan Brown
wrote:

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:
Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours' of the
PC, or whatever that feature is called. Are you interested in something
like that?
A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.
I'd be surprised if that works for Win 10. They use a different
mechanism there.



To change the forced reboot, as I thought I had mentioned previously, I
use Policy Editor

What do you do, exactly?


To make the question easier to answer...

(in an Admin Command Prompt)

gpresult /h gpreport.html

and that's supposed to summarize all the non-default policies.
That's how you find a needle in a haystack.

Paul

On 08/30/2017 03:17 AM, Paul wrote:
Char Jackson wrote:
On Tue, 29 Aug 2017 16:48:26 -0500, philo wrote:

On 08/29/2017 10:04 AM, Char Jackson wrote:
On Tue, 29 Aug 2017 06:21:22 -0400, Stan Brown
wrote:

On Mon, 28 Aug 2017 23:04:32 -0500, Char Jackson wrote:
Not too long ago, I posted a link to a 3rd party program that
essentially stops the forced reboot by moving the 'active hours'
of the
PC, or whatever that feature is called. Are you interested in
something
like that?
A simple Registry tweak will do it:

http://oakroadsystems.com/tech/7tip.htm#RunNoReboot

That's for Windows 7. I wouldn't be a bit surprised if it works for
Windows 10 as well.
I'd be surprised if that works for Win 10. They use a different
mechanism there.



To change the forced reboot, as I thought I had mentioned previously,
I use Policy Editor

What do you do, exactly?


To make the question easier to answer...

(in an Admin Command Prompt)

gpresult /h gpreport.html

and that's supposed to summarize all the non-default policies.
That's how you find a needle in a haystack.

Paul




https://www.windowscentral.com/how-s...lly-windows-10