The latest version of FSLogix is experiencing problems with the  command: frx copy-profile

C:Program FilesFSLogixApps>frx copy-profile -filename d:tempProfile_test.vhdx -username test -size-mbs=30720 -dynamic=1 label=profile-test-verbose
User test” SID is “S-1-5-21-2971068368-244597684-1576390238-2601”
Volume Label: profile-test
Session count: 6
Found user:
Found user: 
Found user: test
Found user:
Found user:
Found user:
VHD not found. Creating…
Create success. Attaching…
Attach success. Getting physical path…
Get physical path success. Opening device…
Open device success. Initializing disk…
Initialize disk success. Getting volume name…

.
Formatting volume: \?Volume{5bc41fa6-5d2b-4389-99de-f4306343069c}
Format success
GetSecurityDescriptor success
GetDACL success
Set security success
Copying profile for user S-1-5-21-2971068368-244597684-1576390238-2601 to volume \?Volume{5bc41fa6-5d2b-4389-99de-f4306343069c}
Looking for Profile Path in registry
CopyProfileToVolume SID: S-1-5-21-2971068368-244597684-1576390238-2601 Volume: \?Volume{5bc41fa6-5d2b-4389-99de-f4306343069c} profileImagePath: C:Userstest
Exporting registry information
Export Profile registry data error: 0x00000001
Error copying profile (0x00000001): Incorrect function.

After downgrading to version 2.9.8612.60056, I was able to migrate the local profile. However, the command needed to be run twice because the first attempt resulted in an error:

Export Profile registry data error: 0x00000002
Error copying profile (0x00000002): The system cannot find the file specified.

​The latest version of FSLogix is experiencing problems with the  command: frx copy-profileC:Program FilesFSLogixApps>frx copy-profile -filename d:tempProfile_test.vhdx -username test -size-mbs=30720 -dynamic=1 label=profile-test-verboseUser test” SID is “S-1-5-21-2971068368-244597684-1576390238-2601″Volume Label: profile-testSession count: 6Found user:Found user: Found user: testFound user:Found user:Found user:VHD not found. Creating…Create success. Attaching…Attach success. Getting physical path…Get physical path success. Opening device…Open device success. Initializing disk…Initialize disk success. Getting volume name….Formatting volume: \?Volume{5bc41fa6-5d2b-4389-99de-f4306343069c}Format successGetSecurityDescriptor successGetDACL successSet security successCopying profile for user S-1-5-21-2971068368-244597684-1576390238-2601 to volume \?Volume{5bc41fa6-5d2b-4389-99de-f4306343069c}Looking for Profile Path in registryCopyProfileToVolume SID: S-1-5-21-2971068368-244597684-1576390238-2601 Volume: \?Volume{5bc41fa6-5d2b-4389-99de-f4306343069c} profileImagePath: C:UserstestExporting registry informationExport Profile registry data error: 0x00000001Error copying profile (0x00000001): Incorrect function. After downgrading to version 2.9.8612.60056, I was able to migrate the local profile. However, the command needed to be run twice because the first attempt resulted in an error:Export Profile registry data error: 0x00000002Error copying profile (0x00000002): The system cannot find the file specified.    Read More

​