Windows 7 Platform Upgrade (KB2670838)

Bournesup

Member
I am currently using ntlite version 1.5.0.6025 (latest). After integration and customization and checking windows update in a virtual environment it indicated that kb2670838 needed to be reinstalled. However, that update is included in the build originally (Note preset, file attached). This is a very key update as it contains directx 11. This could be the reason I get a video card driver crash while using virtualbox. After, reinstalling the issue goes away.
 

Attachments

  • currentpreset.xml
    36.2 KB
Last edited:
This "trivial dependency" stuff (a term I just coined) where a KB might not install (or might remove itself) because a non-important side program isn't detected might explain the behavior I'm seeing on my NTLite'd Win 7 box.

Specifically, up until a week ago, I've only been letting WSUS Offline Update offer me Security Patches. So, after installing Win7 with the Convenience Rollup already integrated, WSUS offered me about 50 patches.

Last week I decided to let WSUS Offline offer me everything. To my surprise, it only offered 5 more updates. So I have a total of 59 Windows updates on my 'Lite'd Win 7 Box. Whereas my friend, who also has Win7 64 Home Premium, has 307.

That's not quite an apples to apples comparison because I sometimes use Microsoft Update on her computer but never on mine. And I sometimes let Windows do "Important" updates on hers. (Whereas I don't think the WSUS care about those.) And even tho I've 'Lite'd hers a bit, her computer isn't as barebones as mine. (If nothing else, she has IE11 on hers, which is probably responsible for a large number of those updates.)

