Forum Discussion
11 Replies
- EA_David9 years ago
Community Admin
@swampy197728 Hey, can you try repairing the game and see if that helps? Right-click the game panel to get the repair option.
If the issue persists, have you restarted your system since this started happening? perhaps there's a failed "ghost" process for the game in your task manager. A restart might help in any case.
Cheers. Hi,
I tried both options but without any luck.
I can see that in Processes only activation_ui starts.
Thanks,
Marek
- crinrict9 years agoHero+
Try if it starts if you do a clean boot: http://help.ea.com/en/article/how-to-clean-boot-your-pc/
I have the same issue. No error - nothing. The only thing that might be out of the ordinary is that I installed the game on my D: drive.
- crinrict9 years agoHero+
Did you try a clean boot as suggested above ?
Hi crinrict; yes, I did and unfortunately nothing changed.
- crinrict9 years agoHero+
Could you check your event manager if that gives you any unravel errors ?
I assume you also repaired the game ?
Thanks for the suggestion; unfortunately I couldn't find any errors in the Windows Event Viewer. I've also tried repairing the game multiple times, but nothing.
I'm happy to say that I can finally play Unravel although I cannot say if it was the Windows 10 Anniversary Update or the latest Origin beta (10.0.1.18416 - 477168) or both.
SO fun fact, two years later, this exact issue is still ongoing for some people who just purchased the game. What I'm seeing as an issue is that the game is attempting to activate through EA using that .exe file, incapable of resolving the EA account associated with Origin, and immediately kicks you back out before the game can load. The way I discovered this? I completely removed my internet connectivity options and quite suddenly the activation window actually APPEARED and asked me to LOG IN to verify activation of the game. Given that I had no internet capabilities on that clean boot run I couldn't.
Returning internet capabilities and now the activation window doesn't even appear, and the same results happen. So. There's a different underlying issue here beyond windows and updates.