XPost: uk.d-i-y
From: nospam@needed.invalid
On Thu, 4/3/2025 11:11 AM, Andrew wrote:
> On 03/04/2025 09:49, David Wade wrote:
>> On 02/04/2025 21:41, Jeff Gaines wrote:
>>> On 02/04/2025 in message Andrew wrote:
>>>
>>>> I have Win 10 Pro and it simply notifies me that Updates are
>>>> available and I choose to download them. I must have set up
>>>> something on Win7 Pro that I upgraded from, because I don't
>>>> recollect making this choice on Win 10.
>>>
>>
>> Are are you sure it doesn't download major updates, its just the optional
it prompts for.
>>
>
> No, the notification says "You need some updates". I click on it
> and the Windows update page appears showing whatever patch tuesday
> updates are available, plus the daily "you have installed something
> we don't like" update, and below is an optional "quality" update
> which I ignore
>
> Putting "updates" into the search box and selecting "Windows Update
> Settings" puts me into the main Windows Update page, where I can
> see "view configured update policies" and clicking on this shows
> a page with the text "Wondering why you're seeing 'Some settings are
> managed by your organisation" (which shows at the top of the main
> Windows Update page).
>
> Then under "Policies set on your device" I see -
> Notify to download updates
> Source:Administrator
> Type:Group Policy
>
> Set Automatic Update Options
> Source:Administrator
> Type:Group Policy
>
> On the right of the screen is a link to learn how Windows
> Group Policies manage updates, which gives this page -
>
> https://learn.microsoft.com/en-us/windows/deployment/update/waas-wu-settings
>
> Scroll down this page to "Configuring Automatic Updates by using Group
Policy" and this looks like how you alter the way updates are downloaded
> and installed
>
> Hope this helps
>
> Andrew
Updates are put into batches and given a monthly stamp.
This may have been intended at one time, to improve the performance
of the Windows Update installation process, which had a huge preamble
as the update process computed which update supersedes which other update.
Even the Jumbo packing mechanism is causing problems for Windows Update,
and the scan time can be pretty long now (a scan happens before an Update
can come in).
They can be on the order of 600MB to 700MB, if downloaded from c
talog.update.microsoft.com .
The Catalog entries are "Cumulative", except when they aren't Cumulative and
other
older patches insist on installing after a later one is installed. the patches
can
contain Servicing Stack Updates, and those gate later patches.
While there is some sort of scheme to only download the parts of it not on the
machine (delta method),
I don't know relative numbers for that. Getting the update through Windows
Update
and not downloading an executable .msu file, might only take 200MB.
In the WinXP era, a Security Update could be 2MB to 3MB, and orders of
magnitude
smaller than the jumbo things that come in now.
Other patching activity is happening constantly. MSEdge checks once per hour
for updates.
Metro.Apps, you can see in the Reliability Monitor, entries corresponding to
them
being updated. Telemetry is uploaded in batches (at relatively low rate). Typed
URLs are being sent to Vortex. It's a busy busy heap of steaming trash.
Some day soon, CoPilot.App may need to be removed. A capability to "watch your
screen"
is being added (not "Recall", a new feature). The CoPilot.App is not
absolutely required,
as the upper-right corner of MSEdge browser has an icon, and you can still ask
questions
(without the machine having access to your screen). The topic of CoPilot
"Helping run your machine",
is fraught with peril. For example, say that CoPilot knows what the "del"
command does. Is that a good thing ? :-/ It would be like a Self Driving
Chainsaw.
Paul
--- SoupGate-DOS v1.05
* Origin: you cannot sedate... all the things you hate (1:229/2)
|
