Not using sysprep, using Driveforge, not deleting the drivers folder, either. Source is USB or CD, destination is folder at root of local system drive. Today I found that by modifying the registry back to the %systemroot%\INF folder, then restarting, then rediscovering hardware after removing the yellow exclamation points, it discovered them correctly. I don't know why, it seems like DriveForge maybe installed drivers for the monitor that didn't work correctly, then the default INF just made it a plug and play monitor, maybe, and that was better or something. Also, IDK why driverforge leaving the default driver folder to the uncompressed drivers means that it can't recognize things as simple as a USB key w/o changing it back to the INF folder. Anyway, I can't really give the computer back to a client w/o switching the registry back to the INF folder, so that'll be cool when that tweak is done, IMO. tslug, which version of driverforge are you using ? kickarse is already working on solving the devicepath issue, so he will probably release it very soon. but if I am not mistaken he is also adding a couple of new improvement which could explain that the version has not been released yet. until then you can simply script the modification in the registry i.e. save devicepath status run driverforge restore devicepath I advise you to save/restore because in most of the cases you will have %systemroot%\inf but in some rare cases the device path might already contain different values.. so save/restore covers all cases Cheers, R.