Scanstate and Loadstate Ignore Environment Variables in INF Files (283367)



The information in this article applies to:

  • Microsoft Windows XP Professional

This article was previously published under Q283367

SYMPTOMS

When you perform a migration with the User State Migration Tools by using environment variables such as %systemdrive% or %homedrive%, Loadstate or Scanstate ignores the variables in INF files and the files are not copied as expected.

CAUSE

The environment variables %systemdrive% and %homedrive% are not read by Loadstate or Scanstate when the variables appear alone in customized INF files.

RESOLUTION

The actual drive letter must be included instead of the environment variable, or the specific file name must be included with the environment variable.

The following examples work:

C:\filename.txt

and

%systemdrive%\filename.txt

The following examples do not work:

%systemdrive%

or

%homedrive%

STATUS

This behavior is by design.

Modification Type:MinorLast Reviewed:1/15/2006
Keywords:kbenv kbprb KB283367