.

.

bitflipper
Windows 8 loves read-only folders and can be a real PIA in that regard. Sometimes, there is a reasonable rationale for doing so. For example, some system folders are intentionally (and permanently) read-only because Windows wants to manage them exclusively. Sometimes, Windows maintains a separate folder that you can write to, but makes it appear as though it's part of the read-only system folder. Take the RO flag off those folders and Windows puts it right back on.

 
At least some of this is on the developer - they want to write to places they aren't supposed to write to. This is mainly a problem with very old SW, but not always. So some of this is really just for backwards compatibility. Having C:\Users\username\AppData\Local\VirtualStore allows me to still run some SW so old (like emagic's SoundDiver midi editor/librarian) that it uses win.ini for its configuration info (!).
 
But they have been embracing confusion ever since they invented "My Documents" as a linked directory that doesn't really exist and forced programmers to only write to where it really was, but at least programmers can figure it out in short order. But by trying to make things easy for the nontechnical but never making it clear for anyone not so clueless that they can't even navigate a folder tree, it just makes it more confusing because things aren't really where they seem to be.
 

Just accept that those over-caffeinated 20-somethnig propeller-heads at Microsoft are smarter than you and know what's best for you. Fall in line or go Linux.

Let's remember of course that Microsods got the idea for linking from Unix. 

But is the new content changing to RO?