Windoze updates
-
My condolences, @JonB.
Hours of downtime doesn't sound right though, even for a major update.
- Is your VM hosted on a spinning hard drive? If so, moving it to an SSD will do wonders.
- Make sure that both your host and your VM aren't running out of memory. If they do, your machine will waste lots of time shuffling data between your RAM and your pagefile/swapfile instead of doing useful work.
-
@koahnig said in Windoze updates:
More on the serious side since you are using a VM you should be able to use the PC otherwise e.g. posting here.
But I have nothing else to do (hence I typed in this grump), I'm trying to commission it so i can do the work I need to do on it. So I have to wait till it's fully finished. That's the point!
@JKSH said in Windoze updates:
Is your VM hosted on a spinning hard drive? If so, moving it to an SSD will do wonders.
Make sure that both your host and your VM aren't running out of memory.
It's a full (ESXi) server, hosting VMs. No others on it. Not doing anything else. Good CPU, cores, plenty of memory. I can't move its storage to SSD!
Trust me, my box is not slow! The amount of Windows updates, and the time whatever they seem to do to apply, is the issue.
I think what happened was the first day it applied updates to the Win 10 version it had. (Example: Windows update stuck at 58% for like 6 hours, it completed overnight...) Then it decided that version of Win 10 was out-of-date, and today it has been upgrading to the current "feature" one (20H2). Rather than deciding to do that before updating everything in the old, installed one. Nice one, Microsoft! ;-)
Anyways.... It has finally settled down now, so I can use it. Doesn't stop me being irritated.... :)
-
@JonB said in Windoze updates:
Anyways.... It has finally settled down now, so I can use it.
πππ
-
I "suspect" that M$ recognizes that you are running windoze in a VM and strangles it on purpose. IIRC, I once read an EULA from M$ that forbid the running of windoze in a VM, unless specifically a version licensed to do so. Silly license games: another reason I shun M$.
-
@Kent-Dorfman
I'm about to abandon the VM, and install Win as base. Which will mean... ...reinstalling Win 10 and waiting for it to update, again! -
Which version are you starting with? Something old? You can create an installation media of the latest version (20H2) with all the updates and install from that. Should be a lot faster than installing old version and updating one by one.
-
@Chris-Kawa
ESXi was an experiment. It doesn't like USB drives, nor NTFS. I don't like it. I intend to wipe it. :). -
@JonB said in Windoze updates:
I can't move its storage to SSD!
Just to confirm: Is the physical storage medium a spinning hard drive? If so, that's definitely your main bottleneck. Doesn't matter how good your CPU/RAM/motherboard/networking is.
@Kent-Dorfman said in Windoze updates:
IIRC, I once read an EULA from M$ that forbid the running of windoze in a VM
Do you have a source for that?
Microsoft provides tidy VM bundles for developers who want to use Windows under a hypervisor of their choice: https://developer.microsoft.com/en-us/windows/downloads/virtual-machines/
-
Hi
If you start with old a version like 1803 you will get those
huge feature updates that takes ages to install.As comparison, using an iso with the latest version it takes like 15 min in the WMWARE workstation to install.
-
@mrjj said in Windoze updates:
As comparison, using an iso with the latest version it takes like 15 min in the WMWARE workstation to install.
Plus the 5 minutes or so to download it ... I'd say going to MS's site and clicking the button is worth it ...
-
The last huge Windows 10 Update neutered Cortana. She is not as smart as she used to be. And, some tech partners didn't get licenses renewed with Microsoft. So cut ties were done.
Cortana does not integrate with iHeart Radio anymore. Each Windows 10 update, I seem to use Cortana less and less. Looking at Google TTS now.
-
As the OP, just to sum up.
Yes I have a hard disk. Yes I/O is a computer bottleneck. Yes SSD would be faster. But I have a hard disk. And it's not an old-spec machine.
My Win 10 comes from download from the MS Partner Network my company pays for. Along with other Win Server OSes, Office, etc. etc. That's where I am sticking to. I don't know which Win 10 version number it is. I would expect it to be rather/fully up-to-date, that's all I know.
None of this seems to me terribly relevant to the moan I am making. I have been installing & upgrading Win machines for years (and years). I have often had days after installing where they keep fetching upgrades.
This time one of the upgrades took > 6 hours. I left the machine overnight, expecting it to not-complete and planning to reboot the next day, but it had finished. I would say with other upgrades it took maybe >10 hours.
The machine has nothing but a vanilla-installed Win 10 on it. It didn't take anywhere near 10 hours to install originally. I just don't get what the upgrade is actually doing which could possibly make it take that long. If it read and wrote every byte in every file on the disk it shouldn't take that long. It's ridiculous.
-
@JonB said in Windoze updates:
I don't know which Win 10 version number it is. I would expect it to be rather/fully up-to-date, that's all I know.
Worth making that sure before it starts updating. There should be no or very few minor updates (often not even requiring a restart) on an up to date image.
I just don't get what the upgrade is actually doing which could possibly make it take that long. If it read and wrote every byte in every file on the disk it shouldn't take that long. It's ridiculous.
Considering it's not my (or others as noted) experience at all, there's something specific to your case that makes it so painful. If you have an MS Partner account maybe that's something worth taking up with your MS liaison to investigate? Or with you IT department if you have one? Maybe the connection to the update server is so terrible or the resources there not up to date.
-
@Chris-Kawa
I decided to go take a look. It is:SW_DVD9_Win_10_1909_64BIT_English_HomeProEDUSLS_N_OEM_X22-15306.ISO
So 1909. That's what they offer currently. That's all I can say.
there's something specific to your case that makes it so painful.
I have done many installs/upgrades. Some aren't too long. But many do take a long time per each upgrade they apply.
If you have an MS Partner account maybe that's something worth taking up with your MS liaison to investigate?
LOL, no! :)
Or with you IT department if you have one?
That would be... me! :)
Maybe the connection to the update server is so terrible
It's not the download time (which is good). It's the apply-the-update. And always has been.
WAIT, UPDATE:
When I click download it gives me 4 links. None of them are "labelled" to say what they are --- just "Windows 10 Download". I took them to be mirrors. I clicked the first one. I just tried the 4th one. To my surprise that is:SW_DVD9_Win_10_20H2_64BIT_English_Home_Pro_SL_S_N_OEM_3_X22-47514.ISO
That looks like 20H2 instead of 1909, not that it says anywhere, or tells you about it. Thanks, Microsoft! OK, presumably that should be an improvement for next time....
Now, as per the moan, I'd still be interested to hear what you think MS Win 10 upgrade actually does which takes quite so long? :)
-
@JonB said in Windoze updates:
Now, as per the moan, I'd still be interested to hear what you think MS Win 10 upgrade actually does which takes quite so long? :)
looking at the issues with KB4592438, I would say, formatting your hard drive takes a while....
-
@JonB well that particular update only causes issues if your run chkdsk and try to auto repair any dmk,
but its not unheard of
-
@JonB
If there is developer mode enabled with windows insider program Then you will get updates regularly and takes much time too.
Before I hadn't enabled developer mode and not joined windozπ insider The updates takes much less time. And updates use to come slower than now