Poking around in OneDrive on my production PC, I noticed an oddly-named file in its holdings. That name takes the form of a Windows GUID, like this:
In poking around with the object, I learned that it is a hidden file, and cannot be deleted (it is “in use” by OneDrive itself). Much to my surprise, I found this precise name occurs in many OneDrive folder structures at the root, particularly on PCs that have been upgraded to Windows 10 (as the host machine from which the intro screencap comes indeed was). In fact, I found a Microsoft Community post that included this very name in its title. In turn, it references my personal favorite source for Windows 10 enlightenment and information, TenForums.com.
More About the “.849” OneDrive item
In another, relatively recent Microsoft Community post (1/1/2019 and thereabouts), Microsoft Agent/Moderator Tina Zhou offer some additional and illuminating info:
First of all, I would like to explain that this is a system file, primarily so the OneDrive can sync itself to every file you want to back up, which means it updates without saving every single file again just the new ones added. It is encrypted to protect data privacy and security.
Interestingly, Ms. Zhou explains that this item does not appear in Explorer in every installation, but only on some installations. She confesses that she is unable to view or reproduce the symptoms or the object handle itself in her test installations. I’ve looked at the OneDrive folders on all 10 of my Windows 10 PCs, and this item occurs on 4 of them. Two are brand-new machines from Lenovo that shipped with Windows 10 installed (which I think puts paid to the notion that it presents only when a PC has been upgraded from an earlier Windows version, such as 7, 8, or 8.1).
Who knows why it appears in some OneDrive root folders, and not in others? I have no idea — and apparently, neither does Microsoft. These little quirks help explain why I like working with Windows so much. Once a systems gains a certain degree of complexity and a sufficient number of millions of lines of code, such oddities simply appear. This is one you can check for on your systems. Be grateful if it’s absent, and learn to tolerate it if it’s present. There’s not much else anyone can do. I love it!
Author: Ed Tittel
Ed Tittel is a 30-plus-year computer industry veteran. He’s a Princeton and multiple University of Texas graduate who’s worked in IT since 1981 when he started his first programming job. Over the past three decades he’s also worked as a manager, technical evangelist, consultant, trainer, and an expert witness. See his professional bio for all the details.