Unchecking [SFC] Breaks Some Installs

  • Thread starter Thread starter Chozo4
  • Start date Start date
C

Chozo4

Guest
Greetings Nuhi,

Not sure if this has been reported at all but was helping a colleague diagnose as issue with their lited install. We were using NTLite (1.5.0.5930) to trim down Windows 7 Professional N SP1 for size testing on a 4GB compact flash drive for an embedded system. We cannot check if it was resolved in newer versions due to their license being expired at this point and I saw nothing noted regarding this regression in the future changelog so I do apologize if this has already been resolved.

After trimming it all down, everything seemed to be going well until it came to installing certain things such as the Visual Basic 2008 SP1 64bit runtime and UX Style Core. They were consistently aborting mid process regarding unable to install VC90 assemblies.

From the UX Style Core for instance the error would be as follows:
Code:
Error 1935. An error occurred during the installation of assembly 'Microsoft.VC90.CRT,version="9.0.30729.1",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {9718BF1D-6A9F-3406-A992-630F7EF2F164}
=== Logging stopped: 11/03/2018  13:46:46 ===

Meanwhile the Visual Basic Runtime installer would throw a similar error but for Microsoft.VC90.ATL.

After narrowing it down and manually trimming down a fresh WinSxS folder bit by bit it comes out to have been as simple as the "InstallTemp" folder being removed from WinSxS as part of the SFC removal process. Restoring the folder resolved these issues. This issue can be replicated with a lited install with only SFC unchecked and an OEM copy of Windows 7 Professional N SP1 COEM (Win7_Pro_N_SP1_English_COEM_x64.iso).
 
Last edited by a moderator:
"We cannot check if it was resolved in newer versions due to their license being expired at this point ..."

This is a common misunderstanding, that I also misunderstood. You might indeed be able to run the latest version on NTLite on your "old" license. (I am.) The only things that won't work are any new features.

No harm in trying to update to the latest build. I'm using 1.5.0.6050 on last year's license and everything works for a Win7 installation.
 
Last edited:
You might indeed be able to run the latest version on NTLite on your "old" license. (I am.) The only things that won't work are any new features.

Good to clarify on that, thank you. I will bring it up to them by the end of the week when they are available again.
 
Chozo4, oh, thanks, yes InstallTemp is needed, this should not have happened and it doesn't in Win10 removal of the same component.
Fixed in the next update.
 
Back
Top