Has anyone else had the issue where adding a ‘Default Icon’ (Edit->Project Settings->Player) causes the build to hang on starting?
If I build without an icon everything runs fine, but when I build with a ‘Default Icon’ set it hangs when I double click on the game icon (doesn’t lock up the pc, it just sits there indefinitely trying to load).
Just a quick update…It seems like after building with the new icon I then can’t delete the files associated with that icon. I can delete the data files associated with the build, but not the exe that actually has the icon attached to it. Its in use by ‘System’, and rebooting doesn’t even break the lock.
Creating a build with no custom icon has no issues though, it runs/can be deleted fine.
We tried building empty projects only with icons at Unity versions: 5.0 beta was ok ; 5.2.3 with icon it doesn’t work, 5.3.0 beta it never works(with icon or not).
Worth to mention → It doesn’t happen on every PC. At 12 PC’s we have at company. The problem occours only on one. Though customers who bought our game are experiencing same problem(process is stuck, and the game doesn’t start), which is really problematic for us.
Even if we build project without setting icon in Unity Editor, and then add icon using 3rd software program it stops working. (though it works without a problem before setting up icon).
Bump. I also have this problem. Build completely hangs and locks up after compiling with an Icon. Withouth it, there is no problem. I can’t even delete the .exe and can’t kill it (not even with ProcessManager in Win10 after 3-4 reboots)…
What is the cause of this? Faulty drivers? Something Unity related?
I’ve been searching for a solution to the “hang on start” issue that just appeared out of nowhere. It happens just the way you describe it also, with the system hang ups, the restarts, and all. I’ve already had an icon attached to the project so I never made the connection, but I just now noticed this post and figured I’d see what your problems where. Turns out it is my problem as well as I just deleted the icon from the project and the exe works just fine now (at least once).
I fixed this once by creating a new project and importing all my assets. It built and ran just fine a few times but then the error appeared again.
I first encountered this issue while trying to run a build of somebody elses game which was made pre-Unity 5, so I wonder if it is a Windows/Hardware issue?
Specs:
Sapphire Radeon 7950
AMD Vishira 6300
Windows 7 Home Premium SP1
Same issue/bump, I just discovered this was the issue after the build “happened” to not apply the custom icon for some reason. I was able to confirm this was the issue by removing the custom icon, re-building (success), adding the custom icon again, re-building (failure).
The failure behavior is exactly as described. The file explorer window “hangs”, the .exe and it’s data file are “in use by System”, even though there’s no corresponding program in the Task Manager (or it’s Details pane) that I can discern. This is only remedied by a full restart.
No custom icons for now, which isn’t a huge deal. But the bug itself (and identifying it ) is quite a huge deal and a pain.
@jamnoon I doubt it’s hardware, I think it’s just Windows 10 related. The playtesters for my game had the same issues and I did on my development machine, and I doubt we have the same hardware.
Same issue. If I use any custom icon the build will not work. If I do not use one the build runs.
This is not a windows 10 or 7 issue this is a unity issue.
(I’m on windows 7)
This is still a massive issue I’ve been having, and it took me literally months to actually figure out that this is what was causing it. It happens with every single project I make, if it’s got an icon the build hangs, and I have to restart my computer to delete the old build. So I think a bump is definitely in order.
I encountered this issue originally on Windows 7. Now using Windows 10 but having same problem. Other posters have said they are having this issue on Windows 7 too.
We have seen this one last year on two machines with Windows 8.1 - but we thought this was fixed by Unity as the latest builds with icons worked on these machines. Now we have seen a refund on Steam with this reason. It is a really annoying issue as the player can only shut down the PC. So the impression of players who have the problem, is that our game has a bug when the problem lies with Unity.
Hi all, I’m going to look into this. I see one reference to a bug in this thread (from @rmshr ), I’ll see if I can find it. Anyone else with reproducible cases, please submit bugs and send me the numbers.