Not really an answer, but a commiseration. Mfc42.dll has caused tons of trouble here at my company.<br><br>You are having a version conflict probably. My suggestion is this. Using windows explorer, find all copies of mfc42.dll on the offending machine. There will probably be one in the system (or system32) directory. That is probably your problem. Right click on the dll file and look at the properties. Check out the version number.<br><br>Our problem here is that we have an app that needs version 4.something, but newer software want version 6.something.<br><br>One workaround for us has been to rename the mfc42.dll in the system directory to something like mfc42V4.dll or mfc42V6.dll and then do the install. If the install is successful, see if the application created its own directory on your harddrive with other dlls. If it did, move the mfc42.dll there and rename the old one back to its original name. Many applications check their own directories first for dlls before checking the system directory.<br><br>Hope this gives you some ideas.<br><br>Kathryn