none
FindFirstFile fails with files in file virtualization solution RRS feed

  • Question

  • We are using Molebox Virtualization Solution to pack and protect our files. It's a full file system, registry virtualization solution which worked fine until we upgraded to Windows 10 Insider Build 17035. Since then when we try to enumerate files, packed into the virtual file system, with FindFirstFile, the function returns INVALID_HANDLE_VALUE and GetLastError returns code 6 (which is Invalid handle value). We are curious what was the change that caused this error in our app. Is it intentional or there are some known bug, that could cause this problem? Should we wait for the stable update or take measures right now? We can't really get rid of the virtualization, because it would affect a lot of data and our customers.

    Our application is built with Visual Studio 2013.

    • Moved by Hart Wang Friday, November 24, 2017 6:44 AM
    Wednesday, November 22, 2017 9:17 AM

All replies

  • To answer this, more information would be useful. Does this "molebox" thing include a filesystem driver, minifilter and so on? Does it rely on "undocumented" techniques that are sensitive to changes in internal Windows structures? 

    -- pa



    • Edited by Pavel A Wednesday, November 22, 2017 11:43 PM
    Wednesday, November 22, 2017 11:41 PM
  • My best advice is to take up the issue with the author of the MoleBox software at https://github.com/sudachen/Molebox
    Thursday, November 23, 2017 12:28 AM
  • Hi dam4rus,

    Thank you for posting here.

    According to your description, it seems to be bug on windows 10.

    I suggest that you can provide your issue on here. you can try to use the tool to write your feedback.

    Since your issue is not about developing software issue, I will move the case to off-topic.

    Best Regards,

    Hart


    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, November 23, 2017 1:48 AM