Unable to launch!

[weiyong95]

Hi i recently downloaded the game. when i press start on the launcher the game wouldnt load. any idea to fix?

im using win 10 !

[MrEz98]

This post should be post in Technical Issue section.

Btw, here.. try read this forum for that problem

http://forum.dragonnest.com/forum/su...ame-wont-start

[Gaming_Boy]

Hi ThreadStarter(TS),

First off, you should be posting on the correct section called "Technical Issue".

Back to topic,

There are a 2 solution that you might want to try to fix this issue:

1. Restarting your computer (Recommended)
2. Modifying the "Windows Security Settings" (Not so recommended[Do at your own Risk])

---

Solution 1. Restarting your computer (Recommended)

This is a basic thing you can do when your computer is not working as it's expected.

Step 01:
Click your Start Menu Icon located on your Taskbar

Step 02:
Click the Power Button and select "Restart"

Step 03:
After your computer restarts, try Launching "Dragon Nest" again.

---

2. Modifying the "Windows Security Settings" (Not so recommended[Do at your own Risk])

This has its risk, it won't make your computer explode but it can make your computer more vulnerable to threats. Thus, it is not so recommended but has a higher chance to fix the issues mentioned.

I recommend switching the settings back to its Default Settings once you played Dragon Nest.(For some people, they need to do this ONCE and it solves their issues permernatly)

Disclaimer: I'm not liable if your computer got infected by threats. DO SO AT YOUR OWN RISK!


Step 01:
Click your Start Menu Icon located on your Taskbar

Step 02:
Type this "Exploit Protection" and click

Step 03:
Here you need to disable 2 security options namely:
- Data Execution Prevention(DEP)
- Validate Exception Chains(SEHOP)

Step 04:
Restart your computer(DO NOT SHUTDOWN OPTION! USE RESTART)

Step 05:
Try launching "Dragon Nest" again


NOTE: After playing DN, please revert back the settings to its default state for more security!

[Gaming_Boy]

Additional Notes: From what I've seen so far, most people got this issue once they updated their Windows to the latest Build.