This looks like a limitation of Hitachi NAS:
From Hitachi’s forums, assuming I have found the correct product, a Feb 2017 thread with a July 2017 response here: https://community.hds.com/thread/11465-filsystemwatcher-dont-work-on-hnas
FileSystemWatcher doesn’t work on HNAS
Hitachi NAS has only limited support for this feature of the SMB Protocol.
Our current implementation of change notification, does not inform clients what has changed, merely that a directory has changed. It is then up to the client to determine what has changed by enumerating the directory
Also a thread from 2013 saying it didn’t support change notification at all at the time. https://community.hds.com/thread/3591
Whatever it is doing, sending change event 153 is completely invalid, as the valid events are only 1-5 as follows:
It’s also generating events for the folder, not the file being modified, which ties in with the 2017 thread quoted above. The thing is, there is no documented way to even ask for the whole folder to be re-read like they are describing, at least that I know of and via the API in question.
It is possible that Explorer interprets an invalid event value as “I have no idea what this device is telling me, so I’ll re-read the entire folder”, but that is both undocumented and will have terrible performance, and is not needed for any other device we know of, so it’s not something we are going to do.
It’s interesting that there is a shell change event for the file in the second log. It’s possible that Explorer itself is generating that after re-reading the folder, but only if it happens to be looking at the folder, in an attempt to tell other programs about the change it noticed. (Explorer does this in a few other cases to help with badly written devices, e.g. optical drives which do not report eject/insert correctly.)
At the end of the day, this looks like Hitachi’s NAS solution is unfinished and doing something illegal according to the API docs. If so, you’ll see similar problems in other programs which monitor folders (e.g. FileSystemWatcher, as mentioned in the quoted thread). It does not look like something we can fix, at least in a reasonable way, and on the flipside it absolutely is something that a NAS should do properly in 2017, so in my opinion you should complain to Hitachi about this.