Game Will Not Launch

[BickyBence]

Everytime I hit the play button in the launcher the game begins to load and then the engine just crashes! Need HELP!

[Texnoz]

You're not getting any error reports either?

Just a crash?

[BickyBence]

I get an error report that says the engine has crashed thats all

[Texnoz]

Try updating/reinstalling/repairing your DirectX.

[Isirius2Dragons]

I'm new here, Just downloaded and game opened and I started playing and discovered mouse way to sensitive. Game froze as I was killed so I had to go to desktop to close game. I tried reopening Launcher and it comes up and starts searching for updates, then throws up this error message.

Update failed!

Could not create file:

C:\Program Files (x86)\Warframe\WarFrame\Downloaded\Public\Warframe.exe.tmp

Access is denied. [0x00000005]

I am running Windows 7, on AMD Dual core CPU, And AMD Radeon 6320 Graphics

EDIT

Maybe if I copy paste above file into my Warframe files but which folder do I put it in or do I make a new folder with above name?

Edited April 2, 2013 by Isirius2Dragons

[Texnoz]

• 
  When clicking the Verify Connection button, the Agent runs the following flow against the Remote Windows machine, on which the Monitored Instance resides:
  
  • Access to the Windows Registry
    
  • entering to the WMI component
    

  -- This path is required in order for the Agent to get the needed data it requires to be configured.

  -- The OS user used in the Agent must have the required permissions to access the remote Windows Registry and WMI.

  -- Lack of permissions, will yield with error messages.

  -- Two Registry keys should exist and have the right permissions (as described in the solution section below)

  • HKEY_CLASSES_ROOT\CLSID\76A6415B-CB41-11d1-8B02-00600806D9B6
    
  • HKEY_CLASSES_ROOT\CLSID\76a64158-cb41-11d1-8b02-00600806d9b6
    

  [*]

  In this solution we will focus on checking and enabling OS user permissions over Windows Registry.

  Only when the OS user can access Windows Registry, it will be able to follow to the WMI component later on.

  Check if the required Windows Registry keys exist

  Two registry keys MUST exist prior the Agent can OS connect through WMI:

  • HKEY_CLASSES_ROOT\CLSID\76A6415B-CB41-11d1-8B02-00600806D9B6
    
  • HKEY_CLASSES_ROOT\CLSID\76a64158-cb41-11d1-8b02-00600806d9b6
    The difference between those keys is the first string, where 76A6415 B is different from 76a6415 8(the letter B and the number 8).
    

  If, for some reason, one of the keys or both doesn't exist, the solution would be to export the key/keys

  from an identical platform where the key exists, and import the Registry key to the desired Monitored Host.

  Both Windows boxes (the one with the key and the one without) should be installed with the same Windows OS and platform.

  Set Permissions over the Registry keys

  Repeat the below procedure TWICE, once for each key:

  • Login to the target host as an Administrator
    
  • Open Start > Run and type Regedit
    
  • From the Find menu, search for 76A6415B-CB41-11d1-8B02-00600806D9B6 class ID (should be under HKEY_CLASSES_ROOT\CLSID\76A6415B-CB41-11d1-8B02-00600806D9B6)
    
  • Right click on this item and select Permissions
    
  • Click Advanced
    
  • Select the Owner tab
    
  • In the Change Owner to...box, highlight the account you are currently logged in as.
    
  • Click Ok
    
  • Click Ok
    
  • Right click the registry item again and select Permissions
    
  • Highlight the Administrators group
    
  • Give Full Control permissions to this group by checking the Allow box
    
  • Click Ok
    
  • Repeat the above steps for key 76a64158-cb41-11d1-8b02-00600806d9b6
    

  Run verify Connectivity again

  Check the Agent after the keys are in place and permissions are granted, by clicking on Verify Connectivity link.

  If the above doesa not fix the problem please:

  1. Go to Administration | Agents | Agent Status under Dashboards

  2. Select the database agent with the issue.

  3. Click Edit Properties

  4. Click Modify the private properties for this agent

  5. Under OS-Monitored Connection Profile change the setting for WMI-Technology to Ntaive

  6. Click Save

  7. Click Back to Agent Status

  8. Click Deactivate

  9. Click Activate