ElvisBlue/x64dbgpython

Failed to load plugin, specific Python version?

Closed this issue · 5 comments

Bluefissure commented

I installed Python 3.10.11 (x64 and x32), and added the paths to PATH. But I still got the error just like #1 .

Is it restricting the specific python version?

Initializing wait objects...
Initializing debugger...
Initializing debugger functions...
Setting JSON memory management functions...
Initializing Zydis...
Getting directory information...
Start file read thread...
Retrieving syscall indices...
Symbol Path: D:\x64dbg\release\x64\symbols
Allocating message stack...
Initializing global script variables...
Registering debugger commands...
Registering GUI command handler...
Registering expression functions...
Registering format functions...
Registering Script DLL command handler...
Starting command loop...
Initialization successful!
Loading plugins...
[PLUGIN] Failed to load plugin: x64dbgpython.dp64
Handling command line...
  "D:\x64dbg\release\x64\x64dbg.exe" 
Syscall indices loaded!
Error codes database loaded!
Exception codes database loaded!
NTSTATUS codes database loaded!
Windows constant database loaded!
Reading notes file...
File read thread finished!
ElvisBlue commented

Weird. Maybe some dependencies is missing. Can you use sysmon and check that for me? Thank. Also Which OS are you running?

Bluefissure commented

I'm using Windows 11 Pro 10.0.22621 22621

and it looks sysmon only logs the process start event info, didn't find any error:

- System 

  - Provider 

   [ Name]  Microsoft-Windows-Sysmon 
   [ Guid]  {5770385f-c22a-43e0-bf4c-06f5698ffbd9} 
 
   EventID 1 
 
   Version 5 
 
   Level 4 
 
   Task 1 
 
   Opcode 0 
 
   Keywords 0x8000000000000000 
 
  - TimeCreated 

   [ SystemTime]  2023-07-13T23:58:25.0462876Z 
 
   EventRecordID 241 
 
   Correlation 
 
  - Execution 

   [ ProcessID]  31592 
   [ ThreadID]  4036 
 
   Channel Microsoft-Windows-Sysmon/Operational 
 
   Computer DESKTOP-ME728U9 
 
  - Security 

   [ UserID]  S-1-5-18 
 

- EventData 

  RuleName - 
  UtcTime 2023-07-13 23:58:25.031 
  ProcessGuid {53143936-8fa1-64b0-d6c6-000000001700} 
  ProcessId 22356 
  Image D:\x64dbg\release\x64\x64dbg.exe 
  FileVersion 0.0.2.5 
  Description x64dbg 
  Product x64dbg 
  Company - 
  OriginalFileName - 
  CommandLine "D:\x64dbg\release\x64\x64dbg.exe"  
  CurrentDirectory D:\x64dbg\release\x64\ 
  User <UserInfoHidden> 
  LogonGuid {53143936-8b47-64b0-b248-554300000000} 
  LogonId 0x435548b2 
  TerminalSessionId 22 
  IntegrityLevel High 
  Hashes SHA256=34DD2EDA0220D64DF84D14D75648129887066785653024BD01F9DBF5873DC4B8 
  ParentProcessGuid {53143936-8b48-64b0-eac3-000000001700} 
  ParentProcessId 16344 
  ParentImage C:\Windows\explorer.exe 
  ParentCommandLine C:\WINDOWS\Explorer.EXE 
  ParentUser <UserInfoHidden>

I'm not that familiar with sysmon, do I need to config it first?

ElvisBlue commented

Hi. Sorry for low response. Can you follow this tut and give me the result?
https://pentestlab.blog/2017/03/27/dll-hijacking/
Thank anyway. I want to see which dll is missing or failed to load

ElvisBlue commented

Hello
After some investigating I find out that new x64dbg version breaks almost plugin that has dependencies in "PATH". Issue here
The only recommend here is using snapshot_2023-03-03_01-29 which not break any plugin that has dependencies in "PATH".

Bluefissure commented

Hello After some investigating I find out that new x64dbg version breaks almost plugin that has dependencies in "PATH". Issue here The only recommend here is using snapshot_2023-03-03_01-29 which not break any plugin that has dependencies in "PATH".

Thank you for pointing out! I'll try that one.