|
Here's a tip for when you're dealing with the tech giants:
If you see anything that is even remotely suspicious, Exit!
I'd suggest deleting your insider account, so that they can no longer do whatever it is that they're doing to you.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Is it distributing the download among as many threads as it can?
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I wouldn't know to verify that. Nor is it likely that you can change it and do anything about it.
|
|
|
|
|
I think you can look in the task manager and see how many threads that process has active.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I have no idea what the process would be in this case. It's not the good ol' wuauclt.exe, I know that much...
|
|
|
|
|
In the task manager you can add columns to show more information about processes including network usage and number of threads.
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
I/O reads and writes? I don't think these figures discriminate between local and network.
Besides...as already mentioned...I'm not trying to disable the update process; I just want it throttled. Is there even anything in Windows that would allow me to do that?
I've since realized the VM's network settings seem to provide some options. I'll poke around the next time it's trying to get an update.
|
|
|
|
|
likely instead of downloading large files/archives of files (zips etc) it's downloading (or merely checking/requesting) lots of [small] individual files. yes tcp is good streaming bulk data but sub-optimal with many many small packets (you know, packets are small but each still having the same sized headers, other paraphernalia as well as req/ack/nack handling)
in a way same concept as DDS attacks, lots of tiny [including request-answer] packets (in both directions) does way more damage than a huge file transfer.
then the connection: fibre, cable and even wi-fi although fast it's only half duplex
...again all them tiny rapid fire reqs, acks and nacks generated at your machine (= zero latency) holding up the remote [hence latency delayed] incoming packets
- lots of carnage, and after the cleanup that who gets to try again soonest [and most often]...
Message Signature
(Click to edit ->)
|
|
|
|
|
That's an interesting thought...even though most of the Win10 installer is in a single large .WIM file, in the case of Insider updates, it may very well be using an entirely different mechanism.
And now that you mention it, the VS 2017 updates (which consist of thousands of small files) tends to affect my network availability in more or less the same fashion. You may be on to something.
Downloading only the bits you need generally make sense if you're only trying to update a system or two, but I'm still a fan of having a single downloadable ISO.
|
|
|
|
|
did u disable the peer to peer update thing in windows update..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Yes. But even if I hadn't, none of my other systems would have any of the files an Insider build would want or need.
I use WSUS to update my systems - but I have the Insider VM query Windows Update directly every once in a while--that's how it can determine there's something available (newer Insider builds don't come through WSUS)
|
|
|
|
|
u can use tcpview / fiddler / microsoft network monitor etc to see what services are sending out data and disable them from the services or registry and also block ms in host file. i assume insider builds will be leaking telemetry like the mars rover...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
I don't want to neuter the thing. I just want it to leave my network in a usable state when it's downloading updates. As mentioned in my original post, it's the only thing I have that manages to totally hog my bandwidth when it downloads updates and leaves nothing for other systems while it's doing that.
abmv wrote: i assume insider builds will be leaking telemetry like the mars rover...
As an Insider build, it wouldn't be doing its job if it wasn't doing just that. It's running as a standalone VM that I barely use other than to test my own apps against, every once in a while.
|
|
|
|
|
Just like we can create checkpoints & restore Windows to an older state, this is possible on Linux(ubuntu server)?
For example, I'm installing a bunch of packages, all of a sudden I suspect I installed the wrong versions in between. And there's a pile of them. Instead of checking one by one, will it be possible to just clean wipe all the installations and take it back to the orginal state? Like maybe creating a checkpoint and then getting back there if something went wrong.
|
|
|
|
|
There is nothing similar to what you have in Windows (a lot will explain you why it is unnecessary in Linux)...
There are several tools however to do that: 10 Easy Ways to Restore Your Linux System[^]
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
|
|
|
|
|
thanks , checking it out. 
|
|
|
|
|
Good read thanks!
Give me coffee to change the things I can and wine to accept the things I cannot!
JaxCoder.com
|
|
|
|
|
If you root you can copy the entire file system over.
|
|
|
|
|
sounds easy, until you start running into symbolic links, devices, named pipes, temp filesystems and you've got dbus some of their newfangled thingymawatsits. ...ends up being a mess of of command line options for this or that.
not that it can't be done, get it right and create a script.
but yes can be done: in fact did it to clone an entire setup onto backup [different config] hardware - something windows definitely can't do. Cloned the SSD, unplug from source, plug into dest, boot... done. (just change the system name if you want to talk to it over a network.)
Message Signature
(Click to edit ->)
|
|
|
|
|
I've cloned the disks in windows to different hardware.
It's a pain, but the process was load over the required drivers for the new hardware.
Installable, but NOT installed.
Clone the drive. Put the clone in the different hardware machine, boot into safe mode without networking.
get the monitor/keyboard/mouse drivers first. Generics usually work at first.
reboot normally.
Apply all of the drivers specific to this machine.
After about 10 reboots. You are pretty much good as gold.
Now, deal with all of the software/copy protection like QuickBOoks, etc.
That recognize the drive changed, or the CPU changed or the core hardware changed.
Back in the day WINNT, we did this in order to upgrade developers computers without reinstalling everything. Probably did this about 30 times.
Anything that causes a crash just requires safe mode boot, installed the new hardware driver, and delete the old one.
USB and Networking are the single biggest nightmares. And nowadays the entire Mainboard and subsystems.
|
|
|
|
|
One word: Virtualization.
Checkpoint management isn't the responsibility of the OS, so that'll remain consistent regardless of what OS you're hosting.
Obviously whether that's the right solution for you is for you to decide.
|
|
|
|
|
usually if it is a decent software u are installing on linux or unix they give u a sh file to remove or uninstall the s/w ..if u are running linux on hyper-v or vmware u can do a snapshot also..
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
Serves you right for not using the Best! Windows! EVAH!
I'll be joining you, in a few months, but my network is so damned complicated that I'm having to try rebuilding it using VMs and spare boxes, first.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Timeshift is your friend. Can work like Time Machine on that other brand. It can undo a major upgrade or minor changes, very configurable.
Lou
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
|
|
|
|
|
This is something that'll vary between Linux distros, since there's a lot of variation in what they include and how their package managers operate.
It sounds like NixOS might be what you're looking for. If you apply a bunch of updates and and something goes wrong, you can just roll them all back and end up in the state you were at before.
You can also use Nix as your package manager on other Linux distributions, but I've never tried it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
