[Dx4win] Problem with 9.0.4.1176 LotW confirmations

[Bob Henderson]

I am having a problem with LotW confirmations.  I have noticed this twice
recently.  The first time a 6m Q with AP2AM was confirmed via LotW but when
the ADIF record was downloaded from LotW DX4WIN considered it a dupe and
did not update QSL status.

A similar incident has occurred today.

The following ADIF was dowloaded from LotW and imported using the Confirm
LotW option.  Only the record for G4XXI was recognised as new and its QSL
status updated.  The other 5 QSOs were reported as duplicates and their QSL
status was not updated.

Can someone help me understand whether I have a problem with the download
from LotW or a problem with DX4WIN handling the file?

I don't think it can be finger trouble as I have done this kind of update
hundreds of times.

Thanks.

Bob, 5B4AGN

ARRL Logbook of the World Status Report
Generated at 2018-07-01 03:27:15
for 5b4agn
Query:
    OWNCALL: 5B4AGN
   QSL ONLY: YES
  QSL SINCE: 2018-06-27 00:00:00

<PROGRAMID:4>LoTW
<APP_LoTW_LASTQSL:19>2018-06-30 22:18:10

<APP_LoTW_NUMREC:1>6

<eoh>

<APP_LoTW_OWNCALL:6>5B4AGN
<STATION_CALLSIGN:6>5B4AGN
<CALL:5>TZ4AM
<BAND:2>6M
<FREQ:8>50.10687
<MODE:2>CW
<APP_LoTW_MODEGROUP:2>CW
<QSO_DATE:8>20180617
<TIME_ON:6>132301
<QSL_RCVD:1>Y
<QSLRDATE:8>20180630
<eor>

<APP_LoTW_OWNCALL:6>5B4AGN
<STATION_CALLSIGN:6>5B4AGN
<CALL:4>W2FU
<BAND:3>40M
<FREQ:7>7.02464
<MODE:2>CW
<APP_LoTW_MODEGROUP:2>CW
<QSO_DATE:8>20160220
<TIME_ON:6>001430
<QSL_RCVD:1>Y
<QSLRDATE:8>20180628
<eor>

<APP_LoTW_OWNCALL:6>5B4AGN
<STATION_CALLSIGN:6>5B4AGN
<CALL:5>G4XXI
<BAND:3>40M
<MODE:4>RTTY
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20050122
<TIME_ON:6>190535
<QSL_RCVD:1>Y
<QSLRDATE:8>20180627
<eor>

<APP_LoTW_OWNCALL:6>5B4AGN
<STATION_CALLSIGN:6>5B4AGN
<CALL:5>OH5KW
<BAND:2>6M
<FREQ:8>50.31540
<MODE:3>FT8
<APP_LoTW_MODEGROUP:4>DATA
<QSO_DATE:8>20180624
<TIME_ON:6>094345
<QSL_RCVD:1>Y
<QSLRDATE:8>20180627
<eor>