No problem I understand ;) so I'll use DGDecIM only on my PC. It's only an (perhaps bad) idea : you could test if your WMI request works and if not, get WMI BIOS serial number instead of baseboard ? And if it doesn't work show a warning "Your hardware is not supported" WMI request on my PC : wmic bi...

So I've tried the new nico.exe and here is the result :
Connected to ROOT\CIMV2 WMI namespace
returned 1, count 0
No objects found
Cleaning up...
Cleanup successfull

You're welcome, it's a pleasure, thank you to spend your time to help me

Thank you but I could try Monday only... I'll tell you

No problem Donald, good luck ! I hope you'll win against the coffee

No problem
"wmic baseboard get serialnumber" command doesn't give result, perhaps because it's a HP ProLiant server and not a PC ?! It works on my PC HP, I get a result.

Same result with the latest exe : [22488] DGIndexIM: ref 11a [22488] DGIndexIM: ref 11b [22488] DGIndexIM: ref 11c [22488] DGIndexIM: ref 11d [22488] DGIndexIM: ref 11e [22488] DGIndexIM: ref 11f [22488] DGIndexIM: ref 11h [22488] DGIndexIM: ref 12a [22488] DGIndexIM: pEnumerator->Next returned 1, c...

Good thing, now app doesn't crash and I have this message : Machine ID 000000000: Incorrect options to DGIndex. Please refer to the manual. Here is the log : 00000001 0.00000000 [14052] DGIndexIM: ref 11a 00000002 0.00175039 [14052] DGIndexIM: ref 11b 00000003 0.00380422 [14052] DGIndexIM: ref 11c 0...

If you want to do some tests tell me. Thank you for your time

Count 0 should be Count 1 or an other value ?
Thank you for your search, but if there is no answer I don't want to take all your time

Here is the new log : 00000001 0.00000000 [22348] DGIndexIM: ref 1 00000002 0.00019167 [22348] DGIndexIM: ref 2 00000003 0.00028616 [22348] DGIndexIM: ref 3 00000004 0.00032572 [22348] DGIndexIM: ref 4 00000005 0.00036990 [22348] DGIndexIM: ref 5 00000006 0.00040178 [22348] DGIndexIM: ref 6 00000007...

Thank you :) I've downloaded the new EXE, created a new folder and put in it, alone. Here is the result : 00000001 0.00000000 [11744] DGIndexIM: ref 1 00000002 0.00015364 [11744] DGIndexIM: ref 2 00000003 0.00021702 [11744] DGIndexIM: ref 3 00000004 0.00024621 [11744] DGIndexIM: ref 4 00000005 0.000...

PM sent

I've ran that from your previous post : http://rationalqm.us/misc/DGIndexIM.exe
And I've tried both, 32 and 64 bits but same issue.

Here is the debug log : First attempt : 00000001 0.00000000 [17532] DGIndexIM: ref 1 00000002 0.00029308 [17532] DGIndexIM: ref 2 00000003 0.00040139 [17532] DGIndexIM: ref 3 00000004 0.00046785 [17532] DGIndexIM: ref 4 00000005 0.00050741 [17532] DGIndexIM: ref 5 00000006 0.00054313 [17532] DGIndex...

Sorry I would like to say no more
Thank you, I'm going to test and I tell you.

First attempt : MSVCP120.dll is missing. I'm going to install Visual C++ 2013
Second attempt (after Visual C++2013 install) :
Connected to ROOT\CIMV2 WMI namespace
Get succeeded
Cleaning up...
Cleanup successfull
But DGIndexIM.exe doesn't work anymore
Thank you for your help

Yes I'm interested by your small program to test, thank you. Do you think appcrash is really related to WMI ?

You could find report and appcrash screenshot (sorry it's in French) in attachments but problems found for WMI are HP WBEM product related.

I'm going to do a WMIDiag 2.2, it supports Windows 2012 R2 without mod.

The OS is 64 bits, is there several versions ?

Yes I prefer to use SW mode and I can't use HW because I don't have an Intel iGPU compatible.
I don't launch any command line, simple double click on DGIndexIM.exe and it crashes. I can't see any crash dump details, only APPCRASH. I can make a screenshot if you want.

Excuse me, it's not DGDecIM but DGIndexIM.exe. I'm sorry for this mistake

So CPU are 2 x Intel Xeon X5650
Is it necessary to use Intel iGPU ? I can use DGDecIM on my AMD platform without problem.
Thank you Donald

It is a 2 x Xeon, I could tell exact reference later.