Files are not exchanged when Windows Server 2003 restarts if you use the MoveFileEx function to schedule a replacement for some files

SYMPTOMS:

Consider the following scenario. In Windows Server 2003-based PC, you can useMoveFileEx plan for replacement of some files. However, these files are not exchanged when Windows Server 2003 reboot if the following conditions are true:

• The System volume is a basic volume.
• The destination drive or the source drive is placed on a dynamic volume.

CAUSE:

This problem occurs because the Session Manager (smss.exe) PendingFileRenameOperations the value processes, and the system restarts. In some unusual circumstances, when the Session Manager processes the PendingFileRenameOperations value, the drives are not available for the system. The drives do not exist because the volumes are not mounted at that time. Therefore, the processing of the PendingFileRenameOperations no value and an error is not reported. The reason that the installation process is not completed during the restart is that the system disk is an essential volume. Therefore, loading the driver for the dynamic volumes may be delayed because loading the driver is not necessary during the restart.

WORKAROUND:

Warning

Serious issue might happen if you change the registry wrongly by using Registry Editor or by using a different technique. This issue might want that you reinstall the operating system. Microsoft cannot assurance that this issue can be resolved. Change the registry at your own risk.

Follow these steps, to modify the startup type value to "0" for the DMBoot driver.

1. situate and then click the following registry subkey:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Services\dmboot

2. In the details pane, double-click Start, and then type 0.