Hi Matt

Good Point, just interesting is, that the Driver is still able to read i.E. the DF_FILE_PHYSICAL_NAME Attribute without Problems. And the Circumstance that the physical Name points to the .INT on the Network Share leads me to the Assumption that there is maybe a Problem reading the INT. But as i already mentioned, without the deep Knowledge of how the Driver is reading the Values this is only guessing.

I already had the suggested Kind of caching the needed Attributes, which leads in a few other Problems, this is why i removed this Caching again.

Anyway i assume that one could trust that the Driver Calls work like expected. Additionally i'm afraid that similar Problems could appear on other Places. This is why i would prefer to Solve the Issue but to build any Workarounds.