Reply 20 of 57, by UCyborg
If you go into its properties, you can take ownership of the file in the Security tab, Advanced button. I give the ownership to Administrators. After you take the ownership and confirm with OK, returning to that dialog will let you change permissions. You can give Administrators full control rights.
I have a habit of keeping the original file by appending .bak to its name, then copying modified version to its place. If you ever happen to run sfc /scannow to check integrity of system files, the file will be replaced with original. Though in reality, when you have a problem with Windows, it's very unlikely that some critical file that sfc checks got corrupted. My guess is that it's more likely for it to be cause in case of faulty hardware.
As much as Dism ... /RestoreHealth and sfc /scannow is preached even by guys at Microsoft in case of problems, it practically makes difference 1 times out of 10. The method of patching system files is probably the most problematic if we're talking about theming DLLs to allow usage of unsigned themes. If one of those DLLs get replaced during update, the user will be greeted with BSOD at next logon unless (s)he switched back to stock theme before restarting. The best theme patcher, UxStyle, is not updated anymore.
Anyway, I wouldn't say it's optimal, but it should be at least functional until the next big update. Windows 10 just won't work properly on my hardware, for one thing, I suspect incompatibility with my motherboard's AHCI driver. Though even in VMware and on other machines, there are some "Completing a failed IOCTL request." errors in Event Log (look for StoreDiag category). I get some other IO related errors, which might be the reason the installation managed to get corrupted to the point it was rendered unbootable a year ago.
At one point, they broke ListView control, causing mouse cursor to jump to corner of the screen. Supposedly fixed in current Insider builds. Someone developed a fix for it. I also remember there was a bug that broke some Visual Studio extensions. Explorer also has number of oddities. With default view control, scrollbar jumps up whenever a accent color changes as a result of desktop background change if you have auto-colorization enabled. At least it can be replaced with Folder Options X / QTTabBar, which also unlocks ability to arrange files freely, something possible out of the box in Explorer on Vista / XP. There's also a weird issue if you try to delete a file from the root of plain removable storage device, things like USB flash disks, the file deletion dialog will lack information about file modification date and the size will be reported as 0 bytes regardless of the actual size. Explorer is also significantly slower at counting files since Windows 8.1. It's especially bad with plain mechanical hard drives. How does MS get away with all of this? 😢
A man can be himself only so long as he is alone; and if he does not love solitude, he will not love freedom; for it is only when he is alone that he is really free.