Once again my documents continually revert to "hidden" setting in properties

From time to time, Windows 10 forces an update and somehow destroys the administrative structure on our computers. I don't know why this happens or how to fix it, how to repair it, and most importantly, how to permanently defend my computer against such Microsoft attacks.

I am the sole user and "administrator" of my computer. Yet my documents ... such as photos, videos, pdfs,... are continually reverted to the "hidden" attribute in properties. I have unset the "hidden" attribute setting on my documents countless times. But next time I return to the computer, the files will have all been reverted to the hated "hidden" file attribute.

It is also a frequent occurrence to find that my documents have been marked in the properties as "this file came from another computer" and I have to "unblock" the files in order for some software to be able to see them, and access them in the normal way.

I would very much like to have these nuisances eliminated. I am hoping that there is a way to prevent the "file came from another computer" setting from ever being imposed via the security software components of Windows (ie. the firewall perhaps?) We all interact with the internet; that means taking in files from "other computers." I don't want to be protected from using my computer by Microsoft.

I am really tired of Microsoft taking away our administrative rights also, and changing all MY documents (OUR personal documents!) to "hidden". Why must thousands of photographs be "hidden"?

Microsoft also forces all of my document folders to be "Read-Only"... another characteristic that I do not want applied to my computer, but about which there is nothing I can do.

I apologize for the redundant writing of the message. I'm trying my best to be clear about what I need, and hoping that someone can help. There has to be some way to prevent Microsoft from dominating every waking hour we are not at our jobs, by forcing us to repair the errors, mistaken atributions, and file properties that it seeks to screw up. Thank you all for your generosity in looking at the forum, and for possibly helping us.