Latest version - can't seem to load any WIM?

X

Xeno

New Member
Hi all, hoping this is something I am overlooking, but I have been using NTLite for quite a while.

I have an untouched ISO of 1909 English International (x64) and I can't mount the install.wim. I get an error right at the end of the process of loading that states that "there are no more files". Doesn't matter which edition I pick, Pro, Home etc.

Same error on Dell OEM images. Recently re-installed Windows on my machine, so it's a fresh NTLite install too.

Any suggestions? Logs suggest error "18", and oddly "123". Repeated attempts seem to change between these two.
 
Hi Xeno,

check these ideas for Error 18 under my reply. It is always a host issue, the antivirus protection in the very least, corrupted/wrong WIMGAPI engine at the most.

Let me know what you check and what it was if discovered.
 
No ADK installed etc - fresh windows install.

Turned off Windows Defender, no effect (it worked with it on before as well).
dll and sys files where they should be
changed my NTLite Temp/Scratch etc to a totally different drive just in case
Re-extracted from the ISO, and re-installed NTLite

Oddly after the above and several reboots, I now get a different error saying the WIM is corrupt. It isn't, as GimageX mounts it fine.

The fact the error has changed surely means it's something on my system, but I can't determine what :-/

This is now my logfile with error codes:

19/12/2019 20:35:00 - Gather image list 19/12/2019 20:35:00 Save settings 19/12/2019 20:35:00 Load image list 19/12/2019 20:35:03 - Gather image list 19/12/2019 20:35:03 Save settings 19/12/2019 20:35:03 Load image list 19/12/2019 20:35:03 Image load: - D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim 19/12/2019 20:35:03 Mount dir: S:\[NTLite Temp]\NLTmpMount01 19/12/2019 20:35:03 Mounting image: D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim (Windows 10 Pro) 19/12/2019 20:35:03 GWH 19/12/2019 20:35:13 Error: Image operation aborted, an error has occurred. Image might be unusable and the editing should be restarted fresh after a reboot. S:\[NTLite Temp]\NLTmpMount01\Windows\WinSxS\amd64_microsoft-windows-t..nputpersonalization_31bf3856ad364e35_10.0.18362.1_none_120982f1438ca428\Content.xml [50] The request is not supported. 19/12/2019 20:35:28 Cancel 19/12/2019 20:35:28 Waiting other operations to finish 19/12/2019 20:35:46 LastError: 50 19/12/2019 20:35:46 Error 50 mounting image: D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim 19/12/2019 20:35:47 Discarding changes - D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim 19/12/2019 20:35:47 Unloading image, discarding changes - D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim (Windows 10 Pro) 19/12/2019 20:35:47 LastError: 161 19/12/2019 20:35:47 Error: '[161] The specified path is invalid.' - Unload image - The image might be corrupted. D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim 19/12/2019 20:44:48 Mounting image: D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim (Windows 10 Pro) 19/12/2019 20:44:48 GWH 19/12/2019 20:45:11 LastError: 1235 19/12/2019 20:45:11 Error 1235 mounting image: D:\[INSTALLATION FILES]\ISOs\Microsoft\Windows 10\Win10_1909_EnglishInternational_x64\Sources\install.wim 19/12/2019 20:45:12 - UR 19/12/2019 20:45:12 - UR ld0 19/12/2019 20:45:12 Deleting temporary files - S:\[NTLite Temp]\NLScratch 19/12/2019 20:45:12 Deleting temporary files

What is code 50, 161 and 1235?
 
Update: So it may be a file permissions issue, but not something I can control. For some reason, the "NLTempMount01" folder being created when loading an image, has the ownership set to "Administrators" but at the point of failure it suddenly changes to "TrustedInstaller", so I can't do anything to it unless I take ownership. All other folders in the temp files are set to "Administrators" as they should be. However, after "unloading" the image in NTLite, which I have to do 3 times, the temp mount folder does get deleted ok.

The image also seems to partially extract into the temporary location, but only 3-4 files in WinSxS which is where it gets stuck.

Even more odd, is trying this on another image, a Dell one, it gets a little further and the temp mount folder owner is "Administrators"! However, it still fails with error 50.

I have tried enabling NTFS long paths in case those crazy long winsxs folder names were an issue. I also turned off NTFS folder case sensitivity. Neither of those makes a difference though. Compression is enabled.
 

Attachments

  • Screenshot_1.png
    Screenshot_1.png
    4.2 KB
Ok, I think it's fixed for good. I removed all trace of NTLite (then of course recovered my license key I forgot about!), and it's now working. In doing so of course, the location of the temp folders is reset. I wonder if maybe the target drive for the temp folders cannot be a drive pool? I was sure I was using it before, but now that it's back at "C:\Users\name\AppData\Local\Temp" all seems well.

To verify, I am changing the location to the "S:" pool drive... ok confirmed. Changing only the Temp location (not scratch), to my S: drive results in the error 50 failure. I guess WIMMount is doing something very low level? If you are able to tell me what this might be, I can contact the author of my drivepool software to discuss further? It's Stablebit DrivePool. But it behaves as a normal NTFS volume for everything else.

Hopefully this helps others that might get this issue!

Thanks for your patience :)
 
Hi Xeno,

that's great info, would explain some mysterious reports like this one.
Will try the drive pool and let you know if possible to adapt or at least detect and warn about it.
It is true that I have no control over the core mounting process, so a warning is more likely.

Thanks!
 
Yeah the drivepool software is something I've used for years, and just sort of forget it's there.
 
You must log in or register to reply here.
Back
Top