Windows 10: Why do people at microsoft have a toxic behavior of not applying view settings to...

I am trying to figure out how to apply a custom view of a library to its subfolder, but apparently people at Microsoft refuse to make this feature available to its users in windows 10, whereas it was available in windows 8, 7, vista and xp, and before.... It cannot be a bug, since the lack of this feature is so obvious.


This happens on a fresh and clean install of windows 1809. No personal programs have been installed. I ran:


DISM /Online /Cleanup-Image /CheckHealth
DISM /Online /Cleanup-Image /ScanHealth
DISM /Online /Cleanup-Image /RestoreHealth

sfc /scannow


and no corruption of any file is reported.


In order to replicate, you go to a library, like 'Documents'', then you change your view, like ''details'' and swap a column with another, like swapping ''size'' with ''name''. Then you create a folder in this library, and go to this folder. This folder is displayed with the default view and the default order of columns: name first , then the other columns.

Or you can go to 'Pictures', choose view ''Details'', then open a folder in this library and it will be the default view for ''Pictures''....



I genuinely want to know why do people at microsoft cling to their toxic behavior of removing this feature of custom view applied to subfolders of a library like "Documents'' ? What is the malicious motivation of these people ?

:)

 

View settings not applied to Library sub-folders

I understand the need to reset some customizations after an upgrade, but that's not really addressing the question. I've gone through and updated my folder views as desired for my local disk. However, the view settings are not applied to libraries.

For example, there is a Documents library by default which includes C:\Users\<user>\Documents. If I go to that specific address, the view settings are customized as I'd like. However, if I view Libraries\Documents it's using some default view setting for
General Items which I've already overwritten (yet it is not applied). If I take the time to change the view for Libraries\Documents, I cannot use "Apply to All" from the Folder Options | View settings, and I have to go through every individual sub-folder to
get everything displayed as I like. This cannot be a purposeful decision on Microsoft's part since the behavior didn't happen when upgrading from W8.1 to W10. It was only after the 1607 upgrade that this presented itself.

Surely there is a way to set folder view settings for Libraries in a manner that they can be applied globally.

 

Libraries View set to a folder will not apply to all it's sub folders


So, as suggested by Brink, I started a new thread for this issue.

Brink you stated ''Just to note, that folders in a library share the same folder view as it was when last closed. This isn't the same as the folders in "This PC".

Yes, this is (supposed to be) true .

Up to Windows 8.1 when you chose a view to folders in a specific library this view would apply to all sub folders of that library and stay if closed and re opened. This would work by individual library. *sarc



So, I chose my view, closed the library, re opened and looked at a sub file. Here is the result.





As you can see, the setting does not apply to the sub folders of that library. It will apply to all the main folders only. Each sub folder has to be set individually in view settings. This makes no sense and is really not practical. *Sad

Like I said, this is a step back from earlier versions of Windows. I've looked everywhere for a fix but I'm at a loss.

Thanks for your help.

 

Registry strange behavior in HKEY_CURRENT_USER\Software\Microsoft\...


I tried to clear all contents of
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts
then set security permission to logger user name () to be clear from:

• create key
• set value

and let it inherently apply to all keys under it

But it responds with icons flickering / blinking very often
so I undo the security setting.. but while keeping on registry browsing under this key I came across:

1. The jpg filetype key and userchoice key were created
2. On userchoice key the logging user () ACL was created, and
3. It's set to DENY on SET VALUE !

Is it windows 10 behavior or an intruder's been screwing up ?
Please help me.. many thanks in advance