If i install third party themes can i take sfc and DISM errors?
If MS ever fixes those commands, probably not! It'll probably 'nuke' your setup.If i install third party themes can i take sfc and DISM errors?
I will do an image of my system.
Good idea!I will do an image of my system.
Bear in mind, patching, (if that's what you intend), does not work on Builds higher than 10586.
On Build 14295, I've resorted to using 'Windows Blinds'.
I'm on 10586 and i am not used to use preview build, windows has too problems just with the official builds.
hehe, you got a point there!I'm on 10586 and i am not used to use preview build, windows has too problems just with the official builds.
Anyway, I can't endorse you messin around with your system but, if you're going to do it anyway, you better do your homework on it and back everything up.
Good luck.
In 7 had only custom themes, it's time to begin even here
W7 was a different story, it had no auto-heal capabilities. Not at this level, in any case.In 7 had only custom themes, it's time to begin even here
So Win 10 is it even less risky than 7 operating with third party themes?
Noooo.
He means The OS heals itself to some extent automatically. Where Win7 was "forgiving" of mistakes, Win10 is pro active and blocks/prohibits more.
For example UXStyle will break Performance Monitor in Win7, in Win8.1, it will break Performance Monitor and Star Screens right click menu. In the earlier builds of Win 10 it broke these and caused "Ghosting" when moving, closing and minimizing an open window.
Now it just doesn't work at all. and if you run SFC(to uninstall it, because it doesn't work) it nukes your system.
For a Shell(theme) patcher to work, it uses system32. But... system32 programs & apps are being phased out and being replaced with XAML , so the registry keys and files it needs, just are not there to patch.
You will need a shell replacement or as in the case of Blinds a shell cover, it works like Vinyl Wrapping for cars.
