I've also seen this behavior in Windows Vista. The work-around is to right-click on the DX4Win application and select the checkbox to force the program to run as Administrator. This causes DX4Win to work as expected.
Regards, Rich Eckman (KO4MR) Hampton, VA
