Can't install latest CU through Windows Update after integrating the previous one and the latest SSU and removing and integrating some things

I still can't install the latest CU (in this case KB4467708) through Windows Update after integrating the previous one (KB4464455) and the latest SSU (KB4465664) and removing and integrating some things with NTLite (see the preset). I used NTLite's latest version and Windows 10 1809 Build 17763.1 x64 image. Now I have the 0x80070032 error (before I had the 0x800f081f error). Also, I don't know if it was caused by integrating updates but the install was much slower than usual.
 

Attachments

Last edited:

SM03

Member
Having this same issue. Recently I've made a customised Win10 bootable ISO via the latest NTLite v1.8.0.6593 beta. Install & Boot.wim source was from the ISO that made from latest 17763.107 refreshed ESD. Integrating all the drivers & latest 2018-11 CU KB4467708, 2018-11 SSU KB4465664 & 2018-11 SU for Adobe KB4467694. No issue during the ISO making process & installation. Even the installed Windows version is showing as 17763.134 in Winver, but the latest 2018-11 CU KB4467708 still showing in Windows update & not able to install. showing There were problems installing some updates, but we'll try again later. Error 0x800f0986. Tried to install it manually but that too didn't installed.

Attaching the Screenshots & presets here, take a look. nuhi

Windows 10 User, which version of NTlite did you use, latest stable or Beta?
 

Attachments

dezn

New Member
Same here.
"Installation Failure: Windows failed to install the following update with error 0x800F0986: Security Update for Windows (KB4467708)."

Apparently flash update works and other updates except cumulative updates.
 

SM03

Member
dezn yes, I can confirm that this bug/issue is present in both latest beta v1.8.0.6593 & stable v1.7.0.6593 build of NTLite. Just made another ISO using the stable v1.7.0.6593 build of NTlite last night & still, the same issue persisted. IDK why nuhi is silent about this matter, he used to be very prompt about such cases as I've seen in past. I am going to make another ISO on the top of the main ISO i.e. v107 using the latest stable build of NTlite & this time, I wouldn't be integrating the latest 2018-11 CU KB4467708 & other SSU & Adobe SU, to make it 134, let's see what would be the result. I will post & update here, requesting you to do the same. if possible & post further.
 

SM03

Member
Aswell as the usual things nuhi has to do there is build 1809 and all the issues that always come with a new build. If he aint here then he is busy sorting stuff. :)
I believe he surely is, but as I mentioned earlier he's very prompt to at least acknowledged any issue posted here as far as I 've seen & experienced, so that's why I was wondering about this hence asked.
 

Sonicmojo

New Member
Seeing this here as well - with the newly issued "Win 10 LTSC 2019" image just released this week. The image arrives as OS Build 17763.107 but after added the latest service stack update - I am able to apply the Adobe Flash updates but the .134 CU simply dies with Error 0x800f0986 - which I believe indicates a corrupt image.

I am going to try and install this clean via MDT with NO NTLite access and see if it's the image or NTLite.

Will report back.

UPDATE: I reverted back to the original LTSC iso - (Oct 2, 2018) and all updates install perfectly. I did apply my usual NT preset to the image and installed to a VM using MDT 8450 with Windows updates coming via WSUS. Everything installed great and I am now current at OS Build 17763.134.

I suspect there is something very strange with the "new" LTSC iso issued this week. Something feels wrong with it as it does not contain Windows 10 ENT N anymore where the original Oct 2 iso does.

I am going to chalk this one up to something being different/wrong/changed in the new ISO and go with the original for now.

S
 
Last edited:

SM03

Member
We all are facing this issue in the newest win10. Hope Nuhi will release an update for NTLite soon to fix this
 

nuhi

NTLite developer
Staff member
Build 6623 should be better in this regard. However, there are numerous preset combinations, so I need your feedback to see what else needs fixing.
Always start from the clean install, or at least Host Refreshed with the latest version, always Windows Update compatibility enabled.

