main thread doesnt resume once ollydbg attaches

[namreeb]

After the thread created by OllyDbg exits as I attach to WoW.exe, the main thread never seems to resume for me, even if I use Olly to try and force it.

Has anyone else experienced this, or even better identified the cause?

[FenixTX2]

Isn't this because Warden has detected Olly's debugger?

[ramey]

After the thread created by OllyDbg exits as I attach to WoW.exe, the main thread never seems to resume for me, even if I use Olly to try and force it.

Has anyone else experienced this, or even better identified the cause?

64bit Windows? I dunno really

Isn't this because Warden has detected Olly's debugger?

No. Jesus christ, please stop assuming shit yourself and bringing it online. WoW or Warden doesn't check for any debugger.

[namreeb]

Sorry, I should have said that initially. It is Vista Ultimate x64.

[ramey]

Sorry, I should have said that initially. It is Vista Ultimate x64.

Yeah, I have the same problem. I've just been way too lazy to really care and check it up.

I looked at it a bit, only for a minute or so, but it seems related to the fact that Ollydbg is 32bit and 64bit is not supported, nor is there a 64bit version of Ollydbg! Lame, but oh well =x

[namreeb]

*blush* I answered my own question. Installing the Olly Advanced plugin seems to fix the problem. OpenRCE

Virustotal. MD5: e91643573c44fea4494ce52fa3399ec1

[MaiN]

Actually, I'm using OllyDbg from Windows 7 64-bit and Windows Vista Ultimate 64-bit, and it works well.
I don't really do anything special other than making sure it's running as admin.

[namreeb]

Not altogether surprising. Are you attaching or running from Olly? I saw lots of forum posts around the webs about people with this problem, but just came across this solution. *shrug* it fixed the problem for me.