When 32-bit apps try to access certain folders or registry keys in a 64-bit environment, they will be redirected to another path. For example, drivers are normally copied to C:\Windows\System32\drivers. When a 32-bit app tries to copy a driver to this location, it will redirected to C:\Windows\SysWOW64\drivers. This is probably what is going on in you case and so you will have to maintain 2 separate versions of your installer program. «_Superman_» I love work. It gives me something to do between weekends. Microsoft MVP (Visual C++) Polymorphism in C

First,thanks for your replies.I am sorry to you because I asked question in chinese. My question is as fllows. I recently created a driver installation program, which uses a number of core functions such as UpdateDriverforPlugAndDevice(), using vs2008, in 32-bit operating system everything is working properly. But win32 program can run in x64, but under x64 it does not work. For example UpdateDriverForPlugandPlayDevices() raises an error, I used GetLastError (), and I see an error code. Later I was using a 64-bit system with vs2008 and compiled the x64 program, everything works fine, but the program can not run in win32. The problem is now solved, but I now maintain two versions of the installer 32 and 64; I do not know what a better way, I just run a seperate version of the executable.

First,thank a lot for your reply.I have checked it as you said.But for winxp and win2000,the usage of function updateDriverForPlugAndPlayDevice() is same.