NTLite v2.3.8.8889 doesn't complete all tasks

[SoulRipper]

Hello,

I updated to v2.3.8.8889 yesterday (I was using v2.3.7.8850 before).
With the same ISO, same preset, same hardware, it doesn't work anymore.

Only changes are:
- NTLite v2.3.7.8850 to 2.3.8.8889
- Latest Windows updates slipstream through the integrated tool

It stays at the "Save changes to the image" step forever. I repeated the process a few times, it always blocks at 22% precisely. The program doesn't seem to crash, it just doesn't continue the process.

Also, why was my preset modified? Example: <c>microsoft.windowscommunicationsapps 'Windows Mail'</c> disappears from the new auto-generated preset. I didn't change anything myself. I attach a copy of the changes in the auto-generated preset vs my original preset.

Is there a way to get v2.3.7.8850 back so I can finish my project and do some additional tests?

Thanks!

 

[SoulRipper]

Finally I could find v2.3.7.8850 on a third-party website. I swapped the new NTLite.exe with this one and it worked flawlessly. No other changes, just the .exe. That means there is a bug somewhere in the new NTLite.

 

[Kasual]

Also, why was my preset modified? Example: <c>microsoft.windowscommunicationsapps 'Windows Mail'</c> disappears from the new auto-generated preset. I didn't change anything myself. I attach a copy of the changes in the auto-generated preset vs my original preset.

Always attach the autosaved presets.

When a component isn't removed in later versions (or updates), this happens because is tied to another component not being removed.

 

[SoulRipper]

I'll do. But that is a secondary problem. The main issue is that v2.3.7.8850 (and previous ones) works perfectly, whereas v2.3.8.8889 doesn't.

 

[nuhi]

Hello,

I updated to v2.3.8.8889 yesterday (I was using v2.3.7.8850 before).
With the same ISO, same preset, same hardware, it doesn't work anymore.

Only changes are:
- NTLite v2.3.7.8850 to 2.3.8.8889
- Latest Windows updates slipstream through the integrated tool

It stays at the "Save changes to the image" step forever. I repeated the process a few times, it always blocks at 22% precisely. The program doesn't seem to crash, it just doesn't continue the process.

Hello,

nothing was changed that would influence saving of the image, unless there was an error prompt about busy file, Windows APIs are saving the image as always.
Please retry with the latest version, it must work. Then provide the %temp%\ntlite.log next time it happens, before restarting the tool.

Also, why was my preset modified? Example: <c>microsoft.windowscommunicationsapps 'Windows Mail'</c> disappears from the new auto-generated preset. I didn't change anything myself. I attach a copy of the changes in the auto-generated preset vs my original preset.

Windows Mail now has a new preset name, please re-uncheck it after loading your preset, it was needed to split detected app+support vs just the app.

Only bigger difference between those NTLite versions should be in app removal, make sure to select "DISM + Custom" after loading the preset, if you want the old way of removing the apps.
Potentially try that to solve the saving issue, if you repeatably get the issue with "DISM" method, that log might be crucial.

Thanks.

 

[SoulRipper]

Hello, thank you for the tips!

So, I have started everything from scratch, selected "DISM + Custom", but that doesn't help.

Log is attached.

Best regards.

 

[nuhi]

OK, this is something with NTFS short 8.3 path names:
Mount dir: C:\Users\ADMINI~1\AppData\Local\Temp\NLTmpMnt02

The tool previously used it as is, short if presented as such, but newer version resolved it on some places, which probably broke saving due to inconsistencies.
Deleting temporary files: C:\Users\Administrator\AppData\Local\Temp\NLTmpMnt02

Reported cause for cancelling:
C:\Users\Administrator\AppData\Local\Temp\NLTmpMnt01\Windows\System32\drvinst.exe
[2] The system cannot find the file specified.

I would rather continue resolving short to long paths on all places, it was for purpose of fixing other issues when people use short NTFS paths.
I'll send you a test version tomorrow, thanks for catching this.

Unloading all images, and setting in File - Settings - Temp folder as C:\Users\Administrator\AppData\Local\Temp, might help in the meantime.
If it was previously C:\Users\ADMINI~1\AppData\Local\Temp

Btw if you figure out what triggered that short path situation, I'm all ears.
Will fix it regardless - it's just so rarely reported, must be some NTFS tweak.

 

[SoulRipper]

Wow, thank you a lot for your detailed explanation.

Indeed, 8.3 file names were disabled on this computer for security reasons through the fsutil behavior set disable8dot3 1 command.
I would never have thought that SFNs are still used nowadays.

BTW:

Unloading all images, and setting in File - Settings - Temp folder as C:\Users\Administrator\AppData\Local\Temp, might help in the meantime.
If it was previously C:\Users\ADMINI~1\AppData\Local\Temp

Completely solved the problem on my side

 

[nuhi]

Thanks for the feedback.

The issue actually was the opposite, on your host it must have been set fsutil behavior set disable8dot3 0
That way it enables long names by default on all volumes.
disable8dot3 1 would also fix it, but it's not up to one tool to dictate what you do with the host, goal is that it works on all combinations.

New build 8890 uploaded, it simply resolves short name into the long name for the temp path, you can put on the host whatever you want.
Cannot confirm that it fixes all cases, time will tell, got quite a few reports of this.

Thanks.