This is a backup copy of Spartan117H3's guide to allow for VMware to run Nexon games.

The original can be found here:

Connfirmed to work on VM OS(Host OS does NOT matter):Edit

Windows XP Professional SP3 32 bit

Windows 7 Ultimate 64 bit

My SpecsEdit

(Someone requested this, so here)

  • i7 930 overclocked 1.35v @ 4.2GHz (22 Idle, 67 load.)
  • Asus P6X58D-E Motherboard
  • ATI Radeon 5850 @ Stock
  • 16GB Mushkin Blackline DDR3 Ram 1600 9-9-9-24
  • 120GB Corsair Force SSD Sata II
  • 500GB Seagate Barracuda 7200 RPM
  • Antec 750W TruePower PSU
  • Asus 25.5" Monitor 1920 x 1200 Res

VMWare Workstation 7.1.3-324285 using Windows XP Professional SP3(Upgraded to Workstation 8 with no issues/using same VM's created in v7.1.3).

My VM Settings PER VMEdit

You probably will need 2 gigs of ram and possibly 2 cores instead of what I have

VM settings PER VMEdit

1 virtual core/1gig of ram, 15 gigs of HDD space.

This allows me to go into Ch 1 FM 1 with minor entrance lag, otherwise it's fine.

Step OneEdit

Find the .vmx file in the HOST OS.

My VM is named "Windows XP Professional" so my .vmx file is called "Windows XP Professional.vmx". If you don't know how to find it, read below:

VMWare Workstation Users (PC Users)Edit

Find the .vmx file in the location you installed the original VM into.

If you don't remember where you installed the VM into, go to Edit->Preferences and look at the "Default location for virtual machines and teams" and it will show you the path to your VM. Then open it with a text editor such as notepad.

VMWare Fusion (Mac Users)Edit

  • From Fusion's menu bar, click Window > Virtual Machine Library.
  • In the left column, Ctrl+click the virtual machine and click Show in Finder.
  • Ctrl+click the revealed package (ending in .vmwarevm) and click Show Package Contents.
  • Ctrl+click the file ending in .vmx and choose Open With > Other.
  • Navigate to TextEdit and click Choose.

You can now add or edit lines lines as needed.

VMWare Player (Non Workstation/PC Users)Edit

Look for ".VMware virtual machine configuration" instead of ".vmx".

You find this most likely in etc/vmware

Step TwoEdit

Add the following line to the bottom of the list.

monitor_control.restrict_backdoor = "true"

Once you are done, save and close the .vmx file.

Step ThreeEdit

Power on the virtual machine and (INSIDE the Virtual Machine, not the host OS) go to Start, Run, Regedit and go to this directory:


Step FourEdit

Once you have the folder "0000" highlighted, right click "DriverDesc" and click modify.

Once you have done that, erase the value data (On Windows XP SP3, mine was named VMWare SVGA II) and click ok.

On Windows 7, it should be VMWare SVGA 3D or something along those lines.

Errors you may haveEdit

  • Error: Themida - Sorry this application cannot run under a Virtual Machine.

This error is caused by not doing Step 2.

  • Error: Maplestory - error: (bunch of numbers). This is an error that occurs when there's an unknown problem.

This error is caused by not doing the registry edit properly and/or not finding all of the proper values.

  • Error: Dictionary Error

Re-read step 2.


If you still get the Themida error and are using Windows 7 64 bit, Ctrl+F "DriverDesc" and find all the values for it and delete them (I did not need to do this/you may have to if you have multiple profiles).

If you STILL have problems, uninstall VMWare Tools INSIDE the VM by clicking Start and typing in "Add and Remove Programs,"(If you're using XP, Start->Control Panel->Add and Remove Programs) clicking  Durka VMWare Tools, then clicking uninstall, and Ok.

Restart the VM and try again.

If you get any Hackshield related error, make sure your installation of Maplestory is proper or reinstall it just to make sure. Durka

Known Bugs/IssuesEdit

VM'ed Maple does lag a lot more than if you were to run it on your host operating system.

There isn't any way around it as far as I know as it is on Nexon's end as it didn't use to lag as bad as after they started scanning to see if Maple was being run in a VM.

You must bear with it if you're going to use this fix.

Full screen alleviates some of the lag, and I believe Mac users don't have that big of an issue when VM'ing Maple.

Speed-hack may pop up some times depending on how solid your processor is.

If you have issues with it, force a constant voltage and turn off CNQ or Speedstep in the BIOS.