limmy
New Member
Posts: 5
OS: Windows 10 20H2
Theme: SCT
|
Post by limmy on Oct 22, 2020 15:21:44 GMT -8
Hello, I pre-installed OpenShell and StartIsBack++ (with license) before executing the file I downloaded from you, yet this appears.  What do I do? |
|
|
|
Post by leet on Oct 22, 2020 15:31:20 GMT -8
Hello, I pre-installed OpenShell and StartIsBack++ (with license) before executing the file I downloaded from you, yet this appears. What do I do?This is a bug. Create an empty file called SCT.exe in C:\SCT |
|
|
|
Post by AbhinavN on Oct 31, 2020 13:47:24 GMT -8
Gentlemen, ye learned how to close the "themesection" handle of winlogon.exe in memory (NT Object Manager namespace), and created this and similiar previous utilities. But when disassembling ye surely have understood, which system call is behind this.
My question in about patching the "winlogon.exe" (or another responsible binary) direcly, (for example I use Windows 10 build 1607).
I understand that it would invalidate the checksum of the binary, but I am ready to boot the Windows with disabled "driver signature verification".
Who can indicate, how to patch, at which offset, which bytes?
|
|
|
|
Post by leet on Oct 31, 2020 15:10:43 GMT -8
Gentlemen, ye learned how to close the "themesection" handle of winlogon.exe in memory (NT Object Manager namespace), and created this and similiar previous utilities. But when disassembling ye surely have understood, which system call is behind this. My question in about patching the "winlogon.exe" (or another responsible binary) direcly, (for example I use Windows 10 build 1607). I understand that it would invalidate the checksum of the binary, but I am ready to boot the Windows with disabled "driver signature verification". Who can indicate, how to patch, at which offset, which bytes? Not happening. Our method (disabling the theme section, not closing it) is easier by a far stretch and actually allows for UWP fo work alongside classic theme. Further it allows for going back to the standard theme if/when anything breaks. Also doing what you said would require a new patch every update. That’s stupid |
|
|
|
Post by ihatemetro on Oct 31, 2020 16:13:04 GMT -8
Gentlemen, ye learned how to close the "themesection" handle of winlogon.exe in memory (NT Object Manager namespace), and created this and similiar previous utilities. But when disassembling ye surely have understood, which system call is behind this. My question in about patching the "winlogon.exe" (or another responsible binary) direcly, (for example I use Windows 10 build 1607). I understand that it would invalidate the checksum of the binary, but I am ready to boot the Windows with disabled "driver signature verification". Who can indicate, how to patch, at which offset, which bytes? Not happening. Our method (disabling the theme section, not closing it) is easier by a far stretch and actually allows for UWP fo work alongside classic theme. Further it allows for going back to the standard theme if/when anything breaks. Also doing what you said would require a new patch every update. That’s stupid Agreed. Patching it is way harder and you have to access startup options EVERY TIME to disable driver signature enforcement. |
|
|
|
Post by AbhinavN on Nov 4, 2020 7:22:41 GMT -8
I've got your point that we don't know how to patch the "winlogon.exe", but to disable "driver signature verification" permanently is possible with this UEFI bootkit: github.com/Mattiwatti/EfiGuard |
|
|
|
Post by ihatemetro on Nov 4, 2020 9:38:17 GMT -8
I've got your point that we don't know how to patch the "winlogon.exe", but to disable "driver signature verification" permanently is possible with this UEFI bootkit: github.com/Mattiwatti/EfiGuardWell, does it support secure boot? Can it be signed using Hashtool on rEFInd easily without having to sign dozens of files if it doesn't? Edit: It works, but it keeps opening OpenCore instead of Windows. UGH. |
|
|
|
Post by dulcedeclown on Nov 8, 2020 5:05:38 GMT -8
Hello everyone,
I hope this is the right place to post this, but I have an issue while using this classic theme tool (I am currently using Windows 10 Pro 1909).
Almost everything works as intended but one thing doesn't and that was the reason I wanted to try this theme in the first place, and that is the title bar of all windows.
My explorer (and every other window) just didn't want to cooperate and the classic theme wouldn't apply correctly to these bars.
How can I use this tool (or other tools/ways) to ONLY apply changes to the title bar of the windows?
I don't know if this information can be of help but customization-wise I am only using Classic Shell (latest stable version 4.3.1) to change the start menu, then everything is normal/vanilla.
|
|
|
|
Post by ihatemetro on Nov 8, 2020 6:34:47 GMT -8
Hello everyone, I hope this is the right place to post this, but I have an issue while using this classic theme tool (I am currently using Windows 10 Pro 1909). Almost everything works as intended but one thing doesn't and that was the reason I wanted to try this theme in the first place, and that is the title bar of all windows. My explorer (and every other window) just didn't want to cooperate and the classic theme wouldn't apply correctly to these bars. How can I use this tool (or other tools/ways) to ONLY apply changes to the title bar of the windows? I don't know if this information can be of help but customization-wise I am only using Classic Shell (latest stable version 4.3.1) to change the start menu, then everything is normal/vanilla. So what do you mean by "not applying correctly"? Is it transparent? Is it still the default titlebar? If it's the former, try this: www.winclassic.net/thread/215/dwmunextendframe-extended-glass-titlebar-remover BTW try Open-Shell, it's open-source Classic Shell with some new features: github.com/Open-Shell/Open-Shell-Menu . |
|
|
|
Post by dulcedeclown on Nov 8, 2020 6:44:30 GMT -8
Hello everyone, I hope this is the right place to post this, but I have an issue while using this classic theme tool (I am currently using Windows 10 Pro 1909). Almost everything works as intended but one thing doesn't and that was the reason I wanted to try this theme in the first place, and that is the title bar of all windows. My explorer (and every other window) just didn't want to cooperate and the classic theme wouldn't apply correctly to these bars. How can I use this tool (or other tools/ways) to ONLY apply changes to the title bar of the windows? I don't know if this information can be of help but customization-wise I am only using Classic Shell (latest stable version 4.3.1) to change the start menu, then everything is normal/vanilla. So what do you mean by "not applying correctly"? Is it transparent? Is it still the default titlebar? If it's the former, try this: www.winclassic.net/thread/215/dwmunextendframe-extended-glass-titlebar-remover BTW try Open-Shell, it's open-source Classic Shell with some new features: github.com/Open-Shell/Open-Shell-Menu . Sorry for not being specific enough, I meant not applying at all, it still is the default titlebar unfortunately  and it doesn't give me any error code at all, it just applies the theme like it's supposed to but the titlebar remains vanilla/unchanged. Also, I'll take a look at Open-Shell  tyvm! |
|
|
|
Post by leet on Nov 8, 2020 6:46:52 GMT -8
Well, that's the one thing this application should do right. Note that it only applies the theme on title bars created after you enable the classic theme. Do you get any specific errors or visual glitches?
|
|
|
|
Post by ihatemetro on Nov 8, 2020 6:47:48 GMT -8
Sorry for not being specific enough, I meant not applying at all, it still is the default titlebar unfortunately Also, I'll take a look at Open-Shell tyvm! Hmm... Weird. Does the Classic Theme itself apply, or is it still the default theme? (Excluding the titlebars) |
|
|
|
Post by dulcedeclown on Nov 8, 2020 6:50:01 GMT -8
Well, that's the one thing this application should do right. Note that it only applies the theme on title bars created after you enable the classic theme. Do you get any specific errors or visual glitches? Unfortunately i get no errors nor visual glitches, at least for the short time I kept using the classic theme (a full day with multiple restarts). What do you mean by "title bars created after you enable the classic theme"? Should I do something else in order do "activate" the classic theme titlebar?  (also, i do not know if "fast replying" is considered spamming, if so I am sorry!) Sorry for not being specific enough, I meant not applying at all, it still is the default titlebar unfortunately Also, I'll take a look at Open-Shell tyvm! Hmm... Weird. Does the Classic Theme itself apply, or is it still the default theme? (Excluding the titlebars) The classic theme does apply itself correctly, just not the titlebar, but the windows are changed to the correct theme colours etc. Maybe I'll re-install it later and post a screenshot if needed! |
|
|
|
Post by leet on Nov 8, 2020 6:52:06 GMT -8
I mean that any programs that are open before SCT enables the classic theme, actually use the default win10 theme. I hear you have restarted multiple times, could it be that you didn't have SCT setup to auto launch on boot?
(I think everyone here is ok with fast replying)
|
|
|
|
Post by ihatemetro on Nov 8, 2020 6:55:50 GMT -8
Well, that's the one thing this application should do right. Note that it only applies the theme on title bars created after you enable the classic theme. Do you get any specific errors or visual glitches? Unfortunately i get no errors nor visual glitches, at least for the short time I kept using the classic theme (a full day with multiple restarts). What do you mean by "title bars created after you enable the classic theme"? Should I do something else in order do "activate" the classic theme titlebar? (also, i do not know if "fast replying" is considered spamming, if so I am sorry!) Hmm... Weird. Does the Classic Theme itself apply, or is it still the default theme? (Excluding the titlebars) The classic theme does apply itself correctly, just not the titlebar, but the windows are changed to the correct theme colours etc. Maybe I'll re-install it later and post a screenshot if needed! What leet meant was that only NEW applications after the Classic Theme was enabled will have the classic titlebar. Also, that's super bizarre that only the titlebars are still the default. You can post a screenshot. And yep, fast replying is not spamming. |
|
|
|
Post by dulcedeclown on Nov 8, 2020 6:56:41 GMT -8
I mean that any programs that are open before SCT enables the classic theme, actually use the default win10 theme. I hear you have restarted multiple times, could it be that you didn't have SCT setup to auto launch on boot? (I think everyone here is ok with fast replying) Good to hear that Oh I understood what you meant now and yeah, I have also tried to enable SCT to auto launch on boot but titlebar still remained win10 vanilla because I also thought that it was some kind of weird bug that prevented the classic titlebar to apply if not done at launch/startup, but nope that wasn't the problem apparently Anyway thank you for the replies/help ^^ EDIT : I'll try to re-install it now and take a screenshot! |
|
|
|
Post by ihatemetro on Nov 8, 2020 6:59:20 GMT -8
I mean that any programs that are open before SCT enables the classic theme, actually use the default win10 theme. I hear you have restarted multiple times, could it be that you didn't have SCT setup to auto launch on boot? (I think everyone here is ok with fast replying) Good to hear that Oh I understood what you meant now and yeah, I have also tried to enable SCT to auto launch on boot but titlebar still remained win10 vanilla because I also thought that it was some kind of weird bug that prevented the classic titlebar to apply if not done at launch/startup, but nope that wasn't the problem apparently Anyway thank you for the replies/help ^^ EDIT : I'll try to re-install it now and take a screenshot! If all is successful than you can post your screenshot in the "Screenshot" board. Glad everything is working. |
|
|
|
Post by dulcedeclown on Nov 8, 2020 7:09:48 GMT -8
Good to hear that Oh I understood what you meant now and yeah, I have also tried to enable SCT to auto launch on boot but titlebar still remained win10 vanilla because I also thought that it was some kind of weird bug that prevented the classic titlebar to apply if not done at launch/startup, but nope that wasn't the problem apparently Anyway thank you for the replies/help ^^ EDIT : I'll try to re-install it now and take a screenshot! If all is successful than you can post your screenshot in the "Screenshot" board. Glad everything is working. Well since it's not working completely I'll post it here to not split the convo in two threads, hopefully I can do that or else I'll remove the attachment later It's actually working on every window now EXCEPT explorer the windows are both active because I edited the screenshot to include both of them in one picture and not upload two different screenshots. I'm actually thinking that it may be classic shell's fault? Even though I don't know how and if it affects the explorer titlebar at all. EDIT : It won't apply to explorer and other windows such as control panel (not the "app" look-like one) but it does apply to pretty much all windows Attachments:
|
|
|
|
Post by ihatemetro on Nov 8, 2020 7:12:22 GMT -8
If all is successful than you can post your screenshot in the "Screenshot" board. Glad everything is working. Well since it's not working completely I'll post it here to not split the convo in two threads, hopefully I can do that or else I'll remove the attachment later  It's actually working on every window now EXCEPT explorer  the windows are both active because I edited the screenshot to include both of them in one picture and not upload two different screenshots. I'm actually thinking that it may be classic shell's fault? Even though I don't know how and if it affects the explorer titlebar at all. Go to File Explorer Settings (either using the explorer command bar or Control Panel) > View > Check Launch Folder Windows in a separate process. BTW, were those icons part of a pack that you can install, or were those manually installed? |
|
|
|
Post by dulcedeclown on Nov 8, 2020 7:15:20 GMT -8
Well since it's not working completely I'll post it here to not split the convo in two threads, hopefully I can do that or else I'll remove the attachment later It's actually working on every window now EXCEPT explorer the windows are both active because I edited the screenshot to include both of them in one picture and not upload two different screenshots. I'm actually thinking that it may be classic shell's fault? Even though I don't know how and if it affects the explorer titlebar at all. Go to File Explorer Settings (either using the explorer command bar or Control Panel) > View > Check Launch Folder Windows in a separate process. OMG! You're a lifesaver it works now! It looks kinda bugged/glitched but I'm pretty sure it's the problem that has been mentioned at the start of this convo, so I'll try that fix and report if everything is solved! YUP! The "DwmUnExtendFrame - Extended Glass Titlebar Remover" fixed the glitched look of the titlebar, now the classic theme works perfectly! Thank you very much ihatemetro and ʇǝǝๅ ftw for the generous and fast help  |
|
and it doesn't give me any error code at all, it just applies the theme like it's supposed to but the titlebar remains vanilla/unchanged.
tyvm!
the windows are both active because I edited the screenshot to include both of them in one picture and not upload two different screenshots.