mystery error accessing CD-ROM after FltStartFiltering() in minifilter, before attach.

Am getting

“The system cannot find message text for message number 0x13d in the
message file for System.”

in CMD.exe and,

“D:\ is not accessible.”
“The system cannot find message text for message number 0x in the
message file for D:.”

in Explorer.exe during attempted access to an empty CD-ROM drive.
This is occuring after my minifilter is attached to another Volume.
The minifilter appears to be working correctly, and is registered to
intercept all pre callbacks.

Have narrowed it down to the problem staring after the
FltStartFiltering() call in DriverEntry().
The installing INF has Default Instance Flag of “0x1”, so it should be
suppressing automatic attach on all volumes. We attach manually to a
Volume later by port callback, but the problem occurs immediately after
the call to FltStartFiltering, before any attach.

The message number appears to be of no help, and I am run out of things
to try, check, and understanding.

Why should even an incorrectly handled IRP by the minifilter on device
stack #1 have any effect whatsoever on a completely different device
stack #2 servicing a CD-ROM. (short of BSOD, of course)

Im pretty much out of ideas. I’ve got nothing.

The error you are getting *isn’t* about D:\ (except in passing). It is
saying that it cannot open the system message file.

The access to d:\ has provoked an errror and in an attenpt to provide an
error message, exploder has tripped over another error - it cannot find the
message file.

So your filter could be getting in the way of the message file lookup…

/rod

Steading System Software