.BAT file to turn off updates?

Paul in Houston TX wrote:
David E. Ross wrote:
On 12/7/2014 9:45 AM, Paul in Houston TX wrote:
(PeteCresswell) wrote:
I always set Control Panel | Windows Update | Change settings |
Important Updates = "Check for updates but let me choose whether to
download and install them".

But every so often I'm in the middle of some development or
troubleshooting task, have to re-boot, and get the dreaded "Installing
xx updates...".

The last one took me down for about a half hour.

There is a nuisance factor there..... A *major* nuisance factor if I'm
in the middle of troubleshooting some production problem.

I am assuming that, somehow, Windows 7 manages to change my "Important
Updates" setting every so often.

So, The Question: can I schedule a .BAT or .CMD file to re-set the
"Important Updates" setting or some other setting so I don't get
blind-sided?
Why not just turn updates off?
That function is off on all my w7 machines.
When I feel like messing with updates I manually connect
to MS updates. Usually once per month.


Even if you turn updates off, every time you launch Windows Update it
will automatically download and install any updates to Windows Update
itself.

Ohh.. Thanks.
I knew the MS anti-virus would still update but did not know
about the update updater.

MSE will update itself (it uses BITS independently not Windows Update)
when defs surpass the hard-coded age limit..... though an update for
defs, if available prior to the age limit, will be offered and logged in
Windows Update.

--
....winston
msft mvp consumer apps

On 12/7/2014 12:13 PM, Paul in Houston TX wrote:
David E. Ross wrote:
On 12/7/2014 9:45 AM, Paul in Houston TX wrote:
(PeteCresswell) wrote:
I always set Control Panel | Windows Update | Change settings |
Important Updates = "Check for updates but let me choose whether to
download and install them".

But every so often I'm in the middle of some development or
troubleshooting task, have to re-boot, and get the dreaded "Installing
xx updates...".

The last one took me down for about a half hour.

There is a nuisance factor there..... A *major* nuisance factor if I'm
in the middle of troubleshooting some production problem.

I am assuming that, somehow, Windows 7 manages to change my "Important
Updates" setting every so often.

So, The Question: can I schedule a .BAT or .CMD file to re-set the
"Important Updates" setting or some other setting so I don't get
blind-sided?
Why not just turn updates off?
That function is off on all my w7 machines.
When I feel like messing with updates I manually connect
to MS updates. Usually once per month.


Even if you turn updates off, every time you launch Windows Update it
will automatically download and install any updates to Windows Update
itself.

Ohh.. Thanks.
I knew the MS anti-virus would still update but did not know
about the update updater.


Because I have two other anti-virus applications and because Microsoft
keeps having security vulnerabilities in its other software, I disabled
its anti-virus Microsoft Defender. It still kept running, even after a
cold bootup!! Then I found how to stop Microsoft Defender. Now I no
longer get nagged to update Microsoft Defender's virus database.

--
David E. Ross

The Crimea is Putin's Sudetenland.
The Ukraine will be Putin's Czechoslovakia.
See http://www.rossde.com/editorials/edtl_PutinUkraine.html.

Per ...winston?:
One can not indefinitely postpone updates when given the opportunity to
do so... Windows is hard coded to override the maximum postpone time
when surpassed (i.e. you get one shot to max the postpone time before
the code will continue the update process (usually within 30 min).

That one rings true in my case. Probably protecting me from myself....
and if I just allowed regular updates even without rebooting maybe they
would not accumulate and eat the machine for a half hour....

OTOH, if updates only happen when the box is re-booted....
--
Pete Cresswell

(PeteCresswell) wrote:
Per ...winston?:
One can not indefinitely postpone updates when given the opportunity to
do so... Windows is hard coded to override the maximum postpone time
when surpassed (i.e. you get one shot to max the postpone time before
the code will continue the update process (usually within 30 min).

That one rings true in my case. Probably protecting me from myself....
and if I just allowed regular updates even without rebooting maybe they
would not accumulate and eat the machine for a half hour....

OTOH, if updates only happen when the box is re-booted....


That's not necessarily how updates function.
Some updates don't require a reboot, some do.

Anything requiring a reboot would would always accumulate since those
updates requiring a reboot don't finalize the install - after a user
profile logoff during the shutdown and then later after the restart and
prior to Windows logon (i.e. Windows can't update files if the user
profile is present using Windows files).

--
....winston
msft mvp consumer apps