OneDrive components are initialized and re‑registered at user logon, profile attach, reboot, and servicing events.

Question

Microsoft officially documents that OneDrive is a per‑user, self‑updating application and that in virtual and multi‑session environments (Citrix VDA with FSLogix), OneDrive components are initialized and re‑registered at user logon, profile attach, reboot, and servicing events. As a result, Windows may update the “Installed Date” metadata without any actual reinstallation, version change, or user activity. This behavior is expected and supported by Microsoft. (Cited from Microsoft Learn OneDrive VDI & FSLogix documentation)

Which document this?

Answer 1

Hi Rout, Subham,

In VDI/FSLogix environments, even when installed per-machine, OneDrive runs a lightweight setup routine (like OneDriveSetup.exe /thfirstsetup) every time a user logs in or attaches their profile.

This routine ensures the user's profile is configured correctly. In doing so, it touches and updates the uninstall registry keys for OneDrive under HKCU. Windows natively monitors these keys, and when they are modified, Windows automatically updates the "Installed Date" displayed in Apps & Features — even though no actual reinstallation or version upgrade occurred.

Stop looking for that exact quote. If you need to explain this to an audit or security team, explain the registry-touch behavior during the logon process. If this helps clarify the mystery, please click "Accept Answer".

Tracy Le.

Answer 2

Hi Rout, Subham,

I’m just following up to see if the explanation regarding the OneDrive registry-touch behavior helped clear things up for your team or auditors.

Were you able to use the "registry-touch" explanation to justify those "Installed Date" metadata changes in your VDI reports? If you've found the specific documentation you were looking for or if you need further help with FSLogix profile behavior, just let me know.

If the mystery is solved, please feel free to click "Accept Answer" so others in the community can find this information easily.

Tracy.

Answer 3

No document in the provided context contains that specific statement about OneDrive components being initialized and re‑registered at user logon, profile attach, reboot, and servicing events, or about this behavior explaining changes to the “Installed Date” metadata.

The available OneDrive- and FSLogix-related documents in the context cover:

• FSLogix/OneDrive compatibility and the FSLogix_unsupported_environment error, and its resolution by updating FSLogix.
• General OneDrive restrictions and limitations in VDI environments, including supported scenarios with FSLogix.
• FSLogix profile containers usage with Azure Virtual Desktop and the fact that OneDrive is not supported in non‑persistent VDI without FSLogix.

None of these explicitly document the Installed Date metadata behavior described in the question.

---

References:

• "FSLogix_unsupported_environment" and OneDrive sync error on virtual machines
• Restrictions and limitations in OneDrive and SharePoint
• User profile management for Azure Virtual Desktop with FSLogix profile containers