title: Android Studio 3.1.1 (AVD) emulator doesn't start
body: <p>I'm running:</p>
  
  <ul>
  <li>Windows 10 Enterprise 64-bit (Version 1709) (Build 16299)</li>
  <li>Intel i5 4690K</li>
  <li>16Gb Ram</li>
  <li>Nvidia GeForce GTX 970</li>
  <li>Bios Intel virtual accellaration and HAXM (in android studio) are activated</li>
  </ul>
  
  <p>---- As far as I can say all drivers are up to date. ---</p>
  
  <p>I just ran through following steps:</p>
  
  <ul>
  <li>Installed - jdk-9.0.4_windows-x64_bin.exe</li>
  <li>Adjusted Java PATH variable in Windows and checked with "cmd --> path"</li>
  <li>Installed - android-studio-ide-173.4697961-windows.exe</li>
  </ul>
  
  <p>Android Studio runs fine but whenever I try to start a virtual device i get following error messages:</p>
  
  <p>See this picture for a first error message -->
  <a href="https://i.stack.imgur.com/UB6wC.png" rel="nofollow noreferrer">Android Studio error message</a></p>
  
  <p>I already tried out x86_64 CPU architecture but it didn't work either.</p>
  
  <p>Then I found out more error messages using emulator.exe in command prompt.
  See -> <a href="https://i.stack.imgur.com/sW9tw.png" rel="nofollow noreferrer">Command prompt error using emulator.exe</a>
  Sorry for the german error message here a brief translation:</p>
  
  <ul>
  <li>"The procedure jump in point "_ZN10QByteArray14trimmed_helperERS_" was not found in the DLL "C:\Users...\qemu-system-x86_64.exe"</li>
  </ul>
  
  <p>When I start the file emulator-x86.exe I receive following errormessage:
  <a href="https://i.stack.imgur.com/rrklM.png" rel="nofollow noreferrer">Errormessage using emulator-x86.exe.</a>
  The showed file is not the only one it claims being missed. In summary it complains about:</p>
  
  <ul>
  <li>libwinpthread-1.dll</li>
  <li>Qt5Svg.dll</li>
  <li>Qt5Core.dll</li>
  <li>Qt5Gui.dll</li>
  </ul>
  
  <p>I can ensure you the files do exist</p>
  
  <hr>
  
  <p>By now I found out following workaround:</p>
  
  <ul>
  <li>emulator.exe -avd "virtualdevicename" -force-32bit</li>
  </ul>
  
  <p>I've got following requests:</p>
  
  <ol>
  <li>I could live with the workaround. But then it would be nice having that -force-32bit parameter being set in the android studio so I'm not forced to start the virtual device via command prompt each time. How to set that up?</li>
  <li>Better would be fixing the initial error. I searched for the errormessages but found nothing helpful till now.</li>
  </ol>