Replies

[frankus333]

 

This reply should be up under #2004100 but I can’t seem to get it there.  (Also, the site search function is not taking me to post numbers I enter into the search box; goes to other posts of mine in same thread.?!)

Thanks b and Woody

I agree that checking and confirming whatever settings used each month is wise, and no real bother.

If I become aware of any worthwhile updates that are issued during the pause period, I presume I can take the pause off with the “Resume updates” button, and filter with wushowhide.   After that, resetting the pause to any specific day/date again (probably back to the weekend before Patch Tuesday) is quick and easy.

woody wrote:

It simplifies the article – the Pause Updates option is available for both Home and Pro.

I only have Home, so can’t see, but does this mean the “Advanced options” possibility of setting a specific day/date to pause until is not available in Pro?  If so, that seems a bit unfair for Pro users who don’t want to get into the intricacies of policy settings.

Cheers

Moderator note: To “nest” a reply to a post, click on REPLY at the top of post you want to respond to.

• This reply was modified 5 years, 5 months ago by frankus333.
• This reply was modified 5 years, 5 months ago by frankus333.

G’day folks

Re my above query about Defender automatically updating; it seems it does if I wait long enough (7 days).  The update gets through the above advanced pausing setting, and presents itself as ready to download, and doesn’t download automatically.

That sounds OK, but I’d prefer it updated its definitions every day.  I don’t suppose there is a way to make it do that on a Home machine?

Cheers

G’day folks

Just wondering why the “hit pause updates for 7 days three times” is still recommended over the advanced option of setting a specific day/date, as per my previous post #2001357?

Is it the case that the recommended method holds for each month without having to be reset (which the advanced method requires)?

If so, is that really an advantage? Is the timing automatically synchronised at each patch Tuesday, or from whenever the updates start to download (not really a safe option)?

Cheers

[frankus333]

G’day folks

I was running Win 10 Home 1809 (not Pro with all the settings options), and a few days ago I allowed the feature update to 1903, to ensure I could easily get it, before having to fend off the upcoming 1909 offering. There is what seems a great improvement in the Advanced Options for pausing updates; allowing a setting of a very specific day/date up to 35 days into the future to hold off updates.

Just wondering why this option has not been recommended, instead of the process Woody recommends, of hitting the “Pause updates for 7 days” button three times? Does this soon to be fixed bug mean this new setting was not to be trusted?

If it works reliably, I envisage setting it to the weekend before patch Tuesday each month, which seems to be about when Woody tends to raise the DefCon level. I have set it up this way for this month (resuming updating on 8th December), and the setting hasn’t disappeared or changed through reboots over the last few days so far.

Also just wondering whether pausing updates prevents Defender from automatically updating definitions? I thought Defender was supposed to automatically update its definitions regularly (daily, or after each reboot?), but it doesn’t seem to be doing so.

Anyway, I am enjoying being able to allow my wifi to connect automatically at each boot, and not having to disable WU after each 24 hours or so.  (Setting wifi to metered didn’t seem to block all updating; only feature updating.)  Fingers crossed.  At last, this is the next best thing, if we can’t have reliable indefinite deferral, as per Win 7/8.1.

Cheers

• This reply was modified 5 years, 6 months ago by frankus333.
• This reply was modified 5 years, 6 months ago by frankus333.

1 user thanked author for this post.

lmacri

G’day again folks

As per my above post, can anybody comment on how reliable/trustworthy this new Win 10 1903 advanced option of setting a very specific day/date to extend the pausing of updates to, as opposed to the option Woody recommends, of hitting the “Pause updates for 7 days” button three times?

If it works reliably, I envisage setting it to the weekend before patch Tuesday each month, which seems to be about when Woody raises the DefCon level.

Also just wondering whether pausing updates prevents Defender from automatically updating definitions? I thought Defender was supposed to automatically update its definitions regularly (daily, or after each reboot?), but it doesn’t seem to be doing so.

Anyway, I am enjoying being able to allow my wifi to connect automatically, and not having to disable WU after each 24 hours or so.  At last, this is the next best thing, if we can’t have reliable indefinite deferral, as per Win 7/8.1.

Cheers

Oops; sorry folks, that should have been obvious.  Thanks PKCano

Cheers

G’day folks

Just wondering how to hide updates on Win 7 Pro 32 bit eeePC machine?  When I tried to install wushowhide, it tells me it is not compatible with my version of windows?

[frankus333]

G’day folks

