"Please close WinDbg before starting the game"???

[GrailQuest]

Was working fine this morning. Now when I try to launch, I get this message with Easy Anti-Cheat logo in the corner.

[Arrow]

I've been playing fine for hours, every day, since its release and had no issues but then after installing HWMonitor -- to monitor GPU/CPU temps (I was curious since I play on EPIC settings), it started doing the same thing as you @GrailQuest , after I rebooted my PC. So I uninstalled HWMonitor from CPUID and still problem persists. I then verified my steam files to any internal errors through the Steam Launcher, and that did not fix it.

Have you been able to resolve this?

Edit:

I just fixed it. I loaded command prompt as Administrator and typed in:

bcdedit -set DEBUG OFF

After doing this, I rebooted PC, and no more error. :)

[GrailQuest]

Originally posted by Arrow:

I've been playing fine for hours, every day, since its release and had no issues but then after installing HWMonitor -- to monitor GPU/CPU temps (I was curious since I play on EPIC settings), it started doing the same thing as you @GrailQuest , after I rebooted my PC. So I uninstalled HWMonitor from CPUID and still problem persists. I then verified my steam files to any internal errors through the Steam Launcher, and that did not fix it.

Have you been able to resolve this?

Edit:

I just fixed it. I loaded command prompt as Administrator and typed in:

bcdedit -set DEBUG OFF

After doing this, I rebooted PC, and no more error. :)

I got it a couple of times. Each time, I just rebooted the computer and tried again and the error did not appear. Really don't know what's going on. Maybe it's something Windows does but not always. And when Windows does it, it gets flagged by EAC?

[Arrow]

If data is written to the hard drive and Windows Event Viewer shows that there was bad block/sector that happened since the system has been turned on, the system could turn on WinDbg to attempt to debug the information to provide more error info on why/where the HD has a bad sector/block it attempted to write to. Other than this, I am not sure why it enabled itself for us.

I do know if you do have a log like that showing in Event Viewer, in elevated priveleged mode (Administrator) for command prompt and type the following in and let it run:

chkdsk /f /r

The chkdsk /f /r command checks the file system on the specified disk for logical errors and automatically fixes them (/f). Additionally, it scans for bad sectors on the disk and attempts to recover any readable information from those sectors (/r).

By doing this, it should reduce the chances of it happening again if this is what caused it.

[6aara]

having a similar issue except my error is "please close win10 before launching"

[Arrow]

Originally posted by 6aara:

having a similar issue except my error is "please close win10 before launching"

open command prompt as administrator, then enter:

sc query winio64
sc stop winio64


it's not Win10 but WinIO which is a capital i and the letter o capitalized instead of the numerical values 10.

You will want to make sure any external devices plugged in are not plugged in if it uses or runs software that utilizes the WinIO driver.


If it says the services does not exist or is not a installed service then this official solution to this problem won't help you and you'll need to likely contact support regarding this.

ps. its a problem that happens with games that uses easycheat, not the games themselves but easycheat itself.