I've run across a situation where a customer is reporting odd behavior from his system. The software running on his system uses the GetVolumeInformation in kernel32 to document the machine's current hard drive serial number. Sometimes it gets the serial number and other times it doesn't. The user can literally run the app and not get the number, exit, then run the app and get the number. Odd, just odd. I've run through the P/Invoke declaration and it seems right. I'm wondering if Trend Micro is interfering but am having a hard time understanding if it is, how. Can Trend Micro interfer with kernel32 API calls?

@wkempf: That is what my brain says too. I probably wouldn't even consider it if I didn't have so many years experience seeing how trend micro in particular, other anti-virus to a lesser extent, has caused ... well just wierdness.

We created a separate app that calls the same API using the same P/Invoke and logged the results and had the user randomly run it whenever they felt like it. It never failed.

It isn't good to throw changes out just to see what sticks but the Trend Micro theory doesn't sound provable in this situation. If you feel like something wouldn't be marshalled right with the first signature it won't hurt my circa 2005 feelings to tell me. Same for the second signature.

Thread Closed

This thread is kinda stale and has been closed but if you'd like to continue the conversation,
please create a new thread in our Forums, or
Contact Us and let us know.