what does this mean?

jvidal

Member
Hi, everyone!
using NTlite 2.0.7580 64-bit.
Integrated all updates into win81SL x64 and everything went fine, except at the very end, a message popped up saying "Error 0x0000007f" [127] the process could not be found" (or words to that effect). After closing that, the process continued and the ISO was created.
What does that error mean? what process couldn't be found?

greetings,

J.
 
Hi, everyone!
using NTlite 2.0.7580 64-bit.
Integrated all updates into win81SL x64 and everything went fine, except at the very end, a message popped up saying "Error 0x0000007f" [127] the process could not be found" (or words to that effect). After closing that, the process continued and the ISO was created.
What does that error mean? what process couldn't be found?

greetings,

J.
I've been having some errors (I think I also had that) when creating the image (besides the one thanks to DISM after integrating NetFx3) but when I have them I unload the image and start the process from the beginning. Also, after unloading an image or even successfully creating a new one, I always delete the previously extracted ISO content and extract it again before loading it on NTLite when wanting to create another image.
 
Last edited:

jvidal

Member
BTW, I tried the resulting ISO on a VM and it installed just fine, except for KB2990967, which was not integrated, but copied to the $OEM$\$$\setup\updates folder, but didn't get installed after installation ended.
 

nuhi

NTLite developer
Staff member
Hi, everyone!
using NTlite 2.0.7580 64-bit.
Integrated all updates into win81SL x64 and everything went fine, except at the very end, a message popped up saying "Error 0x0000007f" [127] the process could not be found" (or words to that effect). After closing that, the process continued and the ISO was created.
What does that error mean? what process couldn't be found?

greetings,

J.
Please attach the preset which demonstrates that and I'll check it.

Windows 10 User, stop spamming if you have no solution to help with.
 

nuhi

NTLite developer
Staff member
jvidal, thanks. OK, sending you the fixed setupcomplete entry test version in the private message.
But for the error 127, can you run the integration from something other than Windows 7?
It might be the Windows 7 DISM is obsolete for it, it would help to know which exact update, so when it happens the next time, please save %temp%\ntlite.log at the very moment.

Let me know how it goes.
 

jvidal

Member
Hi!
I usually run NTlite under win81 x64, only this time I had my workbench busy with other stuff, so I used my main PC (with win7, but updated DISM). I'll try again under win81 and if that doesn't work, I'll try the new version you sent me. thanks!

about the 127 error, all updates (except kb2990967,which is set to run at first boot) are integrated. it's just after that and before the "rebuilding of the WIM file" that the error appears.
I'll report my findings.
 

jvidal

Member
OK, now I did it on win81 x64 host machine and no error 127 (or any other errors). However, setupcomplete.cmd was NOT created under $OEM$\$$\Setup\Scripts (actually, not even the scripts folder was created).
looking at the log, it says "KB2990967 does not support integration, using post setup method", the .msu is copied to the updates folder, but the script is not created...
This is weird, because version 1.x of NtLite did create the setupcomplete.cmd script when needed...
I guess I'll try build 7582 now.
 
Last edited:

nuhi

NTLite developer
Staff member
OK, now I did it on win81 x64 host machine and no error 127 (or any other errors). However, setupcomplete.cmd was NOT created under $OEM$\$$\Setup\Scripts (actually, not even the scripts folder was created).
looking at the log, it says "KB2990967 does not support integration, using post setup method", the .msu is copied to the updates folder, but the script is not created...
This is weird, because version 1.x of NtLite did create the setupcomplete.cmd script when needed...
I guess I'll try build 7582 now.
Thanks for the info, yeah the test version's purpose was to test the setupcomplete fix.
Let me know how it goes.
 

Brutser

New Member
nuhi: i don't know if it's related, but I often get an error when I try to apply the changes, especially if I load a preset, then make some changes, save preset, make some more changes, i cannot pinpoint it, but then when I start the apply process, I get an error even on removing XPS document writer - the apply process I can then only cancel, un-mount the image (discard) then mount it and load the saved preset, start apply and no problems.

I will write if I can actually find a way to trigger this error, so you have some more information, but maybe this is already known?
 

jvidal

Member
Alright, tried build 7582 and everything went smoothly. Setupcomplete.cmd WAS created in $OEM$\$$\Setup\Scripts.

everything seems fine.
Gonna try the image on a VM now, just to be sure.
 

jvidal

Member
Ok, so I tested the image on a VM and it went fine, except windows update still asks for KB2990967, although this time it should have been installed at first boot...
 

nuhi

NTLite developer
Staff member
Ok, so I tested the image on a VM and it went fine, except windows update still asks for KB2990967, although this time it should have been installed at first boot...
Seems like it may be normal reading about it here.

Also see if the Setup\Scripts (and Setup\Files) is cleaned, which would mean it was ran, however if the folders are still there after install then it wasn't executed.
Last idea is to enable OEM SetupComplete under Unattended, if you're using an OEM product key (that makes Windows skip setupcomplete).
 

jvidal

Member
I believe the folders were deleted (or never created, for all I now). I'll have to check again.
I think the key is OEM, yes.
Anyway, it's not a big deal, since it's only one small update.
Thanks again for your patience and hard work!

PS: Are you going to release an update to address the setupcomplete issue anyway? Like make build 7582 official or s/thing like that?
 
Top