New_disprd “Instrument Access Failed”

[Adam1171]

Hello!

I am a new (attempted) user of DisplayCAL with the goal of calibrating a display I use on my Windows 11 system (24H2 26100.4946).

I have purchased the Calibrite Display Pro HL for this purpose. However, since my first attempted calibration and every attempt since then, I have received the “New_disprd Instrument Access Failed” error. I’ve found and read through many, many posts covering this issue but none of the included solutions seemed to have had any effect.

I have made sure to kill the ‘logitech lamp array’ service and double-check to ensure it’s not running before every attempted calibration. I have installed the calibrate profiler software and performed one calibration run beforehand to ‘unlock’ its use. I have removed & reinstalled both DisplayCal and ArgyIICMS (both 2.3.1 and 3.4.0) multiple times, both with and without installing argyII instrument drivers (Though I believe they are not needed for the display pro HL?). I have additionally made sure to kill any unnecessary services running in the background after every PC reboot. I have also attempted calibrate with the device plugged into just about every USB port on my PC.

Forgive me, as I am not very knowledgeable when it comes to any of this stuff, but I am slowly losing my mind!

Does anyone know where I can even begin to troubleshoot this issue? Thanks

Calibrite Display Pro HL on Amazon   Calibrite Display SL on Amazon  
Disclosure: As an Amazon Associate I earn from qualifying purchases.

[Vincent]

If you can measure with calibrite profiler, device is OK. There must be something in PC using the i1d3.

Just to discard some “new unlock code” issue for brand new Calibrite Pro HL, which is very very very unlikely, can you try it on another machine? Or run ArgyllCMS command line with verbose option. Use argyll’s “spotread -v” on some white patch (maybe adding colorimeter correction, but since it’s just a test it is ot needed).

[Adam1171]

Thanks for your reply

I ran spotread -v  and was met with:

“hid_open_port: Failed to open path ‘\\?\hid#vid_0765&pid_5020#7&8670591&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}’ with err 32
Failed to initialise communications with instrument
or wrong instrument or bad configuration!
(‘Communications failure’ + ‘Communications failure’)”

I also reinstalled Calibrite profiler and went through a calibration again just to ensure I didn’t do anything wrong the first time.

(Also, unfortunately I don’t currently have access to any other machines to test this)

[Author]

Posts