Thread: Windows updates
View Single Post
  #10  
Old July 17th 18, 03:04 PM posted to alt.windows7.general
Ed Cryer
external usenet poster
 
Posts: 2,621
Default Windows updates

Paul wrote:
Ed Cryer wrote:
Ed Cryer wrote:
Art Todesco wrote:
On 7/15/2018 4:29 PM, Ed Cryer wrote:
Art Todesco wrote:
On 7/15/2018 2:41 PM, Paul wrote:
Art Todesco wrote:
Anyone know why there are so many Windows 7 updates coming
through? I've had updates everyday for about the last week.

Looping ?

Did you check your Windows Update history for
"failed" items ?

Â*Â*Â* Paul
All were successful and about half were MSE updates.Â* Also they
started on July 1 and there are updates for each day; and several
on some days.

Same here with the MSE updates. It started about the time you mention.
They used to update automatically.
I have "Check for updates but let me choose whether to download and
install them"; and it's been like that for years. So this change in
behaviour must have been occasioned by some MS amendment.

As you say, they now function just like Windows updates; and we get
the message saying updates available, leaving it up to us to download.

Ed

Yup, just got another one this AM.Â* It was optional "Silverlight"
and not optional MSE update.

My MSE updates now come as "Recommended". They used to be "Optional"
until 06.07.
I've had no Silverlight update for weeks. Two new MSE ones today;
both flagged for me to download at my leisure.

The only way I can think of getting back to auto-updating the MSE
things is to change settings to "download and install" for all
updates. And I ain't a gonna do that, no way.
So I'm stuck with what MS have dumped on me.

Ed


Now you can see why MS have done this. Or, at least I can.
It's straddled us with a choice. Do you want MSE definition updates to
be downloaded and installed automatically; or do you want them to hang
around up there until you take action and do it yourself?

Cunning! But very translucent when you hold up to your eyes their
policy of forcing updates down and in, willy-nilly of individual choice.

Well, stay with me. Keep your update settings under personal control,
and just download the virus-definitions as they get advertised.

Ed


There are materials here for manual install. This would
be if your Windows Update was completely broken.

https://www.microsoft.com/en-us/wdsi/definitions

As an experiment:

https://www.winhelponline.com/blog/u...-command-line/


Â*Â* # Administrator Command Prompt
Â*Â* # Use double quotes to handle spaces in the path names.

Â*Â* "%ProgramFiles%\Microsoft Security Essentials\MpCmdRun.exe" /?

Â*Â* "%ProgramFiles%\Microsoft Security Essentials\MpCmdRun.exe"
-SignatureUpdate

If that works, you could do a Scheduled Tasks (schtask???) via
the GUI and have your signatureUpdate done that way. *If* that's
what is really broken. You're going to have to confirm that
the MSE item in Windows Update, disappears after a SignatureUpdate,
to prove there isn't a *real* update coming in.

I don't know if a signature update, can also change the runtime
of MSE or not. An AV may need signatures or it may need runtime
code patching. A good design has both in say, a .msi file, and
is then transparent to the user. Sometimes, a reboot is needed
to finish the install of the runtime update (because killing
the running boss process, is frowned upon by the designers).

Maybe you can dream up a solution, without resorting to
"full auto" out of frustration. I never use "full auto"
on anything, if I can possibly avoid it.

The reason I'm familiar with the first link, is I have
a VM (not licensed) with Win10 running in it. I used a
certain technique to prevent Windows Update, and as a form
of punishment, Windows Defender gets into a snit during
an attempted Win10 session. "Feeding it a cookie" from the
wdsi page, tips it upright again, and eventually there
are enough CPU cycles to do something. But that's the
price you pay for putting roadblocks in the way. That VM
has successfully stayed at 16299 as a result. It's not
the version that mattered. Rather, it was an attempt to
see if the OS would try at some point, to "auto-repair"
itself. It easily has the materials, such as dism and sfc,
to effect a repair if it wanted to. It would only be
"three lines of code" so to speak.

Â*Â* Paul


I've decided to simply continue manually updating as they get found. The
service that checks daily and lets me know works well enough.
In fact (people, please restrain your contempt) I might switch to
auto-update; since for some time now I've been taking all Win7 updates.

Ed
Ads