Now I have the 0x800f0982 error like some users reported before.
How do you retry/fix the OS, is it clean install, Host Refresh, none of the above?
Make sure if the preset is not identical to your first post, to attach the new one and I try.
 
Build 6623 should be better in this regard. However, there are numerous preset combinations, so I need your feedback to see what else needs fixing.
Always start from the clean install, or at least Host Refreshed with the latest version, always Windows Update compatibility enabled.


How do you retry/fix the OS, is it clean install, Host Refresh, none of the above?
Make sure if the preset is not identical to your first post, to attach the new one and I try.
I installed it in a VM through a clean install (like I always do). I unchecked the Windows Update compatibility but does that mean that if I enable it in the hope of being able to install the latest CU I won't be able to remove some things I may have removed related with Windows Update after unchecking its compatibility (I think I don't removed any)? If I can install the latest CU after unchecking the Windows Update compatibility does that mean that I waited for a new NTLite version for nothing since I could have successfully install the latest CU in the x64 1803 (or even x64 1809) version with the latest NTLite versions at the time if I didn't uncheck the Windows Update compatibility (I doubt it since other users had and have this problem and I suppose all of them didn't uncheck the Windows Update compatibility)? I used the same preset like before but now I have a different error. Before that I had the 0x80070032 error (and even before that I had the 0x800f081f error although in this case I didn't use the preset I used when I had the 0x80070032 error and vice-versa) like I said in the first post and now I have the 0x800f0982 error like some users do/did and like I said before.

I still have the x64 1803 version (17134.254) installed in the host and I can't install the latest CU (because of another Windows Update error) like in the x64 1809 version I tested in a VM like I said before and I don't want to do a clean install because I'd have to copy all documents, install all program and configure settings again, although I'll have to do it later whether I like it or not, unfortunately (it looks like I'll have to do it every time a new Windows 10 version is released and after using NTLite because it'll have new functions/apps which I don't want and if I manually run the setup.exe of the new version I may have problems or still have those unwanted functions or some of them). Another reason to not have done it already is that I'm having problems in a VM install (I always test the installs in VMs in order to know if I have any major problems before trying in the host) after removing and configuring things in the 1809 version like the problem about Windows Update (can't install the latest CU also) I mentioned before. I tried that Host Refresh option (that I still don't understand what it does) like someone recommended and it didn't work (as well as manually running the setup.exe from an edited 1809 ISO created by NTLite, ISO which I used in a VM before trying this and had some problems but I didn't care when I tried it in the host) but that might have happened because I used an edited 1809 ISO (created by NTLite, ISO which I also used in a VM before trying this and also had some problems but I didn't care when I tried it in the host) while having the 1803 version currently installed (an edited 1803 ISO created by NTLite was used).

EDIT: This time I didn't uncheck the Windows Update compatibility and I still couldn't install the latest CU.

EDIT 2: So, this time I used the 17763.107.101029-1455.RS5_RELEASE_SVC_REFRESH_CLIENTENTERPRISE_VOL_X64FRE_PT-PT image and now I have the 0x800f0982 error when I had the 0x80070032 error so each time I have a different error.
 

Attachments

Last edited:

SM03

Member
Windows Update compatibility is in Components - toolbar - Compatibility, make sure it's enabled before removing any components.
oh, ok yes, I've found that, though I never actually touched that option before so it's always been on default settings, & I think as long as I don't tamper there, I guess everything is ok regarding the same.

BTW, just wanna ask you nuhi that is the latest stable version v1.7.2.6650 is stable enough now with latest win10 1809 Oct update ISO (.107) to make a customised ISO, & the update module braking issues been finally resolved in this latest NTLite version while making a custom ISO via NTLite or not? Asking this cause after that issue I never tried to make ISO via last few latest NTlite releases & now have some time to experiment so if your confirmation would be appreciated.
 
Top