I was running Win 10 Home 1809, and I allowed the feature update to 1903, to avoid having to keep dodging the upcoming 1909 offering.  There is what seems a great improvement in the Advanced Options for pausing updates; allowing a setting of a definite date up to 35 days into the future to hold off updates.

Just wondering why this option is not recommended, instead of the process of hitting the “Pause for 7 days” three times?

Does this new setting not work as advertised?

I hope it does work properly; it looks like it will save me from having to keep WU disabled, and my wifi not automatically connecting.  (Setting wifi to metered didn’t seem to block all updating; only feature updating.)  Fingers crossed.

Cheers

• This reply was modified 5 years, 6 months ago by frankus333.
• This reply was modified 5 years, 6 months ago by frankus333.

Thanks Woody

So I take it that means the timing starts in relation to some time stamp that each patch comes with, and not from when a particular machine sees the patch (which could be some significant time after release if the machine was kept switched off for a long time.)?

G’day again folks

Just successfully Group A updated a eeePC 1000H 32 bit Win 7 notebook without any stalls on MSRT.  It hadn’t been used/updated since mid year, and the 5 updates selected apparently installed without problems.

The above MSRT problem on my old Dell desktop showed error code 80024001E when it failed, but as indicated above I could not find any specific details about this error; only general details about WU update problems.  I will wait for the January MSRT to see what happens.

Thanks geekdom.  That option is good to know.  Next time I am in that machine I will check it out.

Thanks rick41.  Sorry about my quick vague post.  The updating process seemed to just stop after the first update was complete, while it was apparently attempting the MSRT update.  I assume this because when I cancelled the updating and rebooted and checked for installed updates it showed the first update as successful and the MSRT as failed.  There was an error code (can’t remember what it was and I’m not at home now), which did not show anything specific to MSRT in a google search.

Before cancelling and rebooting I had waited for at least half an hour, maybe more (not sure exactly as I was doing the other two machines at the same time).  I also checked the task manager, and it showed the WU process as running, but the actual process CPU time was almost non-existent, showing 0% most of the time.  The machine had not locked up, and seemed to be working normally.   In the past just clicking in and out of various open windows would jolt things into responding again, but not this time, and I assumed the updating had just stopped.

If manually running MSRT as above doesn’t work, I won’t bother with System Restore, as my past experience (in XP days) was that it would usually come back telling me it could not restore to the point I wanted anyway.  I’m happy to wait until next month’s version of MSRT.

G’day folks

I was able to successfully Group A update a HP15 laptop with Win 8.1, and a Toshiba laptop with Win 7 (both 64 bit) with all December WU patches and Office 365 patches, but my old 32 bit Dell Dimension 4600 desktop completed the .NET update and then just stalled after trying to install the December MSRT.  I restarted and tried again, and it completed the other 2 WU updates but marked the MSRT as failed.  I could not find the MSRT in the list of updates to remove (unsurprisingly), but it would not appear as an option in WU anymore, to download again.

Is there any way for me to get it back?  Does it really matter that much?

1 user thanked author for this post.

jburk07

G’day folks

I am curious about how this timing works as well.  Does the 15 days calculate for any update from its first date of presentation?  Are the updates time stamped, or does the individual computer note and start counting from when it sees each particular update?

Cheers

Thanks geekdom

If power corrupts, I guess it is possible that the power to pull information from our machines has influenced MS to slide from sloppiness, penny pinching on quality assurance to outright clandestine malevolence.  Although possible, I suspect/hope it is unlikely.

Has the telemetry been shown to affect performance?  I guess it clearly does facilitate their ability to thwart our attempts to thwart them.

2 users thanked author for this post.

jburk07, Cybertooth

Thanks PKCano
That thread seems to be saying the telemetry is now unavoidable if I stick to monthly rollups.  I presume the separate telemetry KBs won’t be presented anymore in future.

The thread also suggests ways to avoid telemetry (Group B, scripts/manual eradication and alternate OSes).  My question was more about what the downsides of telemetry really are.  I remember some association with the GWX saga in the past, but not much else.  I presume the possibility of easier manipulation of my machine  by MS and/or performance drag are the most obvious downsides, but wonder how bad these really are, and if there are other reasons to avoid the telemetry?

Sorry, this may be obvious to most here, but I seem to have lost track of it.  If there is no quick and easy link you can point me to, don’t waste any of your valuable time on writing an explanation.  I doubt I will want to experiment with anything other than Group A processes.

1 user thanked author for this post.

jburk07