Mounting WIM slow after NTLite update

J

Jumme

New Member
Hello,

Since I updated NTlite few days ago (2023.3.9171) mounting and unmounting install.wim takes like forever. :rolleyes:

First it appears the progress bar doesnt move for about a minute (spinning wheel if mouse pointer in NTlite window). Fan goes ballistic.

After this progress bar moves, but about 25% of the speed it used to just a few days ago.
Approximately at 45-50% it stalls again. Maybe 30 sec pause. Then sloowly finishes. A few days ago there was no delay at all and no ballistic cpu.

NB: Saving the iso itself is exactly as fast as before.

Anyone experienced the same??


Already did:
  • Free SSD space (before 40gb free, now 60gb free / out of 250gb).
  • "Optimize" SSD (like defrag)
  • Run "Check disk" (no errors found)
  • Turn off Windows Defender
  • Turn off all VMs
  • Delete install.wim file, apply fresh from back up
  • Delete all files in local TEMP folder
  • Delete all presets + backups
  • Remove NTlite. Reboot. Reinstall NTLite.

Dont know where the log is or how to read it. In case there is one.

Thanks!
 
Last edited:
Jumme said:
Hello,

Since I updated NTlite few days ago (2023.3.9171) mounting and unmounting install.wim takes like forever. :rolleyes:

First it appears the progress bar doesnt move for about a minute (spinning wheel if mouse pointer in NTlite window). Fan goes ballistic.

After this progress bar moves, but about 25% of the speed it used to just a few days ago.
Approximately at 45-50% it stalls again. Maybe 30 sec pause. Then sloowly finishes. A few days ago there was no delay at all and no ballistic cpu.

NB: Saving the iso itself is exactly as fast as before.

Anyone experienced the same??


Already did:
  • Free SSD space (before 40gb free, now 60gb free / out of 250gb).
  • "Optimize" SSD (like defrag)
  • Run "Check disk" (no errors found)
  • Turn off Windows Defender
  • Turn off all VMs
  • Delete install.wim file, apply fresh from back up
  • Delete all files in local TEMP folder
  • Delete all presets + backups
  • Remove NTlite. Reboot. Reinstall NTLite.

Dont know where the log is or how to read it. In case there is one.

Thanks!
Click to expand...
It takes a long time with little to no Ntlite components removals. Did windows stuff get reinstalled somehow?

It moves really fast for me but mine is clean
 
Fan going ballistic means your CPU is pegged. That's Defender or another process examining every file, since mounting a WIM extracts thousands of files in a short timespan. Unmounting an image tries to resync file changes back from the scratch folders.

I would open up Task Manager, and look in Performance Tab.
 
garlin said:
Fan going ballistic means your CPU is pegged. That's Defender or another process examining every file, since mounting a WIM extracts thousands of files in a short timespan. Unmounting an image tries to resync file changes back from the scratch folders.

I would open up Task Manager, and look in Performance Tab.
Click to expand...
Yesah, sorry, should have mentioned: Defender is definately off.
Performance tab says "CPU: 15%". Also SSD, network, RAM all low. Nothing suspicious, after my opinion.

On mounting, its the first 40 seconds, then pause again at 45%.
At unmounting, its the first 40 seconds, then pause again at 50%. Exactly.

Necrosaro said:
It takes a long time with little to no Ntlite components removals. Did windows stuff get reinstalled somehow?

It moves really fast for me but mine is clean
Click to expand...
I dont think so, since I removed NTlite completely with all files and cache.
Extracted a fresh wim file from tech machine.
Reinstalled NTlite.

Issue still there. Thanks for your reply.
 
100% NTLite is OK, the fault is on your Windows side or on the hardware side?.
I don't have a crystal ball to see what you're up to with this, but turn it off
all the "bullshit" for the time being and clean up the system properly.
 
Not sure i understand correctly - but you only load install.wim inside the extracted Windows folder when you load it in NTL?
It should take about a minute exept your curent install is missing something.
After all the reinstalls someone can forget something to make things work as before.
 
Jumme said:
Thanks! Did. Same problem.

Im not sure if it was related to upgrading or just a coincidence. Will investigate further.
Click to expand...
Mounting wasn't changed, so it is not a version related.

Try redownloading an ISO and try a fresh one - now you can use it directly in NTLite to unpack itself.

If it hangs again, is your space full or changed temporary/mount directory to something other than a normal NTFS drive?
Do an elevated command: chkdsk /f drive:
where the drive is the letter of the drive(s) having the image and temporary files. May need to recopy fresh image again.

Also try in the tool disabling the File - Settings - Verify files option, but that's just avoiding the issue, even if it helps.

If none of this helps, attach the %temp%\ntlite.log at the moment of the hang.

Thanks.
 
having file verificartion on might increase build times but i have verification On in nero and it has saved my ass on a number of occasions, nuhi has it for a reason and i trust his experience.
 
Jumme said:
Performance tab says "CPU: 15%"
Click to expand...
The thing that stood out in this thread to me is this CPU usage. I'm assuming this is while idle at the desktop? If so, that's very high. It means that either the processor is not very powerful and/or there's way too much running in the background. I'd try installing a default copy of Windows, pause Windows Update, turn off Defender's real-time protection, then install NTLite and try this again.

It's probably just coincidence this happened when NTLite was updated, more than likely the main issue is background apps and/or Windows update, tweaks that were done to the computer, etcetera.
 
Last edited:
Hellbovine said:
The thing that stood out in this thread to me is this CPU usage. I'm assuming this is while idle at the desktop? If so, that's very high. It means that either the processor is not very powerful and/or there's way too much running in the background. I'd try installing a default copy of Windows, pause Windows update, turn off Defender's real-time protection, then install NTLite and try this again.

It's probably just coincidence this happened when NTLite was updated, more than likely the main issue is background apps and/or Windows update, tweaks that were done to the computer, etcetera.
Click to expand...
This is idle at desktop, while basically only NTlite running - mounting 'install.wim' from my default scratch folder.
As a reply to "mayby your CPU is pegged, look at performance tab."

It's currently not an option to reinstall the whole system, since everything else works as expected.
Including a massive number of tweaks I made in both install.wim and boot.wim (outside NTlite), and NTlite itself also working for my pupose.

Its just a minor nuisance to wait some extra minutes in my work flow (since I currenlty use NTlite as a part of a bigger experiment), while I mount and unmaount quite a few times.
I'll continue to investigate and follow up on the many different suggestions from this thread, and let you know anything I discover.
 
You must log in or register to reply here.
Back
Top