My 21H1 Win 10 Pro PC has an old ESD ISO mounted as a virtual drive. It won't eject. SYSTEM therefore has the file open and not able to delete. Nearly 5GB is a lot of space to waste. I confirmed that I didn't have it mounted in VirtualBox. How can I eject the virtual drive and then delete the file? FWIW, the file is Windows20h2-iso-file.iso.
Thanks!
Eject is ghosted out. You can't eject while a process has a file open. What I don't understand is why an ISO I haven't needed in a long time would be opened by the SYSTEM process. I'm a couple versions of Win 10 past the one in question. And the last time I used an ISO that I can remember was to setup a virtual machine - but Virtual Box is not running nor does it refer to that ISO.
Try in Safe Mode.
You could also try Unlock IT to see what process has the mounted image... open.
UnLock IT Free - Unlock a File or Folder Locked by the System
You are probably right, but why would that process have the file mounted and open in the first place? My concern is that there is something going on that I can't see, and that if I could unmount it in Safe Mode I might do some harm.
One oddity - Microsoft says that you should be able to see a virtual drive in Disk Management, but this does not show.
https://docs.microsoft.com/en-us/win...ual-hard-disks
So Unlock It does show H:\ (CD Drive) as locked. Not the file itself, though when you try to delete the file, it can't.
I did 'check', then UI says it's not locked, but it really still is.
I'd sure like to know how and why Windows has it mounted - but not visible in DM, nor is H: visible in DM. BUT - you can click in Explorer on H: and see the contents.
I would go into Safe Mode, and try to eject/delete the ISO.
Then grab a different ISO and see if the problem repeats.
It doesn't really make sense to attempt to troubleshoot WHY it happened, unless we know it happens with ALL ISOs.
IF it only happens with this one ISO, then the problem may just be the ISO itself.
If this happens with ALL ISOs, then we can try to find out... WHY.
Quote
