didn't mean to see this turn into a counting grains discussion over progress bar indicators ... ha ... sorry.
No worries, it's all good information that others will benefit from as well. I only chimed in to help...
my normal notion, set it and forget it for a while. when i come back if it's still not done, walk away again ...
I'm in the same mindset, although if a DL is taking longer than usual, it'll grab my attention. The only time I see DLs longer than 15-20 minutes is over VPN, which I've grown accustomed to. Even some taking over an hour, like India, or the Netherlands. I'm US.
the only thing that slower than expected download progress does is slightly wrinkle my backup routines. since i started using W10 inside of VMWare, i include the virtual machine file in my daily backups when VMWare is not running.
I use VMware Workstation all the time. I would suggest using a linked VM that you customize for a specific need. This way you need only backup the SOURCE image and not the linked cone... assuming it's not a complex setup.
The main benefit is that they are much smaller than a FULL clone and you can spin one up in just a few seconds when you want to create a new custom environment.
Try this:
- Create a fresh VM with the latest W10. You do not want to or need to activate it.
- Install VMware Tools, all Windows Updates, and then sysprep it (OOBE mode, Generalize unchecked, Shutdown). Do not generalize it. CTRL+SHIFT+F3 to boot into Audit Mode at User Account setup screen.
- Once it's shut down, create a LINKED clone. YT Video.
- Fire up the LINKED clone and create a snapshot; Name: post-LinkedClone; add comments in Description if needed.
- Customize your system as needed; create another snapshot; Name: post-customization. Add notes in the Description if needed.
Now, when you back up your SOURCE image, you only back it up once.
However, each time you create a LINKED clone from that SOURCE VM, you'll see a new locked snapshot in the SOURCE VM. You can back up the SOURCE VM again for times like this.
Your LINKED clone is the only thing that will change over usage. This one will be much smaller, making the backup process faster.
I have a LINKED clone that I use just for random experiments. I only fire it up when needed. When I'm done, I'll revert to my snapshot prior to my experiments. You still want to fire them up from time to time to keep them updated. Create a new snapshot afterwards, and delete the pervious one.
Linked Clones are amazing!
NOTE: You must not delete or move the SOURCE VM. If you do, the LINKED clone will not fire up until you fix the broken link to the SOURCE. Learn how to do that now, before you are in a situation where time is critical for you.
To keep the SOURCE VM updated, fire it up once every two months and run the updates, and then sysprep it the same way as before; not generalized. You can do this indefinitely as long as you do not generalize it. If you generalize an image, it can only be done three times.
If you know how to use an
Answer File, you can have it automate the OOBE setup for the LINKED clone to make the initial setup faster. You can use VMware's command line tool
vm run to copy the Answer File to the Windows LINKED VM folder structure so its there before you fire it up.
If my memory serves me correctly, the Answer file needs to copied to here:
C:\Windows\System32\Sysprep