why Hashcat v6.2.5 is slower than v5.1.0

[GWN]

*ttp://registrationcenter-download.intel.com/akdlm/irc_nas/vcp/13794/opencl_runtime_18.1_x64_setup.msi

this is the direct link for cpu opencl

install this and see the output for hashcat -I

your cpu should show up with opencl 2.1

Thank you Snoopy for your prompt response.  Sorry for my delay as I was distracted by other projects.

Thank you so much for your link to OpenCL, it was brilliant.  My initial attempts at finding this sent me to all sorts of weird Intel sites that wanted me to sign up to request authorization to download, so very strange.  Yours was a godsend, easiest install I have had in a long time.

After rebooting (yes I know that should be obvious) I now have my computer showing up with 2.1 as you said:
C:\Users\xyz\AppData\Local\Programs\hashcat-6.2.5>hashcat -I
hashcat (v6.2.5) starting in backend information mode

cuFuncSetAttribute is missing from CUDA shared library.
clCreateContext(): CL_DEVICE_NOT_AVAILABLE

OpenCL Info:
============
OpenCL Platform ID #1
  Vendor..: Intel(R) Corporation
  Name....: Intel(R) CPU Runtime for OpenCL(TM) Applications
  Version.: OpenCL 2.1 WINDOWS
  Backend Device ID #1
    Type...........: CPU
    Vendor.ID......: 8
  Vendor.........: Intel(R) Corporation
    Name...........: Intel(R) Xeon(R) CPU          E5410  @ 2.33GHz
    Version........: OpenCL 2.1 (Build 0)
    Processor(s)...: 4
    Clock..........: 2330
    Memory.Total...: 32767 MB (limited to 4095 MB allocatable in one block)
    Memory.Free....: 0 MB
    OpenCL.Version.: OpenCL C 2.0
    Driver.Version.: 18.1.0.0920

Then running:
C:\Users\xyz\AppData\Local\Programs\hashcat-6.2.5>hashcat -b -m 14600 -D 1
hashcat (v6.2.5) starting in benchmark mode

Benchmarking uses hand-optimized kernel code by default.
You can use it in your cracking session by setting the -O option.
Note: Using optimized kernel code limits the maximum supported password length.
To disable the optimized kernel code in benchmark mode, use the -w option.

cuFuncSetAttribute is missing from CUDA shared library.
clCreateContext(): CL_DEVICE_NOT_AVAILABLE

OpenCL API (OpenCL 2.1 WINDOWS) - Platform #1 [Intel(R) Corporation]
====================================================================
* Device #1: Intel(R) Xeon(R) CPU          E5410  @ 2.33GHz, skipped

Benchmark relevant options:
===========================
* --opencl-device-types=1
* --optimized-kernel-enable

---------------------------------------------
* Hash-Mode 14600 (LUKS) [Iterations: 163044]
---------------------------------------------

Then for reference my windows paths are:

• C:\Program Files (x86)\Common Files\Intel\OpenCL\windows\compiler\lib\intel64_win;
  
• C:\Program Files (x86)\Common Files\Intel\OpenCL\windows\compiler\lib\ia32_win;
  
• C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\bin;
  
• C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.6\libnvvp;
  
• C:\WINDOWS\system32;
  
• C:\WINDOWS;
  
• C:\WINDOWS\System32\Wbem;
  
• C:\WINDOWS\System32\WindowsPowerShell\v1.0\;
  
• C:\WINDOWS\System32\OpenSSH\;
  
• C:\Program Files\Microsoft SQL Server\130\Tools\Binn\;
  
• C:\Program Files\NVIDIA Corporation\Nsight Compute 2022.1.1\;
  
• C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;
  
• C:\Users\xyz\AppData\Local\Programs\Python\Python310\Scripts\;
  
• C:\Users\xyz\AppData\Local\Programs\Python\Python310\;
  
• C:\Users\xyz\AppData\Local\Microsoft\WindowsApps;
  

I searched for cuFuncSetAttribute on my C drive and windows found this:
Name                    Folder;                                                              Date modified; Type; Size
cuda.h                  include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1.6); 2021-12-17 8:06 PM; H File; 791 KB
cudaTypedefs.h          include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1.6); 2021-12-17 8:06 PM; H File 89 KB
cuda..occupancy.h       include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1.6); 2021-12-17 8:06 PM; H File 65KB
generated_cuda_meta.h   include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1 .6\compute-sanitizer); 2022-03-08 1OE22 PM; H File; 77 KB
sanitizer_driver_cbid.h include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vll.6\compute-sanitizer); 2022-03-08 1OE22 PM; H File; 84KB
cuptLdriver_cbid.h      include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1 .6\extras\CUP11); 2022-03-08 7:52 PM; H File; 64 KB
generated_cuda_meta.h   include (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1 .6\extras\CUP11); 2022-03-08 7:52 PM; H File; 77 KB

I also searched for clCreateContext on my C drive and windows found:

Name    Folder;                                                               Date modified; Type; Size
cl.h    CL (C\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vll.6\include); 2021-12-17 8:06 PM; H File; 78KB
cl.hpp  CL (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1 .6\include); 2021-12-17 8:06 PM; HPP File; 287 KB
cLext.h CL (C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\vl 1.6\include); 2021-12-17 8:06 PM; H File; 47KB

These results only add to my confusion...

My questions now are:

1. what do I do about the missing cuFuncSetAttribute complaint?  Do I just disregard this message and start using hashcat?
   
2. what does CL_DEVICE_NOT_AVAILABLE mean?
   
3. am I missing any "path" for these missing/unavailable items?
   
4. any other recommendations on being able to move forward and start using hashcat?
   

Thank you for your ongoing help.