Windows 10 compatibility

So I purchased Automation early access, and I have windows 10. I am having problems with the .net framework that was installed with it. Is there a way to run automation on windows 10?

Here is the message.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.DirectX.Direct3D, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. The system cannot find the file specified.
File name: ‘Microsoft.DirectX.Direct3D, Version=1.0.2902.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’
at Automation_Launcher.Optionsform.HasAnyValidResolutions()
at Automation_Launcher.AutomationLauncherWindow.Form1_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

************** Loaded Assemblies **************
Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

Automation Launcher Steam
Assembly Version:
Win32 Version:
CodeBase: file:///C:/Program%20Files%20(x86)/Steam/steamapps/common/Automation/Automation%20Launcher%20Steam.exe

Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/

Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/

Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/

Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Xml/

Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/

Assembly Version:
Win32 Version: 2.0.50727.8662 (QFE.050727-8600)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Configuration/

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the section.
The application must also be compiled with debugging

For example:

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Can someone please help me?

If it is installed correctly, try this.

I had no problem with windows 10 and Automation. All my games were laggy as crap at first, but one time when Automation crashed on me when I was trying to play, I started it up again and my fps went back to normal.

I’m not having any issues with Automation on Windows 10 either, everything’s been fine from the beginning.

Well, others have had some problems running Win10. The link I posted shows a nearly identical error involving Direct3D in Win10, running Automation. Killrob posted a link to Steam forums with a post from Caswal, which solved it for that user. I think it will solve it for this user as well, but they have not responded yet (that I can tell).

It works for me.