Anyway, I wonder if NTLite should make dummy - or placeholder - files (or whatever it is that Windows update looks at to see what's installed) so that critical and important KB's will be installed, even if some trivial dependency is missing.
 
I just made a Win7 64 H.P. build with a beta v1.7 of NTLite. I had integrated KB2670838-x64 into my "Base" wim. (What I call Win7+SP1 with the Convenience Rollup, or "SP2.") Then I ran that Base thru NTLite again and did some removals.

Sad to report that KB2670838 disappeared after that. (Or, at least, it doesn't show in the List of Windows Updates in Control Panel.)

I was hoping that the new re-ordering of this KB in NTLite would fix this problem.

I have no idea what's causing this. This time around, I also installed a sister KB for 383, KB2834140-v2-x64. That KB is listed.

But I did remove some of the obsolete Windows codecs. And since this is supposed to be an update for mp4, maybe that's what's causing the KB to uninstall? (BTW, I have CleanUp set to "None.")

This particular Preset wasn't as aggressive as others I've done. I've attached it - although, remember, you have to start with a Win7+SP2 Base.

(Maybe I'll try doing the removals at the same time I integrate the KB's, although I don't see why that should make a difference.)

In the meantime, a workaround is to manually install the KB after you install Win7. It persists after that.
 
Actually, I think I'll let nuhi do the experiment. Here are the KB's I integrate:

Windows6.1-KB2670838-x64.msu

Windows6.1-KB3177467-x64.msu

windows6.1-kb3125574-v4-x64_2dafb1d203c8964239af3048b5dd4b1264cd93b9.msu

Windows6.1-KB2552343-x64.msu

Windows6.1-KB2834140-v2-x64.msu

Windows6.1-KB3172605-x64.msu

So the experiment is to integrate these and append the Preset above and see if KB 838 survives in the final installation.
 
Last edited:
Okay, I couldn't resist. (Hope I didn't duplicate nuhi's effort.)

Bottom line: It appears that KB2670838 is not being integrated by NTLite.

I did a fresh install of a (mostly) vanilla NTLited Win7 64 H.P. on a spare primary partition.

I started with the M$ OEM Win7+SP1 iso. To that I used NTLite 1.7 beata to integrate the six KB's in the post above.

I didn't remove anything in the wim except for a bunch of non-English fonts, all the keyboards except US, all the languages except US.

When I booted it up for the first time and checked to see if 838 was in the list of KB's in Windows. It was not there.

Now, I suppose it might be that 838 needs a certain keyboard, or language or font in order to install.

But I don't think that can be the problem, because I can manually install 838 without adding anything back to the installed Windows.

Same if we suggest that 838 needs a prerequisite. If it did, then how could I manually install it without adding the needed prerequisite first?

It might be that it's installed, but Windows doesn't report it.

But that can't be true because after I manually install 838, Windows shows it.

The interesting thing is that, when you're integrating 838, NTLite acts like it's integrating it. That is, the gas gauge takes a while to move along.

So, nuhi,, seems like you ought to try this one for yourself to confirm. What do you think Bournesup ?
 
Ive got 838 dated as 2013-02. 77467 is the SS dated 2016-07-27, then 3125574. Looking where i have them stored then 838 probably isnt needed because its not in my SP2(3125574 and pre reqs only) folder.
 
838 is a platform update that is needed for Resolve (free high end video editor) to display mp4 video files. Microsoft says that it's also required for IE11 install. (But I don't care about IE11.)
 
Now that I've slept on this, a little bit of confusion.

In an earlier post, I tested just integrating updates with no removals. According to what I reported back then, 838 survived.

So it seems that something in the removal engine is removing 838?
 
Last edited:
pmikep, hi, so with your recent findings, can you please summarize this report into a preset which causes KB2670838 to be missing.
Can I use the above "2-ntlite-1-7-sp2-53-with-addbacks-xml" to see the issue?
I presume without removing anything, Windows Update does not list KB2670838 as missing.
Thanks.
 
Your summary is correct and you should be able to use that preset. But give me a few hours and I will run it all on a VM in v1.7 to confirm for sure.
 
Confirmed. Take the first Preset (attached), which is just Win7+SP1 with the Convenience Pack and 838 and you will see 838 listed in the Updates in Windows.

Then take the second Present, which is the very much the same (except with most fonts and keyboards and languages removed, drivers and reg's added) and 838 will not show in Windows.

Note that, for the second, I did not build on an SP2 Base but rather, I let NTLite integrate the KB's during the build, just like the first build.

(I suppose this is a good opportunity to do two builds at once with that new feature NTLite!)
 
pmikep, thanks for more info. I'm a bit sidetracked by that unofficial "SP2" notion.
How I read your report: 'SP2 base after some removals has 838 on WU, while if 838 is integrated with NTLite and the same components removed, it's fine'.
If installing 838 after that happens helps, I suggest to put 838 to Post-setup in the case of that weird reappearance.
If you see it when normally integrated + removals, I'm interested in fixing that, while I cannot guarantee what the unofficial 'SP2' did there to half-cause such a weird anomaly.
 
Calling 3125574 "SP2" does throw people because there was an update called SP2, it was very small if i recall, not like xp's sp2 and sp3 at all in comparison. Note to self - stop calling 3125574 SP2 even in brackets. :)
 
Point taken. I'll plan to go back thru this thread and remove all my references to SP2. (In a day or two.)
 
pmikep, oh you meant Convenience Rollup update, that's fine now.
OK, so is KB3125574 being integrated by NTLite in the working version as well, or you split it into sub-KBs when it works, and when integrating KB3125574 with NTLite as well, the problem appears?
 
Yes, I meant Convenience Rollup.

I don't understand your question.

So I'll reiterate the problem:

I start with Win7+SP1 iso from Microsoft.
I run that through NTLite, integrating KB 574 and 838 into it. (Plus four more KB's.) No removals. No Clean Up.
(See my first Preset above.)

I call that my Convenience Rollup Base.
When I install that iso, 838 shows in Installed KB's in Windows 7.

Then I take my Convenience Pack Rollup Base and I run that through NTLite to remove a bunch of stuff.
(See my second Preset, above.)
When I install that iso, 838 does not show anymore in Installed KB's.
 
pmikep, thanks for the clarification, it's clear to me now.
I'm guessing you remove Internet Explorer? Anyway, removals are dynamic, they pull in any updates that are tied only to the component being removed.
I could review your preset to see which one does it, if WU bothers you after the removals to reinstall it, might manually protect it.
 
Per the Presets, no, I did not remove IE using NTLite.

I don't use WU. (I use WSUS Offline Updater.) I only discovered that NTLite had removed KB 838 when Bournsup reported it here.

It seems odd that NTLite would remove an already installed/integrate update.
 
I did a new build using NTLite 1.0.7.6400. Enqueue downloaded and integrated KB2670838 to my Win7 Convenience Rollup Base image.

Then, when I ran my Preset with removals, NTLite apparently removed KB2670838. (It doesn't show up in the Windows' Updates List in Control Panel.)

Any logs I should attach to help trouble shoot this?
 
Back
Top