A_Args can't handle windows file arguments with spaces (drag&drop, sendto, etc, 8.3 shortname disabled)

[neogna2]

[HKEY_CLASSES_ROOT\AutoHotkeyScript\ShellEx\DropHandler]
@="{86C86720-42A0-1069-A2E8-08002B30309D}"

That's the same drophandler that causes dropped files to become 8.3 short filepaths in A_Args on the PC I tested. I don't know why the same thing doesn't happen on your PC.

And yes I still have python installed, did it has something to do with this?

No, it doesn't look like you're using the python drophandler.

Switching to it might be a way to do what you want to do though. But as I wrote I don't know if there are any issues with using it that way so probably something to research more before using it permanently.

[lexikos]

AutoHotkey v2 does not even register a DropHandler, so drag-drop onto an .ahk file is not possible unless you have registered it yourself or installed v1.

{60254CA5-953B-11CF-8C96-00AA00B8708C} gives long paths including spaces, but does not support Unicode.

[byzod]

AutoHotkey v2 does not even register a DropHandler, so drag-drop onto an .ahk file is not possible unless you have registered it yourself or installed v1.

{60254CA5-953B-11CF-8C96-00AA00B8708C} gives long paths including spaces, but does not support Unicode.

That's really weird, I didn't remember doing anything related to mess with registry of ahk, I don't even know DropHandler is a thing until now
Since it's very unlikely some application doing this (like ahk install mess with VLC media player registry?), I suppose I did something then Windows automatically made it for me

[lexikos]

Like I said, it is registered by the v1 installer.

Windows does not automatically register a DropHandler.

[byzod]

Like I said, it is registered by the v1 installer.

Windows does not automatically register a DropHandler.

Ohh that's it, I installed v1 and upgrade to v2, that's why