[Error] Update Failed - Cannot Find The Warframe Executable!

[Kine_]

http://i.imgur.com/3ETVtdd.png

 

--

 

Clan mate of mine is having this issue each time he launches the game. Wondering if anyone else is getting this error too.

 

 

[RobWasHere]

Run as administrator?

[tantananan]

 

 

Happened to me once when I moved the installation directory of warframe to a different folder. Check the main install folder if it's in the same installation directory. Not the folder in appdata, the Main game directory.

Edited November 12, 2014 by tantananan

[Kine_]

Well this is interesting ...

 

http://i.imgur.com/tGV7PPt.jpg

 

this just happened to me too lmao

 

--

 

My clan mate uses the standalone on win 32bit so I decided to replicate. I am was launching via Steam on Win8.1 

 

1. Deleted Local Warframe content from Steam library

2. Manually deleted remaining Warframe folders and files

3. Cleaned up registry entries using reg scanner app

4. Restarted PC

5. Downloaded standalone Warframe from www.warframe.com

6. Installed to default installation path ( user/appdata/local/warframe )

7. Saw a line in one of the .log files mentioning that directory " Program Files x86/Warframe " does not exists

8. This log file or the reference to it no longer exist

9. Closed launcher

10. Restarted launcher in compatibility mode win xp (sp3)

11. Disabled bulk download + all other tick boxes except 'Aggressive download'

12. Completed the update and logged into Warframe for the first time.

13. Rebound my keys and Graphic settings

14. Exited Warframe

15. Ran Warframe launcher again and received that error message in screenshot

16. Exited Warframe

17. Opened up properties dialog box to the Warframe launcher desktop shortcut

18. Compatibility mode settings was not saved

19. Set compatibilty mode back to win XP (sp3)

20. Launched Warframe and all is well again

 

--

 

21. Exited Warframe

22. Turned compatibility settings off again

23. Received Error message upon next app launch

 

-- 

 

This error message was consistently reproduceable - launching the game in a different setting than it was initially installed in gave that error.

Edited November 12, 2014 by Kine_