ArgyllCMS issues with Windows 11 24H2 26100

[vval]

Hello forum,

I’d spent few hours trying to find out why I get new_disprd failed with ‘Instrument Access Faile’ and ArgyllCMS  is not working at all on a fresh install of Windows 11, while the very same device (i1Display3) works fine on the similar Windows 11 and the very same ArgyllCMS and DisplayCAL versions.

So I’d like to share my findings. It looks like the recent Windows 11 update (24H2 build 26100), updated HID drivers as well and this is the reason.

New device driver version: 10.0.26100.1882 (not working)
Previous device driver version: 10.0.22621.4111 (working fine)

Both Argyll_V2.3.1 and Argyll_V3.3.0 are affected. Both x86 and x64 versions.
I think we need a fix from ArgyllCMS, because it’s obviously its code that couldn’t connect open correct HID device path anymore.

Alternatively, you may want not to upgrade to Windows 11 24H2 and stick to Windows 11 22H2 for a while, where it seems to works well.

Also, all of this is actual to i1Display3 devices with 0765/5020 IDs (USB\VID_0765&PID_5020).
If you have another device you may be lucky and your device is not affected.

(screenshot of working driver version attached)

Attachments:

You must be logged in to view attached files.

[Vincent]

Test i1d3 commandline, for example reading whitepoint on MS notepad with “spotread” or “spotread -X path_to_colorimetercorrection.ccss. ArgyllCMS executables should be on path.
If this works, it seems a DisplayCAL issue with newer windows or some issue on your computer (check that logitech app or something like taht is not using that USB address)
If this fails, report this on ArgyllCMS mailist with spotread output so ArgyllCMS developer or other people can guide you to find the issue.

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

[vval]

Vincent, thanks for your reply! Of course I’ve tested ArgyllCMS’s CLI, specifically spotread.exe, I thought it was obvious since I mentioned that “ArgyllCMS  is not working at all”.

I’m fairly certain this it’s not a DisplayCAL issue; I’m just posting here for reference, because someone might encounter the same problem with unclear messaging from DisplayCAL like “new_disprd failed with ‘Instrument Access Failed’”.

Thank you for mentioning ArgyllCMS mailist, I’ll consider it.

Here’s my ‘spotread.exe -D5’ output just for future reference or if someone is interested.
I’m using -D5 argument as it provides more informative output, which is important in this case.

#######################################################################                                                                                  Argyll 'V2.3.1c' Build 'MSWin 32 bit' System 'Windows V10.0 SP 0'
new_icompath: called with mask 0x1ffff
found HID device '\\?\hid#vid_0765&pid_5020#6&24bc8288&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', inst 15 that we're looking for
found HID device '\\?\hid#hid_device_system_vhf#8&21184364&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', inst 16 but unable get PID and VID
serial_get_paths: There don't appear to be any serial ports
new_inst: called with path 'hid:/15 (X-Rite i1 DisplayPro, ColorMunki Display)' type 'i1D3'
new_icoms 'hid:/15 (X-Rite i1 DisplayPro, ColorMunki Display)' itype 'i1D3' dctype 0x10004
i1d3_init_coms: called
i1d3_init_coms: About to init HID
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&24bc8288&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&24bc8288&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
i1d3_init_coms: set_hid_port failed ICOM err 0x20000
Failed to initialise communications with instrument
or wrong instrument or bad configuration!
('Communications failure' + 'Communications failure')

#######################################################################
Argyll 'V3.3.0' Build 'MSWin 32 bit' System 'Windows V10.0 SP 0'
new_icompath: called with mask 0x1ffff
found HID device '\\?\hid#vid_0765&pid_5020#6&24bc8288&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', inst 15 that we're looking for
found HID device '\\?\hid#hid_device_system_vhf#8&21184364&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}', inst 16 but unable get PID and VID
serial_get_paths: There don't appear to be any serial ports
new_inst: called with path 'hid:/15 (X-Rite i1 DisplayPro, ColorMunki Display)' type 'i1D3'
new_icoms 'hid:/15 (X-Rite i1 DisplayPro, ColorMunki Display)' itype 'i1D3' dctype 0x10004
i1d3_init_coms: called
i1d3_init_coms: About to init HID
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&24bc8288&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
hid_open_port: Failed to open path '\\?\hid#vid_0765&pid_5020#6&24bc8288&2&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}' with err 32
i1d3_init_coms: set_hid_port failed ICOM err 0x20000
Failed to initialise communications with instrument
or wrong instrument or bad configuration!
('Communications failure' + 'Communications failure')

I’m not really asking for help here, I’d like just to warn others and provide information for those who encounter the same of who will find this thread by googling.

• This reply was modified 1 year, 4 months ago by vval.

[Vincent]

Look in Windows services if any other app is using that USB device. There is known incompatibility with some Logitech or Asus laptop windows services.
THere is a thread here about that but I not remember the title.

[Ben]

Something is opening all devices on hid and should not.  It is a driver or a app.   Msconfig should help to disable startups and drivers.

It is something with a bug in it in the new update.   Might need newer drivers and the latest drivers are not from Microsoft.   Fan light controllers was one device that messed up the HID devices.   They scan all the devices and find the one they need.   They do not close there open file on the device.

[vval]

Vincent, Ben, thank you so much!
I was wrong.

Indeed, it was Logitech LampArray Service that caused the issue.

If someone encounter similar issue: you need to run services.msc, find “Logitech LampArray Service” and stop it (to check) and disable it (for more-or-less permanent fix).

The Internet says that it could automatically be re-enabled by the next Windows update and in such a case you may need to repeat disabling process. In my case, this service was most likely installed automatically, because I’m using a Logitech mouse with RGB lights. It also looks like not an Logitech fault, but linked to Microsoft’s new Windows 11 feature called Dynamic Lightning, which attempts to control RGB devices.

[daviangel]

Thanks so much for this answer been driving me nuts ever since it upgraded my Windows 11 install to 24H2 version my colormunki display stopped working with DisplayCAL and tried everything I could think but could never get it to work other than using old Windows 10 install!

This was absolutely the culprit as soon as I stopped Logitech LampArray Service  service stopped getting the instrument access failure error!

[jorel]

Just after a fresh Windows 11 Enterprise (24H2 – build 26100.3915) i had same problem described above.

tested lot of ArgyllCMS versions 2.1.2 , 2.3.0, 2.3.1 and 3.3.0… none worked.

Also tried to run spotread.exe from a command line at the path : C:\Users\<youruser>\AppData\Roaming\DisplayCAL\dl\<Argyll folder> but the output was even shorter than the one above.

Stopping and disabling Logitech LampArray service made DisplayCal 3.8.9.3 able to communicate with the device again as used to.

Thx

[Author]

Posts