Image creation aborted - [112] There is not enough space on the disk.

User_X1

User_X1

New Member
Messages
24
Reaction score
1
Hi Guys
I am busy integrating drivers, changed a few settings and selected unattend options.
Im using an image where it only has 7 Ultimate x86 and x64, the other versions I removed.
At the "Save changes to the image" stage the error pops up stopping the process.
The temp partition has plenty of space - its a 31GB partition with 6.51GB used and 25.2GB free at the time of the error.
I can't understand why the error keeps popping up.
I work on a 7 Ultimate x64 PC and use NTLite x64_2025.01.10263 (before I used x64_2024.12.10210 when the error started, I thought downloading the latest version would solve the problem but it still remains)
I have not installed new programs or changed any Windows settings.
Antivirus is off when i am trying to perform the customization of the 7Ultimate source with NTLite.
I would be very grateful for any help.
 
Is the H: something other than a normal NTFS partition?
If it's a RAMDrive or similar, that would explain it.

Have you really checked H: free space at the moment of the error, cannot believe it to take only 6.51GB for Windows + 345 drivers.

If integrating Nvidia driver, make sure to include only the main INF (nv_disp or so) and audio INF, not multiple of them as it multiplies in size.

Try also using a subdirectory instead of the root directly.
H:\NTLTemp for example, unload all images, set that as the Temporary directory and start again.

Let me know if this helps, then we see what needs to be done from tool's side.
 
Hey
Thank you for your reply.
H is a normal NTFS partition on a SSD drive. (500GB SSD drive)
I did check the free space at the moment of the error yes, I did not click OK on the error screen and immediately went to check the space on H.
I will go and check the Nvidia driver.
I used to use a subfolder named Temp but then I tried just using the root to see if it solves the problem but still no luck.
 
I have now done the x86 part of the 7 Ultimate image and it completed successfully but Save changes to the image only shows 50%.
Is this normal?
 
Still no luck. I have determined its a problem with the x64 modification. The x86 modification completes successfully.
(I have removed the Nvidia driver)
Here is the temp partition space at the time of the error.
 
User_X1 said:
Still no luck. I have determined its a problem with the x64 modification. The x86 modification completes successfully.
(I have removed the Nvidia driver)
Here is the temp partition space at the time of the error.
Click to expand...
8~9GB free is not that much, try to get more, as the error suggests.
x64 is bigger.
 
Hey
OK I am going to delete files in the adjacent partition and make the Temp partition bigger with 10GB.
Will post back if it worked.
 
No something is very wrong.
The Temp partition is at 55GB now and the problem remain.
How can I fix this please?
 
Nah bro seriously this thing doesn't work.
I've been trying everything for 4 days without success.
I even tried on a Windows 10 PC.
 
How many .inf files in the Nvidia driver folder?
dism has a known behavior of creating separate folder for each inf file in the mounted image
 
Hi there was a lot, about 15.
But i removed that Nvidia driver already.
I also chose different hard drives for the temp and scratch folders with 55GB each.
 
Hm, that is indeed puzzling.
Here are the things I would recommend:

- Always start from a fresh image that is known to be valid, compare hash of it to the known ones.

- run an elevated command line for each of those disks/partitions
chkdsk /f X:

Where X is temp and scratch partitions.
This will fix any wrong size assessments there might be in the NTFS.
To simplify things don't specify scratch elsewhere, keep it with the temp (default/unchecked custom).

- Install latest ADK, updating WIM engine of your host, maybe it has a bug.
learn.microsoft.com

Download and install the Windows ADK

Instructions on how to download and install the Windows ADK
learn.microsoft.com
Enough is to select Deployment tools from it.

- As the last resort, install Windows 10 or 11 in a virtual machine and use the tool from inside it.

Let me know how it goes and if you figure this out.
Make sure to skip Nvidia driver (or just keep 1 inf for video and 1 for audio) while debugging this.
 
Hey, again thank you so much for your reply and all the sugestions I really appreciate it. Apology for my delayed reply. After 4 days fulltime strugling with this I had to catch up on some things. Today I have time again to try. I will report back on the results.
nuhi said:
Hm, that is indeed puzzling.
Here are the things I would recommend:

- Always start from a fresh image that is known to be valid, compare hash of it to the known ones.
Click to expand...
I always use a fresh image
nuhi said:
- run an elevated command line for each of those disks/partitions
chkdsk /f X:

Where X is temp and scratch partitions.
This will fix any wrong size assessments there might be in the NTFS.
To simplify things don't specify scratch elsewhere, keep it with the temp (default/unchecked custom).
Click to expand...
Did this, I have attached a screenshot
nuhi said:
- Install latest ADK, updating WIM engine of your host, maybe it has a bug.
learn.microsoft.com

Download and install the Windows ADK

Instructions on how to download and install the Windows ADK
learn.microsoft.com
Enough is to select Deployment tools from it.
Click to expand...
I tried before and tried just now but I am never able to download ADK, I attached a screenshot
nuhi said:
- As the last resort, install Windows 10 or 11 in a virtual machine and use the tool from inside it.
Click to expand...
I have Win10 Pro on this same PC and tried from within Win10 with same result, I suspect the Temp partition may be the culprit
nuhi said:
Let me know how it goes and if you figure this out.
Make sure to skip Nvidia driver (or just keep 1 inf for video and 1 for audio) while debugging this.
Click to expand...
I have skipped the Nvidia driver a few sessions back with same result
 
Damn it did not work. I am so disappointed. I think i am going to have to just give it up :(
It is not to be.
 
On Properties, check "Previous Versions". You wouldn't happen to have Volume Shadow Copies enabled?
 
Can show result of these commands?
Code: 
fsutil fsinfo ntfsinfo H:
fsutil fsinfo volumeInfo H:
fsutil resource info H:\
 
Guys I have made progress.
I overlooked a Nvidia driver which caused the problem.
I selected 2 and missed the other one.
Thank you for your patience with me and your time to assist me I really appreciate it.
Today I made the most progress so far but still no success.
Windows installed flawlessly but at the first start after the installation for a moment there was an error saying:
"Logon Initialization Failure"
Then Windows restarted and a black screen displays.
I have attached it.
Could you please share your thoughts what the reason might be?
I would be very grateful.
 
Yes but really strange
Its a new SSD.
Gee this Win7 mod is giving me hell.
But i have a little good news, after this error i managed to cook up a version that started up into Windows.
First the Auto Logon said wrong password but there is no oassword - i left it blank.
Then Windows auto restarted and logged on successfully.
However i only included the necessary drivers to get Windows working (which wasn't easy)
Now i have to make a version with all the drivers (audio, lan, wlan, video)
Slowly i am making progress but its like picking a lock.
 
You must log in or register to reply here.
Back
Top