Please provide your feedback in this short Flings' survey.
Nov 20, 2022

Why does the imager create a VM with an NVME controller and an E1000E network adapter instead of the recommended
VMware Paravirtual SCSI controller and a VMXNET3 adapter?
I also see 2 USB controllers - one standard controller and one xHCI.
Are there legitimate reasons for this hardware configuration?

Nov 21, 2022

Regarding the the selection of network controller, this hasn't been raised before so probably something just overlooked or not considered. Best explanation I have are NVME and E1000E are defaults in Workstation for new VMs and when adding new adapters. I can appreciate this might not be optimal however - I'll have a closer look.
Also the USB controller configuration is boilerplate, matching what you get on a new VM created in Workstation.

Nov 18, 2022

I have a feature Request:
The possibility of exporting the VM in any state as OVF, i.e. even if OSOT has not yet run or Sysprep has not yet been done.

Nov 21, 2022

Tom, your feature request is well timed. OVF export on VMs imaged to any stage will be available in the next release, which is due in the next few weeks.

Nov 04, 2022

For anyone trying this on a nested virtual machine, vSphere/ESXI 7.x, running Windows 21H2 Enterprise LTSC, make sure you install Microsoft Edge Web View Runtime or an "application not responding" will present itself within the task manager and the application will not open.

Ben made a similar comment below. It should probably be mentioned as a "system requirement" as it might save some folks troubleshooting time. I almost gave up on the application. It is running now and I am testing my first image. Also, I did what Ben did and made the registry change in advance, not sure it was necessary in my case.

Hopefully it works. Thanks to the developers!

Nov 04, 2022

Short lived. I got an error "C:\Users\%username%\AppData\Local\VMware\Imager\cache\adksetup.exe" failed to run with exit code 15605. I'll see what that is all about.

Nov 04, 2022

The problem, at least for me, was Windows ADK not downloading and installing (automatically). I had to manually install those, based on my Windows Version, which is Windows 10 21H2 Enterprise, but afterward it worked.

So, ultimately I installed Edge View Runtime, Windows ADK manually. I imagine on a newer, Windows 11 environment this might not be necessary.

Nov 06, 2022

Thanks AlmostIT for persisting through these problems and the feedback! I will look into getting a proper fix to the Edge View runtime issue and will update the system requirements as you suggested.
Googling the adksetup 15605 exit code, this seems specifically a download failure from the Microsoft site. I would like to take a closer look as not something we have encountered before. Can you please share the imagertoolw log file (under %LOCALAPPDATA%\VMware\Imager\logs) to: ws1labsImager@vmware.com, which is a direct channel to our dev team.

Aug 09, 2022

I keep failing on Prepare, just keep getting Failed to create customized Windows PE ISO.

Nov 02, 2022

We were finally able to reproduce this on the Imager 2.0 release. The Windows PE ISO will fail to build if Imager is run from a UNC share, with a warning in the log file (under %LOCALAPPDATA%\VMware\Imager\logs) similar to:

[WRN] '\\machine\share'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.

A fix is planned for the next release. For now the workaround is to simply don't run from a UNC share. Mapped drives seem to work fine.

Aug 09, 2022

Thanks for reporting this, we will look into it. Can you please share the imagertoolw log file - this is under %localappdata%\VMware\Imager\logs.

Aug 10, 2022

Thanks Paul, just upload the logs here?

Aug 10, 2022

I suggest posting a section of the log file that looks relevant to the problem here in the comments. Unfortunately the Flings site does not have any other useful way to share files.