XPost: alt.comp.os.windows-11

Another curiosity question. Posted to win10, but also win11, because I
know that's where the people with money are.

I have RadioMaximus on the desktop with win10Pro, and the laptop with win10Home. Both connected by cable to the same Verizon router, but one
will update (took 2 minutes) and the other still hasn't started its
download. How can they act so differently? I know the problem one is connected to the net because it's playing music, the whole time.

Moderately old version, same version in each. I use the in-program
update, amd on the laptop the download starts immediatelly, finishes in
10 seconds, closes the program, installs the update in probably under a
minute.

In the desktop, a minute later, the download stage starts immediately
but the progress bar never shows up, and it still says Downloading....
20 minutes later. Cancelled the download and restarted. Closed the
download window, and reopened. Closed the program and restarted program
and download, Looks the same every time.

What possible reasons it could be so different between the two computer

And do you really think it will make a difference to restart Windows?
... Tried that. Didn't help

I know I can go to the webpage and download there, but I'd like to
understand the foibles of data processing. ??????


Yes, dl'ing there went smoothly and quickly. And so did installing.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

XPost: alt.comp.os.windows-11

On Mon, 11/25/2024 9:15 PM, micky wrote:

Another curiosity question. Posted to win10, but also win11, because I
know that's where the people with money are.

I have RadioMaximus on the desktop with win10Pro, and the laptop with win10Home. Both connected by cable to the same Verizon router, but one
will update (took 2 minutes) and the other still hasn't started its
download. How can they act so differently? I know the problem one is connected to the net because it's playing music, the whole time.

Moderately old version, same version in each. I use the in-program
update, amd on the laptop the download starts immediatelly, finishes in
10 seconds, closes the program, installs the update in probably under a minute.

In the desktop, a minute later, the download stage starts immediately
but the progress bar never shows up, and it still says Downloading....
20 minutes later. Cancelled the download and restarted. Closed the
download window, and reopened. Closed the program and restarted program
and download, Looks the same every time.

What possible reasons it could be so different between the two computer

And do you really think it will make a difference to restart Windows?
... Tried that. Didn't help

I know I can go to the webpage and download there, but I'd like to
understand the foibles of data processing. ??????

Yes, dl'ing there went smoothly and quickly. And so did installing.

Considering there is a free upgrade from W10 to W11, and
Rufus is available to bypass some of the requirements,
I don't think having W11 implies "having money".

Now, if you're referring to people "buying things because they are shiny",
we don't have too many of those people here. There aren't any jewel encrusted Android phones here. Or pink-colored PCs (there are such things, maybe you
will luck out and find one on the curb).

One of the computer shops here, that went broke, it had a cool scam.
You would go into the computer store, looking for a PC case. Five
minutes later, a "customer" would come in, a quite effusive gentleman
(not a teenager). He would start looking at the fire engine red
"Fire Engine" computer case. He would claim in a loud voice
that "he had to have it". I'm looking at this and thinking
"give me a fucking break" :-) Yes, older gentlemen go for
Fire Engine shaped PC cases -- obviously this is a thing, right ?

*******

The web site does not delve into anything technical.

Here are some possibilities:

1) Station listing update (a small file)

2) Program executable update
a) Using incremental method (Firefox and Thunderbird do this)
b) Using "full" image files (a larger download)

The program could also collect usage data, but that would be
a relatively small transaction.

Maybe the programs are not doing the same type, at the same time.

Some softwares, they have a scheduler. The developer arranges
each machine to connect to the server at a different hour,
spreading out the load on the server.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Mon, 25 Nov 2024 21:15:40 -0500, micky <NONONOmisc07@fmguy.com>
wrote:

Another curiosity question. Posted to win10, but also win11, because I
know that's where the people with money are.

I have RadioMaximus on the desktop with win10Pro, and the laptop with >win10Home. Both connected by cable to the same Verizon router, but one
will update (took 2 minutes) and the other still hasn't started its
download. How can they act so differently? I know the problem one is >connected to the net because it's playing music, the whole time.

Moderately old version, same version in each. I use the in-program
update, amd on the laptop the download starts immediatelly, finishes in
10 seconds, closes the program, installs the update in probably under a >minute.

In the desktop, a minute later, the download stage starts immediately
but the progress bar never shows up, and it still says Downloading....
20 minutes later. Cancelled the download and restarted. Closed the
download window, and reopened. Closed the program and restarted program
and download, Looks the same every time.

What possible reasons it could be so different between the two computer

And do you really think it will make a difference to restart Windows?
... Tried that. Didn't help

I know I can go to the webpage and download there, but I'd like to
understand the foibles of data processing. ??????

Yes, dl'ing there went smoothly and quickly. And so did installing.

I had something similar happen to me as well with the latest updates
for windows 10. 3 different machines and they each waited for another
to finish before they started - ie comp1-3 were all started to do the
updates with 30 seconds of each other , and comp2 waited for comp1 to
finish and comp3 waited for comp2 to finish before starting there own downloads. First time I had seen this happen. Maybe Microsoft is
limiting by ip address as to how many connections you can have?

Me

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 11/26/2024 12:36 AM, james moffat wrote:

On Mon, 25 Nov 2024 21:15:40 -0500, micky <NONONOmisc07@fmguy.com>
wrote:

