This thread seems to be the same question as yours

However it took forever to load, so I will post it here:

Title: Windows Components Not Updated by SETUP.EXE

From: minoura
Date: 08/27/2002 12:59PM PST
Answer Grade: B Points: 5

We created Setup.exe by using Package and Deployment Wizard on Win98.

The relevant part of Setup.lst is

[Bootstrap Files]
[email protected],$(WinSysPathSysFile),,,3/26/99 12:00:00 AM,101888,6.0.84.50
[email protected],$(WinSysPathSysFile),$(DLLSelfRe gister),,5/31/98 12:00:00 AM,22288,4.71.1460.1
[email protected],$(WinSysPathSysFile),$(TLBRegis ter),,8/18/01 5:00:00 AM,17920,3.50.5014.0
[email protected],$(WinSysPathSysFile),,,8/18/01 5:00:00 AM,77824,3.50.5014.0
[email protected],$(WinSysPathSysFile),$(DLLSelf Register),,8/18/01 5:00:00 AM,106496,5.0.5014.0
[email protected],$(WinSysPathSysFile),$(DLLSelf Register),,8/31/99 3:55:00 PM,598288,2.40.4277.1
File7=@MSV

I executed Setup.exe on Win2K and got the message
sayint that some system components were out-of-date.
I responded with "Yes" for updating the out-of-date components.

However, the components were not updated.
The file modification dates and version numbers of the system component files in \WINNT\System32 were as follows:

stdole2.tlb 8/18/01 2.40.4517.0
ASYCFILT.DLL 8/18/01 5.0.21.34.1
OLEPRO32.DLL 8/18/01 5.0.4517.0

The application was correctly installed.

Thank you in advance.

Toshi
[email protected]


View Accepted Answer


If this EE solution does not provide the information you are looking for, you can signup as a member and ask your specific question of our 125,000 experts for free.
Question History
Accepted Answer from AlonHirsch 08/28/2002 12:16AM PST
Hi,

From Windows 2000 onwards, the system files can not be updated by user programs. These files are now controlled and maintained by the Windows Installer service.
This is to prevent accidental replacement or deletion of the system files.

The only way to update the system files is by installing a Service Pack or some other software from Microsoft that requires these files to be updated.

In order to prevent this error message from occurring on a Windows 2000 system, simply remove all the entries in the Setup.lst file under the BootStrap section.

HTH,
Alon
Comment from minoura 08/31/2002 05:20PM PST
The comment was very useful for us as we simply believed that the files in \WINNT\System32 should be updated.

The file vb6stkit.dll was still loaded to \WINNT\System32 on Windows 2000 Server.

On Windows XP, vb6stkit was missing, and it was loaded to \Windows\System32.

Thank you for your help.

Toshi
Comment from AlonHirsch 08/31/2002 11:59PM PST
You're welcome.

Glad I could help.
Alon