Error [183] Cannot create a file when that file already exists.

H

Hatless2139

New Member
Messages
4
Reaction score
0
I have searched all over the site and tried all the suggestions I could find. As you can see in my log i've tried changing the temp folder locations.

I've also tried running the program as admin

i've tried other ISO files (the one in this example is fresh from microsoft today)

I decided to buy this program after running a test build in a virtualbox with the free version. This is a pretty sad way to start off after spending the money to support the program :(

Any help to resolve this would be appreciated.
 
This is a new NTLite major build, which may have new unreported bugs. But this is a common error, we should check the obvious first.

Are you running any 3rd-party security software? Please temporarily disable it while running NTLite. Most likely your VM instance isn't running with the same level of security enabled.
 
garlin said:
This is a new NTLite major build, which may have new unreported bugs. But this is a common error, we should check the obvious first.

Are you running any 3rd-party security software? Please temporarily disable it while running NTLite. Most likely your VM instance isn't running with the same level of security enabled.
Click to expand...
I only use windows security. I don't install extra AV programs, firewalls, etc.
 
Have you tried temporarily disabling real-time scanning while NTLite is processing?
 
garlin said:
Have you tried temporarily disabling real-time scanning while NTLite is processing?
Click to expand...
I just tested this. No luck. I even did a fresh start, cleared out everything from the program and deleted all of the temp folders/caches
 
Hatless2139, is maybe e:\Temp\ on a RAM drive, a hardlink or something unusual compared to the normal fixed NTFS drive?
Looking at the log, trying to open the image for mounting fails, that is not normal, must be something with the system itself.

Maybe try deleting in Regedit this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images
(After unloading any loaded/blue images from the tool itself)

Recopy fresh image that you're sure is not corrupted, and retry then.
Update the tool first while at it.

Let me know if you remember anything that could help replicate this.
 
nuhi said:
Hatless2139, is maybe e:\Temp\ on a RAM drive or something unusual compared to the fixed NTFS drive?
Looking at the log, trying to open the image for mounting fails, that is not normal, must be something with the system itself.
Click to expand...
No, I do not use RAMDRIVE or any similar software. I only moved it to E:\temp after it wasn't working in the default location on [ C: which is just a standalone nvme m.2 SSD ]
nuhi said:
Maybe try deleting in Regedit this key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WIMMount\Mounted Images
(After unloading any loaded/blue images from the tool itself)
Click to expand...
Nothing was listed inside of this key but i deleted it anyways.
nuhi said:
Recopy fresh image that you're sure is not corrupted, and retry then.
Update the tool first while at it.

Let me know if you remember anything that could help replicate this.
Click to expand...
I uninstalled ntlite, removed the reg key above, and all temp folders. downloaded fresh ntlite installer, downloaded a fresh w11 iso from microsoft again today. Verified the hash. Same Error. Ntlite 2024.3.9817. Tested again after switching to beta 2024.3.9819: same error. Switched back to stable which brought it to 2024.3.9819: same error. (removed all temp files between each test)
 
Hatless2139 said:
No, I do not use RAMDRIVE or any similar software. I only moved it to E:\temp after it wasn't working in the default location on [ C: which is just a standalone nvme m.2 SSD ]

Nothing was listed inside of this key but i deleted it anyways.

I uninstalled ntlite, removed the reg key above, and all temp folders. downloaded fresh ntlite installer, downloaded a fresh w11 iso from microsoft again today. Verified the hash. Same Error. Ntlite 2024.3.9817. Tested again after switching to beta 2024.3.9819: same error. Switched back to stable which brought it to 2024.3.9819: same error. (removed all temp files between each test)
Click to expand...
Then try another machine, it must work.
For example spin up a virtual one on that machine, just for testing, if you don't have another machine (OS) at hand.
Other than a broken mounting engine, I am out of ideas. We can talk about the OS repair after you confirm it can work, as there is always a small chance it's something unique.

After another OS is checked with the same image, you can also try mounting on the "broken" OS with this tool to see potentially another error, or it shows it works, then I wonder which parameters you put in there.
Mount point is the new temporary directory, dedicated to the mount.
Source is WIM path (.\Sources\install.wim on that image, copied outside of ISO).

Thank you.
 
Hi,
Had the issue when evaluating Microsoft Automated Deployment Kit (ADK) alongside NTLite.
on Windows 10 Enterprise 22H2 x64 - 10.0.19045.4412

The issue happened after uninstalling ADK. In a nutshell, ADK uninstall deletes HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount key which loads wimmount.sys driver.

This shows as below in C:\Windows\Logs\DISM\dism.log when attempting to load a .wim file with NTLite or dism.exe
Code: 
2024-05-27 21:48:31, Info                  DISM   DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
[5588] [0x800704db] OpenFilterPort:(408): The specified service does not exist.
[5588] [0x800704db] FltCommVerifyFilterPresent:(502): The specified service does not exist.
[5588] [0x800704db] WIMMountImageHandle:(1099): The specified service does not exist.
[5588] [0x80070002] StateStoreRemoveMountedImage:(1124): The system cannot find the file specified.

I restored the registry settings by importing the following .reg file from a colleague. This solved my issue after reboot. NTLite back to running.
Code: 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount]
"DebugFlags"=dword:00000000
"Description"="@%SystemRoot%\\system32\\drivers\\wimmount.sys,-102"
"DisplayName"="@%SystemRoot%\\system32\\drivers\\wimmount.sys,-101"
"ErrorControl"=dword:00000001
"Group"="FSFilter Infrastructure"
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,64,00,\
  72,00,69,00,76,00,65,00,72,00,73,00,5c,00,77,00,69,00,6d,00,6d,00,6f,00,75,\
  00,6e,00,74,00,2e,00,73,00,79,00,73,00,00,00
"Start"=dword:00000003
"SupportedFeatures"=dword:00000003
"Tag"=dword:00000001
"Type"=dword:00000002
 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount\Instances]
"DefaultInstance"="WIMMount"
 
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WIMMount\Instances\WIMMount]
"Altitude"="180700"
"Flags"=dword:00000000
 
Oh! That's some great info, will add detection if that key is missing for people to reinstall ADK or to restore automatically since those are standardized entries.

Thank you.
 
nuhi said:
Oh! That's some great info, will add detection if that key is missing for people to reinstall ADK or to restore automatically since those are standardized entries.

Thank you.
Click to expand...
Hi Nuhi,
Thanks a lot for your reply to this thread.
Please note that in my specific case, reinstalling Windows ADK did NOT configure back WIMMount registry key. I had to restore it manually.
The issue may lie in adksetup.exe or adkwinpesetup.exe uninstall parameters.

I look forward to your next update with the missing key detection :)
In the meantime, I will continue trying to convince my company to purchase your great product for our Windows 11 deployment.
 
This happened to me as well. It was I had uninstalled Macrium Reflect, which very kindly left the key broken.
Perhaps, if you wanted to be very kind, you could check that offer to reset the registry key for wimmount.sys is pointed to a valid location and if it is not offer to reset it to stock.
I created a .reg file with the above settings and it fixed the same error for me.
 
Thank you, so it's 2 uninstallers so far that break Windows image mounting.
Well, thank you both for finding this, now I am motivated to invest time into detecting and auto-fixing that situation.
At first it was just cool to have, now it's a necessity.
Should be in after the next version, will post here when done for future readers of that error code.
 
You must log in or register to reply here.
Back
Top