An Xcopy thread is just what I needed. My problem is different though, as I cannot get xcopy to run at all, it just skips to the next install. I call a .cmd file from RunOnceEx.cmd to copy the i386 directory to the hard drive. I don't want to use drive lettes as they may change so I've set it up like: RunOnceEx.cmd cmdow @ /HID @echo off IF EXIST D:\CD.txt set CDROM=D: IF EXIST E:\CD.txt set CDROM=E: IF EXIST F:\CD.txt set CDROM=F: IF EXIST G:\CD.txt set CDROM=G: IF EXIST H:\CD.txt set CDROM=H: IF EXIST I:\CD.txt set CDROM=I: IF EXIST J:\CD.txt set CDROM=J: IF EXIST K:\CD.txt set CDROM=D: IF EXIST L:\CD.txt set CDROM=E: IF EXIST M:\CD.txt set CDROM=F: SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY%\001 /VE /D "Copying i386 Directory" /f REG ADD %KEY%\001 /V 1 /D "%systemdrive%\install\i386copy.cmd" /f i386copy.cmd rem cmdow @ /HID @ECHO OFF %systemdrive%\windows\system32\xcopy32.exe %CDROM%\i386 /e /k /h /i /y %systemdrive%\i386 The registry entries appear normal, i386copy.cmd is called, but xcopy dosn't run. If I run i386copy.cmd by just launching it, it works fine every time, but not when called from RunOnceEx. Any ideas? Oh, if I put the xcopy line directly in RunOnceEx.cmd and have xcopy execute from the regisrty it does work but shows the command window. I want to keep it clean looking during the install. Thanks, -Mike