Circular blue arrows never go away on many files

This problem is still in 2025, and if you search online you can see it's been around for at least a decade.

I did some more testing, the EXACT same issue is with OneDrive, OwnCloud, NextCloud, and some others which makes me to believe it's maybe not an issue by each of these applications but something in the general DLL's provided by Microsoft.

Sadly microsoft will of course just as with the MSXML3.DLL error I had to fix for Microsoft back in 2006 or 2007, can't remember exact year anymore, but they will ignore and deny it.

Back then there's the Memory Allocation Error when loading tons of XML files for Civilization IV.

Eventually after many testing and compilations of the sdk I could only conclude it has to be in the MSXML3.dll (of which I don't have the source) so I couldn't pinpoint it.

But I reported it to MS and they basically said they are the supreme superior master race, they know everything, they are perfect and flawless..

After many debugging without source sadly, but one can still do assembler and memory dumps and so forth I could proof it's the MSXML3.dll where the error is.

I then send again with all my findings an email.

2 weeks later they brought out the patch. NEVER acknowledged their racism, fascism and arrogance! 

There's no "Thank you for doing our job" or a "Sorry we are racists and assholes here at MS" don't expect anything from the master race.

That's the MS mode of operandi.

So don't expect them to fix this bug. It ain't going to be fixed unless I or someone else, just as back then with the MSXML3.dll bug will invest hundreds of hours searching for bugs in MS source code, without us actually having the source code.

Sadly I don't have the time anymore I had back then being a student. Now my time is too limited to fix yet again another bug for MS master race.

Always keep in mind the people working for MS are the supreme superior master race. They are perfect and flawless and any issue you have, it's always you as the Untermensch who's to blame! Don't expect anything from MS, unless you do the work for them to pinpoint where the error is.

And this error, my belly is usually extremely accurate, tells me is again in one of their dll's