Announcing Windows 10 Insider Slow Build 17025 for PC Insider

JUst started the Saving Image. I will capture the screen when its complete as well as a dir c:\image. Then I can boot off the HD and export from the System Information Utility - however I can't see any extention except .txt. Is there another way to format the output from System Information or is a text file acceptable - 13% now.

The only information I'm interested in is how long it took to capture the image, C: drive used space on VM you captured, size of captured install.wim file, processor on host, and if VM is on SSD or HDD.

That's enough to do some comparison.

Kari said:

The only information I'm interested in is how long it took to capture the image, C: drive used space on VM you captured, size of captured install.wim file, processor on host, and if VM is on SSD or HDD.

That's enough to do some comparison.

Host CPU AMD FX(tm)-6100 Six-Core Processor VM is stored on a 1TB Segate Spinner. I'll rename this VM Kari and can reserve it for more tests if you wish. I will join it to a Insider MSA so I can get Fast Ring updates. Process took ~ 33 minutes but of course I was doing other stuff.

Cheers. Good luck with the new tut

martyfelker said:

Host CPU AMD FX(tm)-6100 Six-Core Processor VM is stored on a 1TB Segate Spinner.

@martyfelker, your captured image is about 4.7 GB (bytes converted to GB). How big was the installation (used space on C:) from which image was captured?

If you didn't check it before starting, just boot to desktop and check size in C: properties, start size was the size shown minus image size 4.7 GB (C: now contains the captured image, too).

Damn. Deleted the VM by accident. It's on an ext4 filesystem and certainly not worth the effort of recovery. However the created size of the VM was 32 GB and pagefile.sys and swapfile.sys to about 1/2GB (2048MB RAM). The Windows installation was approx 20GB so there would be about 7-8 GB left after the install.wim image. No matter - I really was creating the VM in order to upload to my ESXi 6.5 VM which already has Debian, Fedora, Tumbleweed, and Kubuntu at the latest versions.

BTW I really don't need to be tutored on using the File Manager dude. And a thank you would be nice,

martyfelker said:

BTW I really don't need to be tutored on using the File Manager dude. And a thank you would be nice,

⚠️[emoji848]

martyfelker said:

BTW I really don't need to be tutored on using the File Manager dude. And a thank you would be nice,

Let's start with this: I am not dude to you, and you do not have any reasons to be rude.

Next: you would have received my thanks, of course. Check my posts throughout Ten Forums, always when I have asked fellow members to check something for me, I have thanked them. Always. Our matter was not finished, before the thanks there was one crucial part of information missing, the size of Windows installation. I asked it and remained online awaiting your answer although it's already almost 2 AM here.

About you not needing instructions to use File Manager, let me start by saying that I didn't give any advice. I just explained an easily overlooked fact, that if you checked the installation size after the image was captured you should deduct size of the image of total size.

Having said that, judging by how difficult it seemed to be for you to enter a simple command correctly I thought it would only be polite if I explained how to calculate the installation size.

Thank you.

Kari

I'll just hold my tongue. You got the data you wanted and I'm finished. No doubt you yourself never have any typing errors (because that's what they were) - especially after you've hoisted a few. I even thanked you for telling me about Shift+F10. Bah!

Attached are the screens showing the execution of the command from a command prompt and the before and after virtual disk properties. There is nothing but the software from the install (i.e. pure Microsoft) The host is Windows Server 2016 and its running VMware WS 12.5.7. The VM is in a Shared ESXIi 6.5 VM. Any more questions?