Synchronization issue with unknown files
Hello. I have synchronization issue with 2 uknown files since 2 years or so. During that period I've restarted synchronization once. It didn't help. The weight of files sometimes changes what suggests that those files are in constant use. I would have excluded them from synchronization, but I can't identify them. There is no place where I could have found the name and location of those files. Does anyone know, by any chance, where are any logs or how to enable them, if they are not enabled by default, to troubleshoot that? Thanks in advance for any help in that matter... and Happy New Year!!How does local OneDrive determine if a local file needs to be updated?
When using multiple computers to edit a OneDrive file, a computer often fails to recognize its local copy needs to be updated, even though the file on all computers is set to "Always keep on this device." This means changes are lost with no conflict error generated. Is the OneDrive algorithm for deciding when to update a local version of a file documented anywhere? Usually when a change is made to a file, it starts uploading to the cloud within seconds. Within several seconds after the changed file is uploaded, other computers will recognize their local copy is outdated and will begin downloading the changed version. That is the expected behavior. But often, that doesn't happen. The outdated version is used to make new changes. Those new changes are uploaded successfully. No conflict warning is generated. The earlier changes are lost forever. I have not found any documentation on how local Windows OneDrive decides if its local version of a file needs to be updated. Is it looking at file size? Timestamps? If timestamps, is there a margin of time sync differences? Does the OneDrive metadata include the source device of the last upload? Not knowing any of this I cannot troubleshoot the problem much beyond establishing that the problem is not with uploading changes. OneDrive local is reliably uploading changes. MD5 hash codes in the cloud match the hash of the changed file on the source computer. I don't have time to jump through hoops with someone at frontline Microsoft support who doesn't know any more about the algorithm than I know in order to get the issue escalated to someone with the information needed to pinpoint the issuse.
Face scan recognition limits?
I was a big fan of adding name tags in photos before, and was eager to have it back. Problem is, I have quite a large number of photos, and onedrive just stopped scanning, being very far from finishing the job. I mean, considering for example the pictures my spouse appears in, one drive started recognizing her in the most ancient photos quite nicely, but stopped somewhere in 2006, and than added just a dozen from the most recent pictures. Yes, I keep taking photos of her meanwhile. Unfortunately it didn't accept help from me, like hey look here, this is a face, and is the face of this person. Any idea if this is just temporary?Move files from Account A to Account B 165 GB data
I’ve been using Microsoft Office 365 Family for several years, sharing it with my family members. We have 6 accounts, each with 1 TB of storage. One of my accounts has now reached 985 GB, so I need to transfer files from Account A (my account) to Account B (my wife’s account). These files mainly consist of photos and videos — over 200,000 files in total. I tried transferring a 6 GB wedding shoot (.ISO format), but it took more than an hour. Re-downloading and uploading all the data isn’t feasible as my internet connectivity is limited to 100 mbps only. I’m looking for the best and most efficient way to move these files directly between OneDrive accounts.
Some Fabric Lakehouse tables not appearing in Microsoft Purview after scan
Hi everyone, I’m running into an issue where several tables from a Fabric Lakehouse aren’t appearing in Microsoft Purview after a workspace scan. Here’s the situation: I scanned a Fabric workspace that contains multiple Lakehouses. For most Lakehouses, the tables appear correctly in Purview after the scan. However, for one specific Lakehouse, several tables that I know exist aren’t showing up in the scanned assets — even after adding the Lakehouse as an asset to a data product in the Unified Catalog. What I’ve tried: I rescanned the workspace and the specific Lakehouses. I verified that the tables are persistent (not temporary) and appear under the Tables section in Fabric, not only as files. I confirmed permissions for the Purview connection account. Scan results and errors: After the rescan, the tables still didn’t appear. The scan logs show several ingestion errors with messages like: Failed to ingest asset with type fabric_lakehouse and qualified name [qualified name] due to invalid data payload to data map I checked the error entries to see which assets they point to, and none of them are related to the tables in the Lakehouse in question. There were four of these errors in the last run. Additional context: Some older Lakehouses that had been archived months ago in Fabric still appeared as active in Purview before the rescan, so there may be stale metadata being retained. Notes: I’m aware Fabric scanning in Purview currently has sub-item scanning limitations where item-level metadata is prioritised, and individual tables aren’t always picked up. But given that tables from other Lakehouses appear as expected, and given the ingestion errors (even though the errors do not point to the missing tables), it feels like there may be a metadata sync or processing issue rather than a simple coverage limitation. Question: Has anyone encountered this behaviour or the “invalid data payload to data map” error before? Any guidance on further troubleshooting steps would be appreciated. Thanks in advance!
Ghost Profiles Persist in Edge Profile Switcher Despite Cleanup
I've submitted a detailed Feedback Hub report documenting persistent ghost profiles in Edge’s profile switcher. These profiles remain visible despite full local and registry cleanup, and there’s no user-facing way to remove them. The issue affects profile integrity, sync behaviour, and UI clarity. It’s reproducible and has no current resolution. Here’s the link to my Feedback Hub submission: https://aka.ms/AAykvpv If you’ve experienced this issue, please upvote or share your observations. Let’s help Microsoft prioritise this fix.Ghost Profiles Persist in Edge Profile Switcher Despite Cleanup
I've submitted a detailed Feedback Hub report documenting persistent ghost profiles in Edge’s profile switcher. These profiles remain visible despite full local and registry cleanup, and there’s no user-facing way to remove them. The issue affects profile integrity, sync behaviour, and UI clarity. It’s reproducible and has no current resolution. Here’s the link to my Feedback Hub submission:https://aka.ms/AAykvpv If you’ve experienced this issue, please upvote or share your observations. Let’s help Microsoft prioritise this fix.
OneDrive changes metadata on files
I'll try to make this brief. OneDrive is not accepting/changing the metadata on my images after edit. What happens is this: 1) I create an image file with keywords in DAM 2) OD uploads correctly. 3) I make a change to the file, e.g. keywords 4) OD uploads OK. Then 5) a minute or two later OD redownloads the file without the keyword edit, reverting to previous version. 6) DAM sees the change, and reverts the keywords. And then I'm in a perpetual loop. I have had 2 MS support cases on this, supplied videos, had screen share sessions and on all occasions, the support agents stop responding either by email or by phone. This is a very worrying issue and I see that others have experienced this over the last few years. I have had to remove my Photo library from OD, work on a local drive and rely on backups. Does anyone have any idea how to resolve this?
How can I force OneDrive to accept metadata for images and photos 1:1?
Is there any way to force OneDrive to save images as an exact copy of the original local files, including all changes to metadata? In detail: I have massive problems with using OneDrive as a data storage for photos, as OneDrive is often unwilling to accept changes to metadata (especially tags or geo-coordinates). The problem seems to have existed for years, as you can read in various places: https://www.dpreview.com/forums/thread/4527626 - OneDrive reverts changes to IPTC (!) https://answers.microsoft.com/en-us/msoffice/forum/all/onedrive-randomly-re-creates-pictures-some/7ca06735-eac2-470d-8c54-77adc7955d5c https://www.lightroomqueen.com/community/threads/lightroom-with-onedrive-keyword-metadata-conflicts.41753/ and other places. I also have the problem that I change the metadata of my images with digiKam, but that these changes are then often not accepted by OneDrive. There is then a file conflict, OneDrive renames my local files and I then have two variants. Or the changes simply do not arrive in OneDrive and are not even recognized as changes. In other words, it is not possible to reliably change image metadata when the folder is synchronized with OneDrive. So I tried the following workaround to at least have a secure and exact copy of my data somewhere: - I now use local folders for pictures and videos that are not synchronized with OneDrive - I synchronize these local folders via "Synology Drive" one-way (from the PC to the Synology) with a Synology Diskstation - "Chloud Sync" runs on the Synology to synchronize the changes from the Synology to OneDrive one-way. - The aim is for the data in OneDrive to also correspond to the local data on my PC The synchronization from the PC to the Synology works. I can compare data with WinMerge and the data on the Synology corresponds to the local data. The synchronization from the Synology to OneDrive does not work properly: I can synchronize the data from OneDrive to my PC for testing and comparison. If I now compare my original local images with those that come back to my PC via the detour "local -> Synology -> OneDrive -> local 2", many changes in the metadata of the images are not adopted.
