LabVIEW
Reading CPU Usage in 64 BIT labview using pdh.dll dosent work.
@AtulS wrote:
if i manually specify path for 32 bit version of pdh.dll (Sustem32WOW) VI gets broken arrow ..
As mentioned, don't do that. Let Windows resolve that path...
Search LabVIEW like a graph! 
Without seeing what Windows API functions you call it is difficult to say what could be the problem. You added a snippet but that is in LabVIEW 2018 format and I only have LabVIEW 2016 installed on my machine (I'm working on a long term project in that version with RT and FPGA and various industrial protocol libraries installed, which is pretty critical and can't risk to mess up the LabVIEW installation for that).
So can you append a downsaved version of your VI to a post? The one where you claim to have changed all handles correctly!
From a somewhat educated guess I would think that your first function is PdhOpenQueryA() whose three parameters are all pointer sized variables! Then you use PdhAddCounterA() with the first being a handle, so pointer sized, and the 3rd being a DWORD_PTR, again pointer sized, and last but not least another handle, hence pointer sized and of course passed as reference, hence passed as Pointer to Value.
I think you should get the idea from here on!
And PdhGetFormatterCounterValue() might be also tricky. Its third paramater is an unsigned 32 bit integer but passed by reference! And the last is a pointer to a struct whose second element is a uniion of various dataypes, some of them being 8 byte long. So unless you pass in an array of two 64 bit integers you are bound to receive bad data. Personally I would make it a cluster with an unsigned 32 bit for the status, another 32 bit integer as filler and last but not least a 64 bit integer for the union element. Then Unflatten that value into a double, or an int32, or int64 depending on the value returned in the lpdwType variable.
