Hello everyone.

We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.

The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.

The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.

On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.

So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality. If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers. And always feel free to hit us up on Twitter @MxdRealityDev.

Uploading 20 GB to app LocalState in device portal fills 40GB


I have built a script that uses the device portal API to copy files to LocalState folder of our app.

This is the code to upload:

            await _dp.UploadFileAsync("LocalAppData", fileName, Path.Combine("LocalState", folderPath), Config.PackageName);

The problem is that the files are taking twice as much space as they should, so even with a completely empty Hololens, we're coming up very short -- but this should not be the case.

Is this a bug with the Device Portal? Is there another way to load ~40GB of data onto the device without doubling it? Is there a way to clear the cache or write space? Thanks.


  • Update--

    Files copy to a temp folder and then are copied to the correct folder.
    If not enough space for the second copy is available, the copy from temp fails and the temp file is left with no recourse to remove it, so the space is still taken up.
    Similarly, if a file is copied to a non-existent directory, it only fails after the temp attempts to copy it to that directory.
    The bug here seems to be that we don't have any ability to clean up or clear the temp files, so that disk space is never recoverable (without a factory reset, at least).

Sign In or Register to comment.