Moving file failed...

Unity Engine
1

Hi,

I started trying 2019.3.0b6 for development, and I’m getting a lot of “Moving file failed” issue.
This is where Unity comes up with a dialog with [Try again] [Force quit] options.
I haven’t seen this since early 2018 builds…

Looks like this, but it’s always a different file

Start importing Assets/Scripts/Game/MetaGame/MetaGame.cs using Guid(51f33f5d83cd72345a89b3b450e51578) Importer(-1,)
Force Quit pressed for Moving file failed: Moving E:/Work/Project.2019.3/Temp/UnityTempFile-eb5aba1f7aca71c438ea018622a3d06a to E:/Work/Project.2019.3/Library/TempArtifacts/Primary/51f33f5d83cd72345a89b3b450e51578: The system cannot find the path specified.

Last time it was ProjectSettings/ProjectSettings.asset …

Does anyone see this, or is it just me or our project?

2

I see this pretty much every time i trigger a build, that something can’t be moved from staging to the output directory. I thought this was a local problem on my end, but perhaps it’s not. Then I can just press “Retry” in the error dialog and it works.

3

I usually get those prompts when some Windows Explorer window in the background points to one of the /Temp folders ( essentially where the temporary output/staging happens )

3 Likes
4

It is still happening in 2019.3.0f6
Just occurred 4x in our team withing and our

5436984--554133--upload_2020-2-3_11-23-28.png

After Force Quit, Unity crashes 100% on the next restart:

0x00007FF7ECD2DD21 (Unity) IsMetaInfoSame
0x00007FF7ECD32CBE (Unity) RefreshInternalV2
0x00007FF7ECD35331 (Unity) StopAssetImportingV2
0x00007FF7ECD2C816 (Unity) InitialScriptRefreshV2
0x00007FF7EC296501 (Unity) Application::InitializeProject
0x00007FF7ECBF0648 (Unity) WinMain
0x00007FF7EFB6C602 (Unity) __scrt_common_main_seh
0x00007FF8BB8C7BD4 (KERNEL32) BaseThreadInitThunk
0x00007FF8BC7ECED1 (ntdll) RtlUserThreadStart

After the 2nd restart Unity starts again

5

Oops, it was an error on our side.

Our version control tool aggressively deletes empty folders and it deleted the Library/TempArtifacts folder…

3 Likes
6

For me, it was either that, or the Remove Empty Folders option under Assets menu. I both disabled that and quit SourceTree, and then it was fine. (I was trying to use “MeshBaker” asset, just in case somebody searches it up)

7

Look for multiple instances of UnityHub and or Unity Editor running in the background. That fixed it for me. For some reason there were 5 Unity Hubs running

6 Likes
8

I also just had that issue and it helped to just close Visual Studio and try again.

7 Likes
9

Thanks Wiechciu

Just close Visual Studio. Worked for me! Thanks your my Hero of the Day :smiley: