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

Sept/Oct 2019 Issue of The NT Insider available

Download PDF here:

It’s a particularly BIG issue, too: 40 pages of technical goodness, ranging from WDF to Minifilters. Check it out.
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

What is Microsoft Office Isolated Conversion Environment?

MIGMIG Member Posts: 2


My filter driver gets it's reparse requests ignored when it is reparsing files in paths like this one

Searching around, I find references to some tech called 'Microsoft Office Isolated Conversion Environment' which appears to be some kind of sandboxing mechanism (although details are hard to find). My guess is that Win10 might be refusing to reparse access to here for security reasons.

Does anyone know if I am on the right lines here? If so is there any way I can escalate privilege or something to allow a reparse to happen?


  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,159

    I have never heard of that. This doesn't make it sound like anything that special though:

    What do you mean that your reparse requests are ignored?


  • MIGMIG Member Posts: 2

    Thanks Scott,
    Yes I saw this link, that and a couple of others are the basis for my assumptions (and my catchy thread title).
    Not sure what is described here is quite the same as what I see in Office 2016 though. I figured they might have kept the tech but somehow built it directly into office.
    If I procmon an excel file open from a network share, I see a copy of the excel file created in this location (possibly for the file preview before enabling edit).
    If I ask my filter driver to encrypt all excel files, the excel thread creating this file will successfully trigger a reparse in my driver and create this file encrypted.
    A second excel thread tries to open this file milliseconds later, this again triggers a reparse in my driver but the new CreateFile never appears (or perhaps gets consumed higher in the stack, but bizarrely it doesn't appear in procmon either).

    I only see this issue with win10 (win7 is fine with same Office version) and only when accessing network files.

  • Scott_Noone_(OSR)Scott_Noone_(OSR) Administrator Posts: 3,159

    Do you reparse to another location on the local drive or on the network share? When you reparse an open to an alternate path it should be the I/O Manager that retries the create with the new path, so it's odd that you're not seeing another open.

    I'd put a breakpoint on the second reparse and then trace the response to the application. If you do a .reload when you hit the breakpoint you should see the call stack go back to user mode, at which point you can put a breakpoint after the Office call to CreateFile. It would be interesting to know what the application is getting back in this case.


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
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE