belowaverage-org/SuperGrate

Failed to start / finish USMT, an un-known error has occured.

Closed this issue · 1 comments

Describe the bug
"Failed to start / finish USMT, an un-known error has occured" when migration is almost done and nothing is created in Store

To Reproduce
Steps to reproduce the behavior:
Capture a user's profile from a remote PC

Expected behavior
USMT to complete

Screenshots
If applicable, add screenshots to help explain your problem.

Logs
[VERBOSE]<21:44:52> 2024-01-24 21:44:51, Info [0x000000] Success, 37 errors ignored. See the log for more information.[gle=0x00000091]
2024-01-24 21:44:51, Info [0x000000] USMT Completed at 2024/01/24:21:44:51.690[gle=0x00000091]
2024-01-24 21:44:51, Info [0x000000] ----------------------------------- USMT ERROR SUMMARY -----------------------------------
2024-01-24 21:44:51, Info [0x000000] * One or more errors were encountered in migration (ordered by first occurence)
2024-01-24 21:44:51, Info [0x000000] +-----------------------------------------------------------------------------------------
2024-01-24 21:44:51, Info [0x000000] | Error Code | Caused Abort | Recurrence | First Occurence
2024-01-24 21:44:51, Info [0x000000] | 395 | No | 37 | Read error 395 for C:\Users\lcarroll\OneDrive - Gilead Sciences\Desktop[244507252_402261131336283_7773709582088968574_n.jpg]. Windows error 395 description: Access to the cloud file is denied.
2024-01-24 21:44:51, Info [0x000000] +-----------------------------------------------------------------------------------------
2024-01-24 21:44:51, Info [0x000000] 37 migration errors would have been fatal if not for /c. Please set log verbose level to at least /v:1 for details

[ERROR]<21:44:53> Failed to start / finish USMT, an un-known error has occured.

[INFO]<21:44:56> Removing USMT from CCPC6P1MNR3...
[SUCCESS]<21:45:38> USMT removed successfully.
[INFO]<21:45:38> Done.

IMPORTANT

To retrieve the logs, click "File", the select "Save log..." Copy the contents of the log file and paste it here.
Refrain from copying and pasting the log from the console since it does not output verbose information.


**Additional context**
It does work well but looks like it cannot be completed. If it has to do with the numbers of errors (37) ignored because of /c, 
then how to exclude One drive from migration?. Thank you

Unfortunately I'm getting the same issue over and over, primarily on Windows 10 computers. Windows 11 backup seems to work --- I haven't tried a restore just yet.