When does this happen - at the beginning of the setup or later on?
If at the begining, then the files in question are listed in the bootstrap section of your SetUp.Lst file and are system files. These files are newer than the ones on the receiving PC. But they cannot be simply replaced because the are locked and continuously in use by the OS.
First, make sure you are using Service pack 4 or 5 for VB6.
Then, easiest way to correct the problem is to update the receiving PC OS with a Service pack that is newer than, or equal to, the Service pack for the VB SP that you are using and newer than the OS Service pack of the system that the set-up was made on.
Sometimes another process running in the background causes this, such as a printer manager.
I have this problem with files like the MFC42.DLL and usually get by with de-selecting this file from the set-up list. However, some other components may then error out when registering during set-up. If you see this then you need toeither end the process, removing it from the auto start AND INI files, so it doesn't get restarted again during the reboot, causing the same problem again, or, simply install the most recent Service Packs on both systems.