Please help, Image hanging prompt error 183 “Cannot create a file when that file already exists”

sanduo

New Member
Current situation:
1. I am an administrator account
2. the software version is 2.3.6.8804
3. The latest Windows 10 computer system update patch is June 15
4. mount WIM image, windows 11

Problem Description:
1. the original image has been tested and cannot be attached
2. change the image name, unable to mount
3. each mount will create many cache folders, but they will not be deleted by themselves
Unable to mount, prompting "* * * 183 the file already exists when the file cannot be created"
The log files are as follows. Please also provide help

121.png12.png
 

Attachments

  • NTLite.log
    1.7 KB
D

Deleted member 8142

Guest
pl cross sure if "Temp" directory is there inside %windir% or %systemroot%
if not create it & cross check again via mounting any wim image.
or
is dism mounting same image on same os without any errors which you used in this scenario plus %tmp% being the mount point of image.
 

garlin

Moderator
Staff member
NTLite cannot mount the WIM, due to permission errors on the temp mount (wimlib error 12).
Try these steps:

1. 'Image history / Forget' all your current images. Close NTLite.
2. As Administrator, remove all the NLTmpMnt folders.
3. Restart the system, to clear any running processes.
4. Load your install.wim
 

sanduo

New Member
NTLite cannot mount the WIM, due to permission errors on the temp mount (wimlib error 12).
Try these steps:

1. 'Image history / Forget' all your current images. Close NTLite.
2. As Administrator, remove all the NLTmpMnt folders.
3. Restart the system, to clear any running processes.
4. Load your install.wim
I have followed your steps, and the problem still exists.
If the permission is wrong, I have modified the file. All users can fully control this directory. But the problem remains.
I use the software to create many images. When I import the WIM image made in 2021, I also prompt 183 this error.
I think the only method that has not been operated is to reinstall the system!
Of course, there is a popular saying here that "restarting can solve 99% of the faults, and reinstalling can solve 100% of the faults".
 

sanduo

New Member
pl cross sure if "Temp" directory is there inside %windir% or %systemroot%
if not create it & cross check again via mounting any wim image.
or
is dism mounting same image on same os without any errors which you used in this scenario plus %tmp% being the mount point of image.
I have confirmed that the "temp" folder in%windir% exists. I also tried to empty the contents of this directory and restart.
But the fault remains. This is a strange question.
 

Attachments

  • NTLite.log
    3.2 KB
Top