Error 183: Cannot create a file when that file already exists.

Krunklehorn

Krunklehorn

New Member
I get this error when trying to load an exported WIM of Windows 10 Home from the stock Microsoft ISO.

The program aborts and attempts to unload the image but gets stuck on a particular file and just fails, leaving the image in a fake mounted state.
It can't be deleted unless I boot to PE and use console commands. I've cleared it like six times already. Then I can reboot and then NTLite lets me
unload the image.

I tried reinstalling NTLite, redownloading the ISO, tried it with the Professional WIM instead and tried it on two different computers. Nothing works.

EDIT: Just tried converting the stock ESD to a WIM keeping all the images in tact and then loading the Win10Home image but the issue is still here.

See images for more details...

https://imgur.com/PomgloK
https://imgur.com/l6Fcqpt
https://imgur.com/Ijr5GCm

Thanks for the time!
 
Last edited:
Are you using only one drive for Windows and everything?
If so, then your drive might be too fragmented, also, is recommended to use a short path, as C:\Slims or D:\Slims (when you have more than one drive letter).
 
Kasual said:
Are you using only one drive for Windows and everything?
If so, then your drive might be too fragmented, also, is recommended to use a short path, as C:\Slims or D:\Slims (when you have more than one drive letter).
Click to expand...

I don't think so because the computers I'm doing this on are store front display laptops. They're fresh and haven't been used for anything.

It's always the same file too, systemreset.exe, every time.

Last thing I can try is an older ISO. Does anyone know where I can get older stock builds?
 
Kasual said:
Are you using only one drive for Windows and everything?
If so, then your drive might be too fragmented, also, is recommended to use a short path, as C:\Slims or D:\Slims (when you have more than one drive letter).
Click to expand...

Ive never had this issue using default folders.
 
These are the default folder paths using the Administrator acount on w7.
C:\Users\Administrator\AppData\Local\Temp and C:\Users\Administrator\AppData\Local\Temp\NLTmpScratch

For the Source folder i usually use x:\w7dvd(orw10dvd etc).
Capture.JPG
 
Okay I re-downloaded NTLite and the Win10 ISO and changed my temp and scratch directories to C:\Tmp and C:\Scratch on a completely new store computer but still had the same problem!! =(

It's always the same file called systemreset.exe!
 
Store front displays, display units, are they are running in retail demo mode? That could be your bogey.
 
Clanger said:
Store front displays, display units, are they are running in retail demo mode? That could be your bogey.
Click to expand...

Nope, they're just regular laptops, completely clean, fresh Windows 10 on all of them. Hard drives all pass the SMART test I do using CrystalDisk. Variety of brands, Acer, Dell, HP etc.
 
@Krunklehorn, This looks like a too long path, or corrupted WIM issue, or your antivirus in the background.

You said you tried on a fresh machine. Once you changed to a shorter path, did you unmount any previously loaded image, copied fresh image and remounted/reloaded it?
Because the mount folder is not changed until the image is reloaded, if it was already loaded using the previous path, it remains like that.

Please confirm or retry the shorter Temp folder path, freshly loading the image.
For corrupted WIM, there should be a message in that temp folder, in ntlite.log, you can attach it here at the moment of the issue, if the above didn't help.
And try suspending any antiviruses in the background, it's often that too.

Thanks.
 
This morning, my system reported this exact error and it turned out to be DISM. W7 tried to install Oct. 21 SSU (servicing stack), and it didn't work.
Because DISM was broken, I couldn't remove it from Installed Updates, or using NTLite.

The solution was rolling back to a System Restore checkpoint. Lesson here: don't disable or remove System Restore.
It can repair many unexplained install or update problems.
 
i had the same error 183, on w11 original image from microsoft, the build 318, change the shortcut from the default location to root (C:\), and create two different directories, one for mount directory, second for scratch directory, should work fine. It won't fix it until you cleanup the default temp directory for ntlite, or choose like nuhi said.
 
Please try build 8890 or newer, this (NTFS 8.3 names on the host support) should be fixed.
 
nuhi said:
Please try build 8890 or newer, this (NTFS 8.3 names on the host support) should be fixed.
Click to expand...
Hi nuhi
For the first time in the last 4/5 yrs I got this error 183 messages searched google & found all these threads so just posting it here without creating a new one

using the latest NTLite 2.3.8.8890 & got this error
1.png

Tried completely uninstalling & reinstalling, still the issue persisted, so reporting here
Tried multiple times, uninstalled, clean the NTLite DIR, temp folder, & everything, also tried different user accounts & different directories [path] to install to get rid of this, but none absolutely worked so seeking help here

since this thread has the very recent of your response so choose to report this here. can you provide any fix for this?
 
SM03 said:
Hi nuhi
For the first time in the last 4/5 yrs I got this error 183 messages searched google & found all these threads so just posting it here without creating a new one

using the latest NTLite 2.3.8.8890 & got this error
View attachment 8111

Tried completely uninstalling & reinstalling, still the issue persisted, so reporting here
Tried multiple times, uninstalled, clean the NTLite DIR, temp folder, & everything, also tried different user accounts & different directories [path] to install to get rid of this, but none absolutely worked so seeking help here

since this thread has the very recent of your response so choose to report this here. can you provide any fix for this?
Click to expand...
Thanks, sending a test version, we can continue via PMs.
 
nuhi said:
Thanks, sending a test version, we can continue via PMs.
Click to expand...
nuhi
just tested it, not solved, PM'ed you the screenshots & log files. check pls

EDIT: If anyone reading this after I posted here originally, It has been fixed since v8913
 
Last edited:
You must log in or register to reply here.
Back
Top