Latest KB4338814 & KB4338822 Integration Failed on NTLite

  • Thread starter Thread starter gjalleri
  • Start date Start date
Hi,

please try the KB4338822 instead, Microsoft seems to have had a bug in the now obsolete 4338814.
If you google the error 0x800f0922 with 4338814, you can see it's not tied to NTLite.

Thanks anyway, keep me updated if you have any other issues.
 
I did integrate KB4338814 then after I redid everything and integrate KB4338822 and they got the same error appeared in the screenshot.
Then KB4338822 was skipped and another error appears. Dunno if this gonna affect the installation I will check later.
View attachment 836
View attachment 838
 
I've been using nuhi's software since nLite days and also NTLite will tell that if your integrating x86 or x64 base on machine architecture.
windows10.0-kb4338822-x64_2db60cf228eca5137700178e0e7b2d6d3d19f78b

Off Topic:
I'm the one who suggest nuhi for naming his software to NTLite.
 
gjalleri, aa that's you. Thanks for the name idea once again.

I just now tried and the integration of those two KBs worked, from both Win10 1803 and same as you 8.1.
Can you please get me the ntlite and ntlite_dism logs at the moment of the error with that latest KB? The skipped one without any popup if I understood correctly.
Before that please unload the image to start fresh, and reboot the machine. Maybe even recopy the clean ISO to be on the safe side, if you haven't done so already.

Btw there is no progression percentage while integrating from Win8.1 as a host and Win10 image, just states "Processing".

Check your temp/scratch directory free space in File - Settings.

Thanks.
 
I will now try on my HDD now before I was using 13GB RAMDrive maybe lack of space I dunno and also I found a minor UI bug when you open NTLite and the drive doesn't exist.
View attachment 840
NTLite will fail to load properly and you can't change the settings to change the temp directory and some glitch with the UI.
View attachment 841
 
It was false alarm, it turns out that 13GB ram drive is not enough space for NTLiting and KB integration.
 
Thanks, will see about increasing the warning limit for the free space requirement in that situation.
 
Back
Top