X64dbg: update the launcher to be more intuitive

[amn]

x64dbg presents a cryptic error message telling me "RegCreateKey failed" and presumably aborts process after that.

I have no intention to run the tool with Administrator privileges, is it essential or critical to its functionality, or just an artefact of some operation(s) that it assumes upon start?

I am going to be debugging my own processes, not even that -- actually I just want to open a .DBG dump file.

I understand that it may be a Windows limitation that requires the program to run with Administrator privileges in order to do some/everything that it is doing, but is there any chance to compartmentalize functionality so it at least starts when run with user privileges?

Am I welcome to submit a patch? Thank you.

[ThunderCls]

I'm assuming you're executing the launcher, if so, it will just try to create a couple entries in the Windows registry for shortcuts and icons and that stuff, but it's not required for proper use of the debugger, just run x32dbg.exe or x64dbg.exe directly depending on the platform you want to debug and you're good to go

[mrexodia]

Yeah I have to fix the launcher to make it more clear how to start x64dbg
itself...
On Sat, 13 May 2017 at 13:22, ThunderCls [e-mail] wrote:

I'm assuming you're executing the launcher, if so, it will just try to
create a couple entries in the Windows registry for shortcuts and icons and
that stuff, but it's not required for proper use of the debugger, just run
x32dbg.exe or x64dbg.exe directly depending on the platform you want to
debug and you're good to go

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/x64dbg/x64dbg/issues/1591#issuecomment-301242094, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACWCmbztlZ7itRIv7V86DMRKfZqyZpV4ks5r5ZJ4gaJpZM4NaCS7
.

[amn]

Appreciate your swift and constructive response, guys. Thank you for the tool. For now, I figure I will be loading from the x64dbg.exe that is in the ./release/x64 folder, as opposed to the "launcher" that's ./release/x96dbg.exe (not sure why it has "96" in the name?)

[mrexodia]

32+64
On Sat, 13 May 2017 at 16:51, amn [e-mail] wrote:

Appreciate your swift and constructive response, guys. Thank you for the
tool. For now, I figure I will be loading from the x64dbg.exe that is in
the ./release/x64 folder, as opposed to the "launcher" that's
./release/x96dbg.exe (not sure why it has "96" in the name?)

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
https://github.com/x64dbg/x64dbg/issues/1591#issuecomment-301253019, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACWCmRrHnguA3b4GAh0oGzILppRjk6Wfks5r5cNggaJpZM4NaCS7
.

[mrexodia]

The launcher has now been improved: