KB4506990

SHO_GuN

Member
My last post seems to be a "me only" situation, lets see about this situation :)

When I integrate "windows10.0-kb4486153-x64.cab" and "windows10.0-kb4506990-x64_b08d8cae796e003093469d9ff4559b7464086617.msu", Windows Update is happy.

When I integrate "windows10.0-kb4486153-x64_8da922572d9adb038b41fb65b458b36a491ecc62.msu" and "windows10.0-kb4506990-x64_b08d8cae796e003093469d9ff4559b7464086617.msu", Windows Update requires KB4507419 to be happy. KB4507419 contains both kb4506990 and kb4506998. kb4506990 was already integrated and kb4506998 says "not applicable to this system" or words to that effect if I try to install it.

Anyone else have this happen?
 
Last edited:
.Net 4.8 right? I get my updates manually from ms and 6990 and another kb are listed under another kb and iget the same warning installing 6990.
 
Last edited:
Yeah, 4.8. Though my OP is correct, it is hard to read - let me condense my point:

Integrate .net 4.8 *CAB* and kb4506990 - WU is happy.

Integrate .net 4.8 *MSU* and kb4506990 - WU is unhappy.
 
Bloody windows, bloody .nets. :mad: facepalm. Wonder what happens with net4.8 all os .exe. Whenever these quirks show up i make a note for next time, say balls to it shrug them off until someone asks about it. Im gonna look see if i need 4.8 and if i dont then cobblers to it. Just another day in paradise :D
 
Last edited:
I integrate both .msu plus servicing stack and latest cumulative update and no problems here. Just microcode intel and flash related updates are offered.

In that order:

1. Windows10.0-KB4512937-x64.msu
2. Windows10.0-KB4486153-x64.msu
3. Windows10.0-KB4506990-x64.msu
4. Windows10.0-KB4511553-x64.msu

I tested on Windows 10 1809 LTSC.
 
I have never paid attention to "order" since switching from XP/NLite to Win10/NTLite. I just took another look at this issue.

When I use ".net 4.8 *CAB* and kb4506990 " they are integrated in that order.

When I use ".net 4.8 *MSU* and kb4506990 " kb4506990 is integrated first. I didn't test, but am guessing that is why kb4506990 isn't sticking.

I am not seeing how to change order - do you have to make a separate run to do so?
 
.NET 4.8 msu was released after the rollup. Everything will be right after the next version of .NET cumulative update. So far I think the only way to properly integrate with NTLite is to integrate KB4506990 into a separate session of KB4486153 or with a new version of NTLite that improves update detection.
 
I am not seeing how to change order - do you have to make a separate run to do so?

Yes. A search for "Integration Order" shows that this situation is so rare, the ability to change the order was not added to NTLite.

I just verified that if you do a separate run after you have done everything else and just integrate KB4506990 everything is fine.

I think that as AeonX mentions, after the next .NET cumulative update, it will resolve itself.
 
Servicing stack and cumulative update are automatically detected by NTLite and placed in the correct order. One suggestion for nuhi is to implement .NET rollup detection as well.
 
I think that as AeonX mentions, after the next .NET cumulative update, it will resolve itself.

So much for that theory :rolleyes:

KB4511522 has replaced KB4506990. It is dated 8-16-19 on Microsoft Catalog...with a build date in NTLITe of 7-24-19, one day older than KB4486153 so it is still out of order LOL
 
Back
Top