three times this week I have support calls from people who tell me that
my app is complaining that specialfolder.documents is returning ‘not exists’
I don’t even know how that is possible.
And the software has not been changed for 6 months.
Has anyone else encountered this?
Is there a way to get the actual place that documents are being stored?
(one customer tells me that it is Z:\documents, and that my app has no permissions to write there)
There is no guaranty you can write to My Documents on Windows.
Thats simply how Windows works.
Only place where you can always write is App Data and Common App Data.
1 Like
Hmmm.
I’ve been doing it this way for 30 years.
2025 is the first year in which I’ve heard of a problem.
‘The Web’ says it is usually OneDrive that messes this up, and for at least one customer, that’s been the case.
(Mind you, [off topic] Google searches are now extremely unreliable if you heed the AI summary.. Seems like it’s almost always wrong/hallucinating recently)
It just depends on how companies IT department has set up the Domain controller and Domain policies.
1 Like