Announcing Windows 10 Insider Slow Build 17025 for PC Insider

   Warning

Let's keep this discussion friendly shall we.

Brink said:

   Warning

Let's keep this discussion friendly shall we.

Truly noted.

larc919 said:

We don't normally get new builds on Monday. I think Dona and crew need Mondays to recover from their weekends.

She's recovering nicely, in Lisbon!

fjk61011 said:

Attachment 162477

Yes, I got the same thing today - download adobe flash followed by signature issue, then followed by everything up to date.

Brink said:

   Warning

Let's keep this discussion friendly shall we.

Sure. I'm always friendly and courtesous.

I've now done about 30 image captures since Saturday both on physical and virtual machines. Those, and the tests some of your geeks kindly made at my request do not answer the question I was mostly interested in: how predictable is the time required?

Logically thinking, the better the hardware performance, the faster it is to capture the image when captured installation is about the same size, but in reality the same process on same hardware varies. For instance in my own tests using same conditions and same VM, capture time when checking integrity and verifying captured image was anything between 24 and 45 minutes. Same process, same VM, same conditions (on host machine nothing else going on).

One question that is answered is the image size, it will in most cases be between 30 and 40 percent of the size of captured Windows installation. Less installed software and more captured user data > image will be closer to 30%, less user data and more installed software > closer to 40%.

Lot of other questions I had on my mind still unanswered, need to capture some more images :)

I will continue testing. Thanks geeks for proving valuable information.

Kari

Here's the end of my testing Kari dism capture-image command. It is in fact a simple command but bash does not use the : delimiter (but I could, as always, be wrong about that. The most interesting thing to me about this unappreciated work is the DISKPART outcome. The command took roughly 30 minutes to complete but as others have said some of the switches could be eliminated. No 3rd-party software was installed on the Hyper-V machine. The install.wim file is as it may be in this environment. I will search for a DISKPART tutorial on this forum and if none is available I'll think about writing assume Kari hasn't one handy. It been a pleasure to help you

This discussion of file manager was illuminating. But I've purchased xplorer^2 pro lifetime upgrades for 69 bucks. I can now retire Total Commander from my dock (naturally I'm keeping that program - it has many, many useful add-ons available and is a great program)