Windows 7 Platform Upgrade (KB2670838)

B

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:
I presently use the windows update downloader with the convenient rollup. KB2670838 gets removed somehow with your new version during the customizing. However, 1.3.0.5020 does not remove this update. The preset is the same as above other than the version of NTlite being used.
 
@Bournesup, thanks for reporting, will check and report back. Sorry for the delay.
VM content should not ever crash your host driver, that sounds like a VM bug or unstable system. With the Spectre patches lately, it's all in the air.
 
It has been confirmed it is the spectre patches that causes the host driver to crash. The crash is between the VM and the host. Guess, I will need to be patient as newer updates are released to address the spectre issue.
 
bump

I presently use the windows update downloader with the convenient rollup. KB2670838 gets removed somehow with your new version during the customizing. However, 1.3.0.5020 does not remove this update. The preset is the same as above other than the version of NTlite being used.

The video card driver crashing the host from virtual box has been resolved.

However, the kb2670838 still get removed which needs to be reinstalled.
 
Try to integrate only updates without removals or tweaks, after that, remove components.

Here goes my guess:
​
Skipping the KB2670838 update could be due to media components removal.​
 
Try to integrate only updates without removals or tweaks, after that, remove components.

I have tried that approach, and get the same results.

Monitoring the winsxs during the integration process into the mounted wim suggest that there is a xps component directly related to kb2670838 as well as downlevel support for directx 11. PDF has become the default method of reading and downloading documents, as well as printing documents to an non active printer, xps has become obsolete.

The observation that the older version of ntlite (1.3.0.5020) did not break the integration still holds true.
 
I have the same problem with v1.6.0.6146, it even dont show up in"Installed Updates" when I install it again.

In my preset I havnt removed any Drivers, or Hardware support so maybe its someting with the winsx

And when I load Live Install in 1.3.1.5060
I see Telephony under Network, and Diagnostics and Troubleshooting under Remoting and Priacy
but it dont show up in the later version of NTlite exempel v1.6.0.6146
 
Last edited:
Hi again @nuhi
I used v1.6.0.6146 to Integrate update KB2670838,
and when I have Installed the windows and start NTlite- Live Install or open Control panel / Programs and Features The update KB2670838 dont exist and the programs and games that need this update cant start. So I open v1.6.0.6146 again and try to Integrate the update but it says it allready exist.

But then I start 1.3.1.5060 and use Live Install and Integrate the update KB2670838 then it works to Integrate and the things works after.
 
Interesting. I thought KB2670838 had been integrated into my Win7 when I integrated it a few months ago via NTLite. I searched for it in the Windows' Installed Updates list, but didn't see it.

I just installed it manually. (Windows did not complain that it was already installed.)

But the ntlite.log says it had been integrated by NTLite.
 

Attachments

  • NTLite.log
    28.8 KB
Last edited:
I checked before using the cleanupmgr. Although it says it was integrated, it somehow gets removed during the component removal process. If you check installed updates, it is not listed. I checked it in a virtual environment and after a fresh install and in both cases it was not listed.

However, during the integration process of that update the manifest files indicate that there may be some dependencies on xps document viewer. But, I remove these components as I do not use XPS document viewer. Which may be the cause, however, NUHI hasn't replied to this thread.
 
Interesting. Well, I make a "Convenience Rollup Base" iso first that has KB2670838 integrated into it. (I guess you're gonna make me load that into a VM now so that I can see if 838 is really there.) Then I remove XPS stuff in a second run of NTLite.

I'll report back after I run the VM of my C.R. Base.
 
I confirmed that 838 is installed on my "Convenience Rollup Base" installation of Win7 64 HP.

I'll try removing XPS using NTLite next.

I forgot - I don't have NTLite activated with the particular VM I was using.

Anyway, I removed XPS using the built-in Windows' Feature Removal.

As expected, 838 survived that operation.

I'll leave it to nuhi to confirm that removing XPS with a later version of NTLite also removes 838.
 
Last edited:
After reading KB2670838 Summary


This article describes a platform update for Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1. This update improves the range and performance of the following graphics and imaging components:
  • Direct2D *
  • DirectWrite *
  • Direct3D *
  • Windows Imaging Component (WIC)
  • Windows Advanced Rasterization Platform (WARP)
  • Windows Animation Manager (WAM)
  • XPS Document API
  • H.264 Video Decoder *
  • JPEG XR codec
Click to expand...

* DVD Maker
* DVD Play
* maybe some other components

Probably:
Windows Image Acquisition (WIA) -> WIC

When i remove Remote Desktop/FX components, i got the updates listed in Windows Updates (after being integrated with NTLite).
 
I leave WIA in my preset. So something else? (Bournesup suggests XPS, and I removed that from my preset.)

Interesting that a KB would be missing when a Windows component is removed.

Does that mean that the update gets removed somehow? Or is this more of an accounting thing, where Windows reports that the KB is missing, but it's really still there?
 
Interesting. So now I wonder how may other updates that I thought I installed uninstalled themselves after component removal?

(Might be moot in my case, since I use WSUS Offline, which re-queries what I have and what I need every time I run it.)
 
Checking deeper to your preset (and compared to mine), these (added to the previous listed) look more related:

screensavers
Windows Sidebar
Snipping Tool
Still Image Class Installer
Sticky Notes
webclient
Windows TIFF IFilter (OCR)

XPS doesn't got removed, only disabled in Features and that shouldn't be a problem, unless "low level" protections are disabled.
 
Last edited:
I'll just wait for nuhi to reply to this thread. I already gave as much information as I possibly could from the observations during the update integration process, plus the preset information as well.

As for what updates get removed depends on alot of factors. Supersedence, and what components get removed.
If you check the number of installed updates on a fresh installed, and the number of updates that were integrated, most likely they will be different.

Also, check the number of items in the winsxs folder. Run the cleanmgr.exe from Microsoft, then check the number of items in the winsxs folder, then the number of installed updates most likely they will be different as cleanmgr also checks supersedence.
 
You must log in or register to reply here.
Back
Top