Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging

The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.

Check out The OSR Learning Library at:

Windows Internal File Id and Named Streams

rstruempfrstruempf Member Posts: 103

Does the file id (FileInternalInformation) identify a file, including named streams, or a stream?

If it identifies a file, then does createfile when using FILE_OPEN_BY_FILE_ID always open the default stream, or is there a means to open a stream using the file id?


  • rod_widdowsonrod_widdowson Member - All Emails Posts: 1,172

    Last time I looked at NTFS (during XP-SP3) the ID was per File and it opened ::$data. I see no reason why NTFS would change but I don't see any reason that the other filesystems would follow suit.

    If I had that problem I'd open by FileID for no-access and then do a related open to that handle for the stream. You used to be able to open a stream realtive to another stream, but these days (IIRC) you can only open a stream, relative to ::$data.

  • rstruempfrstruempf Member Posts: 103

    That's the info I needed. Thanks!

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Writing WDF Drivers 7 Dec 2020 LIVE ONLINE
Internals & Software Drivers 25 Jan 2021 LIVE ONLINE
Developing Minifilters 8 March 2021 LIVE ONLINE