Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Black screen after applying a theme #51

Closed
Yaron10 opened this issue May 13, 2021 · 8 comments
Closed

Black screen after applying a theme #51

Yaron10 opened this issue May 13, 2021 · 8 comments

Comments

@Yaron10
Copy link

Yaron10 commented May 13, 2021

Hello,

Thank you for msstyleEditor. I'm a complete beginner in themes editing and I appreciate your work.

I was trying to edit a Windows Theme (NOT located in Resources/Themes but in my Downloads folder) with msstyleEditor and pressed "Test".
The corrupt theme was applied and I now get a black screen on reboot.

I've read https://technastic.com/recover-from-black-grey-screen-third-party-themes-on-windows-10/ but that corrupt theme is not listed under Resources/Themes.

I've used xcopy aero "Downloads\Corrupt Theme" /i but I do not know how to run copy aero.theme "corrupt theme 01.theme".
What .theme file is Windows using now? And where is it located?

(Windows 10 20H2. Unfortunately I did not have a restore point).

This is an emergency. :) I'd appreciate your help.

@nptr
Copy link
Owner

nptr commented May 13, 2021

Hello. Sorry to hear!

Themes applied via the "Test" feature are located in "C:\Users\Public\Documents\tmpXXXXX.msstyles". When msstyleEditor closes normally, the theme is reverted back to the one used before. This temporary file is removed afterwards. There is no theme file involved, just the visual style (.msstyles).

Are you sure this temporary theme (from the "Test" feature) is the culprit? Can you remember which themes you had applied and if you deleted or copied any files while the "test" theme was active?

If you think that this temporary theme is still used by windows, you could try to replace it with a working one or maybe even delete it in the hope that windows reverts to a safe default.

@nptr
Copy link
Owner

nptr commented May 13, 2021

One user reported he was able to fix it using this approach: #32 (comment)
It think that this is the safest way to go, but I don't have any more details on it however. If you manage to solve this issue, doesn't matter how, please report back how you did it.

@Yaron10
Copy link
Author

Yaron10 commented May 14, 2021

Hello,

I've just had access to that computer.
I've replaced the tmpXXXXX.msstyles file and all is well now.

Thank you so much. I'm truly grateful. 👍


I'm a complete beginner in theme editing.
I'm even new to Win 10. I love the good old Classic Theme, and I didn't want to quit Win 7.

My system is RTL (Right To Left, Hebrew), and some potential themes on WindowsLive are not compatible.

The most important things to me are the various bars (Toolbar, MenuBar, StatusBar etc.) background color, and replacing the fonts to NON-ClearType ones. Both color and fonts system-wide.

What is my best option? Can I somehow import the Classic Theme from Win 7?
Would you be willing to help through the process?
-- If it's rather complex, I'd pay for a good and patient guide. :)

Best regards.

@nptr
Copy link
Owner

nptr commented May 14, 2021

Glad it works again. Can you remember what you did to get into this error state? msstyleEditor reverts the theme on exit, so I am a bit worried how it was still active. Did you have multiple instances running maybe?


I think your best option would be finding an existing classic theme for Win10 and further modify/fix it if necessary.
@malvinas2 (a user of msstyleEditor) has one on his Github page, I suggest you give it a try :)

Apart from that, I can only give you some basic info as I don't have much experience on the modding part itself. I'll thus have to decline your monetary offer, but:

  • For a general overview of my tool, check out the readme.
  • For changing window borders and a brief description of the image atlas concept, see here
  • Fonts, this is tricky (but possible) and not really implemented. See here.

It might also be worth checking out documentation or tutorials of Windows Style Builder. WSB is a structured a bit different and uses different but similar names for parts, but its definitely possible to transfer and apply the gained knowledge to msstyleEditor.
Some resources:

PS: If you'd like to contribute, you can always send in mini tutorials, documentation or reports bugs.

@Yaron10
Copy link
Author

Yaron10 commented May 14, 2021

Hello Jakob,

Thank you very much for the detailed and very helpful reply. It's highly appreciated.

Can you remember what you did to get into this error state?

I'm not absolutely sure, but I think I did the following steps:

  • Downloaded this theme to my Downloads folder.
  • Opened tahoma without antialiasing.msstyles in msstyleEditor.
  • I'm not sure whether I edited anything or not.
  • Ran Test in msstyleEditor.

msstyleEditor reverts the theme on exit

msstyleEditor did not exit gracefully. As soon as I ran Test I got the black screen.

Did you have multiple instances running maybe?

I think I had only one instance running.


I think your best option would be finding an existing classic theme for Win10 and further modify/fix it if necessary.
@malvinas2 (a user of msstyleEditor) has one on his Github page, I suggest you give it a try :)

Great!
I've just briefly tested it and it looks really promising.
I'll certainly contact the developer in the coming days. :)

Fonts, this is tricky (but possible) and not really implemented. See here.

I actually came across #15 earlier today.
I edited ---.msstyles.mui, followed the rest of the steps and got the Tahoma font in the Task Bar.

Interestingly - applying only this change, Firefox has some glitches:

תמונה

Note the caption buttons on both sides: native on the right and "weird" on the left.
It's RTL and my custom Firefox theme, but it also happens with Firefox default theme.

This also happens with https://github.com/malvinas2/ClassicThemeForWindows10.
I might have to discuss it with malvinas2.

If you'd like to contribute, you can always send in mini tutorials, documentation or reports bugs.

At this stage it's all so new to me.
I'd certainly be glad to contribute as soon as I got a better grasp of the material.


Allow me to thank you again for your work and the important info.

Best regards.

@nptr
Copy link
Owner

nptr commented May 15, 2021

I will consider adding a dead man's switch to the test feature, similar when changing resolution in Windows. It's not the first time a theme rendered Windows unusable...

Good luck on your undertakings! Just in case: documentation snippets and tutorials can be put here. I'll then see if and how I can integrate the information into a formal documentation.

@nptr nptr closed this as completed May 15, 2021
@nptr nptr reopened this May 15, 2021
@Yaron10
Copy link
Author

Yaron10 commented May 15, 2021

I will consider adding a dead man's switch to the test feature, similar when changing resolution in Windows.

👍
That's a great idea.

Good luck on your undertakings!

Thanks again for your kind help.

documentation snippets and tutorials can be put here.

I'll remember that.


I don't know if I should open a separate issue for the following minor improvement:
Remember msstyleEditor's window position.

Best regards.

@nptr
Copy link
Owner

nptr commented May 16, 2021

Noted ;)

@nptr nptr closed this as completed May 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants