Exactly Luka. Same here.
This is one of a number of program faults that have existed for many years. There are no unambiguous solution because they can be caused by any of a number of different system states. Because of cybersecurity, vendors are forced to patch and update software
continually. The size and complexity of the programs is such that exhaustive testing is not practical.
You've probably noticed that support fora like this one are full of instances where users report success only to follow-up with a whoops! it's back again post.
What Microsoft (and every other IT software vendor on the planet) has forgotten, is that the users and user interfaces are a parts of the system. The way software is designed and remotely maintained, software configuration management does not exist. The
best any of these "crowd-sourced" volunteer operations can do, is tell you what worked in their particular configuration and code base, at the particular state the hardware and software were in at the moment. (The details of the code changes in are not available
to the user for a combination of proprietary and cybersecurity concerns.)
Sparing the details, one of the things that it appears several hundred thousand of us are struggling with is a recurring inability to access network attached storage. Some solutions appear to work some of the time or until the next update. (I've been in
the digital system design business for about half a century. I'm not up to following 14 pages of detailed instructions like, "change the XDFG setting in line 341 of the RRTWQ module to 55t77YHI***h9923llkjlbhh442%!q".
On the other hand, after 50 years I have a pretty good intuitive sense of the root causes of what I'm seeing. Yesterday, relying on that instinct I finally got the system to recognize the NAS and display the directory structure with the files, by doing
something suggested to solve another problem (the green ribbon of death). This was a major improvement over the previous two days, when, by rebooting everything I could occasionally get the system to display the drive and the folders but no files. (Using
Properties I was able to determine that I had 208 GBytes of data stored, and a potload of folders with 0 bytes in them.)
Again, experience cautioned me that it was too soon to celebrate. I tried to load a file. The result was simply mindboggling.
A page generated by Microsoft appeared with a prominent banner reading: "Join the Celebration -- Get the Windows 10 Anniversary Update today!!" The content of the page informed me "Your App doesn't work with Windows 10," and directed me to go to the App
developers Website for a solution.
What App was not specified, and I was clueless, since all I had done was double click on a filename to see if it would load.
At which point the Windows 10 viewer archly informed me, ""We can't open this file."
There is no way that an average user can deal with this level of insanity.