Getting an unknown error when unmounting image

[MadsBrockmannJuhl]

When I try to unmount a .wim, I'm getting this error:

Exception thrown: 'System.ComponentModel.Win32Exception' in Microsoft.Wim.dll
An unhandled exception of type 'System.ComponentModel.Win32Exception' occurred in Microsoft.Wim.dll
Unknown error (0xc142010c)

How I've set it up is like this:

private void UnmountWim()
{
    WimgApi.RegisterLogFile(@"C:\Temp\QuickWimLogs\UnmountWim.log");
    WimgApi.UnmountImage($@"{tBox_UnmountMountDir.Text}", $@"{tBox_UnmountCaptureDir.Text}", 1, true);           
}

The UnmountWim.log says the following:

[295648.303964] [0xc142010c] ImageRecaptureDirectory:(128)
[295648.303964] [0xc142010c] WIMCommitImageHandle:(1429)
[295648.303964] [0xc142010c] WIMUnmountImage:(2037)

I did notice, that if I change the commitChanges to false, then it would somewhat unmount the wim, meaning that the mount folder is empty, but the .wim is still mounted. I can see that when I open a CMD as admin and type in DISM /Get-MountedWimInfo:

Mounted images:

Mount Dir : C:\Temp\Mount1
Image File : C:\Temp\ADRevit2022\Application.wim
Image Index : 1
Mounted Read/Write : No
Status : Invalid

However, I'd like to be able to use the commitChanges to true.

Any help is appreciated!

[jeffkl]

@MadsBrockmannJuhl how are you mounting the image? I didn't find much on that error but one person reported that it was because the image was originally mounted as read-only: https://e3fi389.wordpress.com/2011/12/03/dism-unmount-and-clean-up-a-wim-image/#comment-962

[MadsBrockmannJuhl]

Hi
I found the issue to be when I have the folder open in File Explorer, then I get the issue - if I close File Explorer or just go one folder back, then it works fine without any issue.

So I guess there isn't a real issue after all! :)

[jeffkl]

Hi I found the issue to be when I have the folder open in File Explorer, then I get the issue - if I close File Explorer or just go one folder back, then it works fine without any issue.

So I guess there isn't a real issue after all! :)

Ah so an open handle to the mount directory would probably cause this since I think the WIMGAPI call tries to delete the folder or get exclusive access? You could probably incorporate some code in your API to determine if any process has an open handle to the folder before trying to unmount the image.