The asset failed to save

[Rob_McLachlan]

Another year, another time this has happened to me! This time the other Unreal Engine instance was hidden in ‘Background processes’ in Task Manager.

[ItsYoungFox]

Hah! i created two desktop window and had ue4 running in both :rolleyes:

[anonymous_user_806b6da4]

I had this same issue, a Static Mesh asset was failing to save and it was a problem I dealt with for ages.

But, I solved it by saving and exiting unreal (leaving the problem file unsaved). Then, I just opened Task Manager and closed all instances of Unreal.

This solved my problem, hope it helps!

[RabbitHoleAvert]

@Rob_McLachlan

Another year, another time this has happened to me! This time the other Unreal Engine instance was hidden in ‘Background processes’ in Task Manager.

Thanks for noting that. I had closed down everything and it didn’t help. Seeing your message, I looked in “Background Processes” and bingo

[ZcheK]

I had another UE4 running in processes but not showing. Shut that down and it could save. The risk was I didn’t know which was the ‘bogey’.

[gothicserpent]

this happened to me.

after i restarted the computer, it worked. if anyone has the failed to save error.

[Xenovore]

This happens ALL the time, mostly because the editor is too slow to provide feedback (i.e. the splash window) about whether the project is actually loading. We really need (at the very least) the option to say “Load only one UE4 editor instance”. This would also be helpful if a developer’s system only meets the minimum requirements – don’t need yet another instance of UE4 eating up memory and HD bandwidth.

And realistically, maybe it’s about time Epic spends some time on an optimization release, instead of another feature release… UE4 seems to just get more sluggish with each new release; e.g. 4.21 loads noticeably slower than 4.18 on my system.

[max201218164]

Me too, so thanks

[anonymous_user_28fe00231 (anonymous_user_28fe0023)]

Dude what the hell, i had the same problem it does not even show another Unreal Engine tab on the taskbar needed to close it from the TaskManager in order to really close it. But it worked eventually

[Daemontrack]

For me the saving assets was failing because of a completely different reason. Realized, I had a space in my folder name. Removing the space solved it for me!

[roberteker (RobertED)]

This just happened to me as well. Is there a setting to prevent multiple instances of the Unreal Editor to launch?

[Zoned.Dev]

Thankyou so much! I did the exact same thing. My map wouldn’t save and it was freaking me out, didn’t realise I had accidentally opened up two instances of the editor.

[mvollrath]

Also got duped by the double editor instance and this helped me. Thank you!

[anonymous_user_b1499ca2]

Help me out, please! UE4 4.23.1(from EGS launcher) [HR][/HR]
I do check twice, I have only 1 instance of UE4 running in the Task Manager.
I tried to reboot the PC, but nothing happens.

Steps on how I created the project:
I created C++ => Basic Project => No Starter Content.

The Only way to fix it was to change Read-Only for Map folder. I did this for all Content Folder(To avoid it in feature). [HR][/HR]

But I am sure that it is not the best way to do it!

[Nawrot]

@Rob_McLachlan

Another year, another time this has happened to me! This time the other Unreal Engine instance was hidden in ‘Background processes’ in Task Manager.

Just like old rimes, but then we had white viewport error.

[Ion_Cocarcea]

It happened to me too, but you can run the Engine with admin rights and check if you have one more instance in task manager of the same project. Also check if the file is not readonly. And it will work fine.

[rit]

Thank you so much!

If not for this post, I might be wasting a whole afternoon trying to debug my project.

[zerowjj]

hahaha, the same

[Manim8]

@anonymous_user_595f74f21

Oh Unreal Engine is lot more SNEAKIER than that. Sometimes, it will open a second copy of the editor without showing any icon up at all on the Task Bar
but it shows it instead as a process running silently in the background in the task manager. I’ve had that happen a few times to cause the asset save error.

Then you have to shut that process down, and relaunch, for sometimes the menu launcher don’t launch when its got a copy of the editor running in the background.

WOW. That is what my problem was! I thought my file was corrupt and was like “NOOOOOOO”. It started with 1 static mesh that I re-imported. Then another. Then if I made a change to an existing asset Blueprint, it failed to save that too.
Read through this thread and nothing was working until I saw this and checked my Task Manager and saw it! The sneaky little rascal. I ended the process and relaunched - BOOM! It now works! Very strange that this happens though. Unreal needs to look at this.

[Etchano]

@anonymous_user_9c2a9a99

OK, I think I discovered what was wrong. It turns out that I had accidentally launched the editor twice (it was waiting at the dialog box saying I had files open in the last session, and asking did I want to reopen them).

Perhaps the launcher could check for this and prevent it (or at least, ask if its what you really meant) since this doesn’t appear to be a very useful mode of operation.

Had the same issue today! And you saved the day hahaha