Keysight Handheld Meter Logger - Know bug list since 2015 up to 2026

[Kiriakos GR]

Keysight Handheld Meter Logger this is a piece of software which gained my positive vote as user interface since 2012.
Unfortunately for us the consumers, the switching of brand name (spin of) from Agilent to Keysight this had a cost.
The team of people them supporting software and marketing of orange series of DMM and tools, this were dismantled.

Handheld Meter Logger this is now a dead project in the eyes of Keysight.
Now at 2021 its a good time so the bug list to be summarized.

1) Most annoying issue this is scientific values in use at graphic users interface at vertical axis. 
There is no prediction from the end of software developers, the current scientific notation ( power of 10 exponent) to be able to change at regular numbers.

2)  When data-log session this is longer than 60 minutes, in most cases will appear within the logged values, one incident of zero value to be recorded too.
Lets assume that you are measuring voltage at battery discharge session, and a nice graph of discharge curve this starts to buildup overtime, due software glitch an voltage spike of zero volts this gets recorded too.
As soon this glitch appears, anything recorded as Min / Max statistics this getting destroyed.

3) At Windows operation systems Win 7 or higher ( if you own a wide screen) and if you do try to increase percentage of screen fonts from 100% to a higher value (110 or 115%) so the text on desktop to appear larger, the Handheld Meter Logger software does not go full screen any more.

4)  Handheld Meter Logger software this is in theory capable to export your work as documents by the help of Microsoft office.
Undocumented limitations
a) Compatibility of Agilent / Keysight software with Microsoft office, this starts from MS Office version of 2010 and or higher.
b) Printed report generation, this can not include more that 200 data-points,  for example if you logging mains voltage you need to limit your log length to 200 data-points if you expect to use printed report generation.

5)  Handheld Meter Logger unable to connect with  Keysight server ... Check for updates...
Indeed some one pulled away and this plug, from the end of Keysight, and the software has nothing to connect to.
I am offering this clarification and or confirmation, because many of us we though that the problem could be miss-configuration of operating system and or a Firewall issue.
 


Nothing of all these makes sense, but it does from the end of Keysight,  Handheld Meter Logger this is a free sample an appetizer, so the consumers to be aware of other software that Keysight has on sale.   
What Keysight it is in denial to grasp, this is Handheld Meter owners feeling of disappointment, and it negative impact at any of Keysight marketing plans.   


https://www.keysight.com/us/en/lib/software-detail/computer-software/keysight-handheld-meter-logger-software-for-pc-2470924.html

[Kiriakos GR]

I have fresh information's to share.

Keysight Support EU, at June 2025 opened for me, Support Case 01866762.
Entire feedback from this topic, this were transferred at THE Powers that be, software support division.

I do not feel optimistic, but from the other hand, for as long Keysight this has at their portfolio even a few Orange Series DMM.
They are obligated to provide BUG-FREE software for them.


About me, for any critical data logging application, I am using the combination TsDMMViewer Data Logger for FLUKE 8846A.

But I do wish to see Keysight Handheld Meter Logger getting a new facelift, because this is the only one able to support Many DMM simultaneously.   

[Kiriakos GR]

Interesting News...   at 25 June 2025,   Keysight added a driver file for W11 support,  that is a workaround.

In other words,  I count this as a silent software product support action, in favor of  Keysight Handheld Meter Logger.

First Blog post web link, this is upgraded to latest known at 2026.

As local copy I am attaching the relative PDF. 

[Kiriakos GR]

We are now one year later, after of me reporting entire summary of bugs to Keysight.
And its obvious, they did nothing.

For us insisting to use this software, the "Zero Spike" Long-Session Bug, this is top ranked BUG.
I did a simple thought, can we use third party editor, so us to delete the "Zero Spike", from an entire logged session?

And I got AI response, file format of the saved log, this is proprietary, compiled binary format designed specifically by Agilent/Keysight to prevent external tampering.

And I do wonder, of what the Fuck is all that?

to prevent external tampering ??
Since when us electricians we are considered as vicious hackers?
 
Well, there is only one logical explanation, Agilent/Keysight along FLUKE, they both thought measurement reports extracted as PDF, as a new form of merchandise.
The point is that printed measurement reports, this might have some value as inspection material and a proof.
But these things they might have some value as simple documentation for internal use = predictive maintenance log.

This reporting feature it is not evidence standing in a court of law. 

Indeed us involved at product reviews at 2012, we did not have enough training, at judging software related limitations and bugs.
Electrical logs reporting feature this came from FLUKE Corporation, and several years later, this is also when abandoned by FLUKE Corporation.
Agilent/Keysight they thought as well of this, as an item, a sales point.

Electrical logs reporting feature, this failed to become adopted, and this is of why this got abandoned.
Thermal imagers logs reporting, this is now also under evaluation, if this also fails be adopted?  This will have the same fate as it had the Electrical logs reporting feature.

In conclusion:
What regular humans should keep as an answer,  logs saved as a file due this software, they are not editable.
And due to proprietary software restrictions, no one will ever dare making an third-party editor.