Cleaning Up

[RossMMason]

How do you stop monitoring for changes? Could you please explicitly mention clean up steps even if non are required?

I am experiencing an error with regard to a removable USB drive which I think could be resolved if I could somehow clean-up and then restart the monitoring at key points such as when the machine goes to sleep. The error code I am receiving is 80080222. Could an explanation and mitigation steps for this error be included in the docs?

My problem is outlined in this SO post: https://stackoverflow.com/questions/57466690/0x80080222-error-when-monitoring-folder-with-storagelibrarychangetracker

---

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 81f99dd3-f720-8363-b812-1b25b771278d
• Version Independent ID: b662410d-8bf8-a99c-bad1-586de07751f1
• Content: Track file system changes in the background - Windows UWP applications
• Content Source: windows-apps-src/files/change-tracking-filesystem.md
• Product: uwp
• Technology: data-and-files
• GitHub Login: @knicholasa
• Microsoft Alias: nichola

[knicholasa]

Hi, thanks for the feedback and you've already done the right think in going to SO for assistance. Another resource to check out would be our support forums. If you get assistance through these other resources and believe that information would help improve the docs, please come back and update this thread. Otherwise I will follow up internally to see about adding that information to the docs.

[RossMMason]

Thanks Nick,

I haven't had much luck with the support forums in the past!

I’ll definitely feedback with any further information if I find out any more. If you have contact with the team could you try and track down the meaning of that error code and find a way to incorporate it in the docs. Understanding what it is trying to tell me would be a good first step and I can’t find any further information on it anywhere.

[RossMMason]

Some more info on my particular problem although it is probably not that important to the documentation request.

We originally wrapped some exception handling round the error to catch it and this was useful in diagnosing the error but once the error occurred we got no changes until the machine was rebooted.

We have since updated some drivers on the machine and we still intermittently catch and log the error but we then receive the changed files on our next polling attempt.

It would still be really nice to have info on the error message we are receiving added to the docs and also to have some information on housekeeping. I.E if clean-up is required and if not why not.

[knicholasa]

Hi @RossMMason, I reached out to the team and they are curious to learn more about your scenario. Adam left a comment on the stack overflow thread, please follow up with him there and he can help you out. I'll update the docs as necessary depending on what they learn from that thread.