|
|
Post by Splitwirez on Aug 15, 2017 9:45:01 GMT -8
Uhhh...you're 100% sure it was UxStyle? 'cause it doesn't sound like it to me. Plus, I've used UxStyle on Creators Update with no issues, sooo... .-.
|
|
|
|
Post by ocass66 on Aug 15, 2017 10:32:48 GMT -8
In all honesty, I have no clue what caused the problem. All I really know is that deleting uxtheme.dll helped because it tricked (for lack of a better word) sfc /scannow into realizing that something was wrong with my PC and fixing it.
|
|
|
|
Post by skeleton11223 on Aug 15, 2017 15:51:54 GMT -8
Something similar happened to me when updating once, it just tried to bootup and the screen would flash black and white, luckily I had a restore point right before I got uxstyle and everything was fine.
Themes are a terrible idea on Windows 10, just don't even bother with it, Microsoft doesn't want us to use our own themes.
|
|
|
|
Post by Splitwirez on Aug 17, 2017 1:11:34 GMT -8
In all honesty, I have no clue what caused the problem. All I really know is that deleting uxtheme.dll helped because it tricked (for lack of a better word) sfc /scannow into realizing that something was wrong with my PC and fixing it. Well yeah, of course sfc /scannow will notice if some of your system files are flat-out missing... ...although UxSryle doesn't even modify any system files so lol wtf Something similar happened to me when updating once, it just tried to bootup and the screen would flash black and white, luckily I had a restore point right before I got uxstyle and everything was fine. Themes are a terrible idea on Windows 10, just don't even bother with it, Microsoft doesn't want us to use our own themes. What, so just give up and let them win? No, that's easily the worst idea I've heard in a long time. Who joins a Windows customization forum, then argues that customizing isn't worth it, and says we should just give up in our quest to regain what Microsoft has taken us and to create what they never gave us? .-. |
|
|
|
Post by ocass66 on Aug 17, 2017 5:22:16 GMT -8
¯\_(ツ)_/¯
I'm just happy I didn't have to do a system restore and then reinstall the update.
|
|
|
|
Post by skeleton11223 on Oct 12, 2017 3:18:09 GMT -8
In all honesty, I have no clue what caused the problem. All I really know is that deleting uxtheme.dll helped because it tricked (for lack of a better word) sfc /scannow into realizing that something was wrong with my PC and fixing it. Well yeah, of course sfc /scannow will notice if some of your system files are flat-out missing... ...although UxSryle doesn't even modify any system files so lol wtf Something similar happened to me when updating once, it just tried to bootup and the screen would flash black and white, luckily I had a restore point right before I got uxstyle and everything was fine. Themes are a terrible idea on Windows 10, just don't even bother with it, Microsoft doesn't want us to use our own themes. What, so just give up and let them win? No, that's easily the worst idea I've heard in a long time. Who joins a Windows customization forum, then argues that customizing isn't worth it, and says we should just give up in our quest to regain what Microsoft has taken us and to create what they never gave us? .-. To be honest, using classic shell to change the taskbar and customizer god to change icons is a much better idea to use than severely crippled themes that put you in bootloops, not to mention the fact that you can't even disable auto updates making the situation 10x worse. |
|
|
|
Post by haloman30 on Oct 12, 2017 5:28:48 GMT -8
Well yeah, of course sfc /scannow will notice if some of your system files are flat-out missing... ...although UxSryle doesn't even modify any system files so lol wtf What, so just give up and let them win? No, that's easily the worst idea I've heard in a long time. Who joins a Windows customization forum, then argues that customizing isn't worth it, and says we should just give up in our quest to regain what Microsoft has taken us and to create what they never gave us? .-. To be honest, using classic shell to chabge the taskbar and customizer god to change icons is a much better idea to use than severely crippled themes that put you in bootloops, not to mention thw fact that you can't even disable auto updates making the situation 10x worse. Auto updates can be disabled in win10 pro via gpedit. I have it set that way on my win10 which still runs AU due to having similar issues on Creator's update. It wasnt a full system broke entirely, as i set default theme on before doing so. I tried slamming a theme on and...tl;dr had to reinstall. Even so i still don't think that just "not even bothering" is not at all the takeaway as its due to bothering that these will maybe eventually stop being a problem. Or at the very least be able to, as splitwirez said, regain what Microsoft has taken from us and create for ourselves what we were not given. Just seems silly to just give up when something doesn't work. Ive started just using VMware on my windows 7 to avoid breaking my actual win10 install, and I dont experiment on my real install until ive tested on a VM. If possible i'd say maybe try doing that in the future to avoid the headache of reinstalling |
|
|
|
Post by skeleton11223 on Oct 23, 2017 16:01:43 GMT -8
You can? Then I guess if you have pro and know about updates, then yeah themes are ok but when you can't disable updates, don't bother.
|
|
|
|
Post by tuxedo on Oct 24, 2017 4:38:47 GMT -8
|
|
