VMware Communities
emmav674
Contributor
Contributor

VMWare workstation does not release handles creating an iso

Hello,

I have this problem: I use Workstation Pro 14.1.1 build-7528167 with Windows 10 Enterprise LTSB to develop embedded solution with Windows Kit and I use oscdimg in order to create isos of embedded S.O.

In order to be able to create a bootable USB key, I have to shutdown completely Workstation (not only the VM).

These are the steps to reproduce the problem:

Install Windows ADK, then launch with administrator privileges:

cd c:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\amd64\Oscdimg

oscdimg.exe -u2 -o -b"X:\W10IoT\boot\etfsboot.com" "X:\W10IoT" "X:\ISOs\myiso.iso"

If you try to create a bootable disk with that ISO, it remains hooked by VMWare till you shutdown it.

There is a workaround because I generate a lot of iso during developing and this very annoying..

By the way, with other virtualization platform, no problem at all

Reply
0 Kudos
4 Replies
continuum
Immortal
Immortal

Lets see if I get this right:
1.you create the ISO using your hostOS
2. you then use this from a VM
3. you then try to disconnect this ISO from the VM and fail to disconnect it.
Right ?
Try this ugly workaround:

1.you create the ISO using your hostOS

2. you then use this from a VM
3. disconnect ISO from VM
4.assign other ISO or a physical device to that VM
5. let VM actively read the newly assigned ISO/device
6. now your original ISO should be unlocked


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
emmav674
Contributor
Contributor

1. I create the ISO using VM

2. I use the iso from the hostOS (with rufus I write it on a usb stick)

I do not connect the iso in any way, or touch it, or do anything else on the created iso on the VM. Simply I create it directly throu vmware shared folder

Reply
0 Kudos
continuum
Immortal
Immortal

Ok
that was the missing piece.
Simply do NOT use VMware shared folders.
Create a standard windows share instead = problem solved.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

Reply
0 Kudos
emmav674
Contributor
Contributor

I have to use shared folders.. not enough space unfortunately

Reply
0 Kudos