Another curiosity question. Posted to win10, but also win11, because I
know that's where the people with money are.

I have RadioMaximus on the desktop with win10Pro, and the laptop with
win10Home. Both connected by cable to the same Verizon router, but one
will update (took 2 minutes) and the other still hasn't started its
download. How can they act so differently? I know the problem one is
connected to the net because it's playing music, the whole time.

Moderately old version, same version in each. I use the in-program
update, amd on the laptop the download starts immediatelly, finishes in
10 seconds, closes the program, installs the update in probably under a
minute.

In the desktop, a minute later, the download stage starts immediately
but the progress bar never shows up, and it still says Downloading....
20 minutes later. Cancelled the download and restarted. Closed the
download window, and reopened. Closed the program and restarted program
and download, Looks the same every time.

What possible reasons it could be so different between the two computer

And do you really think it will make a difference to restart Windows?
... Tried that. Didn't help

I know I can go to the webpage and download there, but I'd like to
understand the foibles of data processing. ??????


Yes, dl'ing there went smoothly and quickly. And so did installing.

I had something similar happen to me as well with the latest updates
for windows 10. 3 different machines and they each waited for another
to finish before they started - ie comp1-3 were all started to do the
updates with 30 seconds of each other , and comp2 waited for comp1 to
finish and comp3 waited for comp2 to finish before starting there own downloads. First time I had seen this happen. Maybe Microsoft is
limiting by ip address as to how many connections you can have?

Me

You would have to research DoSVC and see if there is any coordinating behavior.

I try to update one machine, and if the DoSVC cache is big enough, it
can hold the updates for other machines to tap into. The other machines
have to select the

Settings : Windows Update L Delivery Optimization

Allow downloads from:

Devices on my local network <=== for the receiving machines (all machines
could be set this way)

A machine which is serving to other machines (based on the files it just downloaded
to do Patch Tuesday) might be in here. The cache is using presumably its default location,
and is not using the GPEDIT policy variable "DOModifycacheDrive".

# 2.4GB (not the zero bytes File Explorer says) on my Win10 install

C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\Cache

The control on a caching machine is demoed here. To do this manually (on Home), you have
to add DeliveryOptimization first, then add the policy you want to implement.

https://www.tenforums.com/tutorials/105373-change-delivery-optimization-cache-drive-updates-windows-10-a.html

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization
DOModifycacheDrive REG_SZ %SYSTEMDRIVE% # These two are examples of supported syntax
DOModifycacheDrive REG_SZ D:\DOCache
DOAbsoluteMaxCacheSize DWORD 10 # 10GB of space (now using 2.4)

I used GPEDIT.msc then pushed out the change with

gpupdate /force

and then the new registry entry appeared in that location. If you are on Home, you would use Regedit to set whatever you like.

But my experience so far, is the scheme is pretty fickle, and
one machine might get used, another machine not get used, as a source.
I don't really think these caches are corrupted or anything.

Paul

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2024-11-26 06:36, james moffat wrote:

On Mon, 25 Nov 2024 21:15:40 -0500, micky <NONONOmisc07@fmguy.com>
wrote:

I had something similar happen to me as well with the latest updates
for windows 10. 3 different machines and they each waited for another
to finish before they started - ie comp1-3 were all started to do the
updates with 30 seconds of each other , and comp2 waited for comp1 to
finish and comp3 waited for comp2 to finish before starting there own downloads. First time I had seen this happen. Maybe Microsoft is
limiting by ip address as to how many connections you can have?

No, they are collaborating. It is a feature.

--
Cheers, Carlos.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Tue, 26 Nov 2024 01:57:10 -0500, Paul <nospam@needed.invalid>
wrote:

You would have to research DoSVC and see if there is any coordinating behavior.

I try to update one machine, and if the DoSVC cache is big enough, it
can hold the updates for other machines to tap into. The other machines
have to select the

Settings : Windows Update L Delivery Optimization

Allow downloads from:

Devices on my local network <=== for the receiving machines (all machines
could be set this way)

A machine which is serving to other machines (based on the files it just downloaded
to do Patch Tuesday) might be in here. The cache is using presumably its default location,
and is not using the GPEDIT policy variable "DOModifycacheDrive".

# 2.4GB (not the zero bytes File Explorer says) on my Win10 install

C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Microsoft\Windows\DeliveryOptimization\Cache

The control on a caching machine is demoed here. To do this manually (on Home), you have
to add DeliveryOptimization first, then add the policy you want to implement.

https://www.tenforums.com/tutorials/105373-change-delivery-optimization-cache-drive-updates-windows-10-a.html

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DeliveryOptimization
DOModifycacheDrive REG_SZ %SYSTEMDRIVE% # These two are examples of supported syntax
DOModifycacheDrive REG_SZ D:\DOCache
DOAbsoluteMaxCacheSize DWORD 10 # 10GB of space (now using 2.4)

I used GPEDIT.msc then pushed out the change with

gpupdate /force

and then the new registry entry appeared in that location. If you are on Home, >you would use Regedit to set whatever you like.

But my experience so far, is the scheme is pretty fickle, and
one machine might get used, another machine not get used, as a source.
I don't really think these caches are corrupted or anything.

Paul

thanks for the info.Will be looking into this today.
Me

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)