|
|
Post by faenus on Jan 3, 2020 8:33:49 GMT -8
Unfortunately my fears got verified. It's nearly impossible to keep .NET like this. It needs "Windows Features" to be present, which itself needs "WinSxS" to exist, which is 4Gigabytes in itself. And I really doupbt I can Junction that one. It's the most mysterious Windows conjuration.
Anyhow. Thanks for all the help.
|
|
|
|
Post by leet on Jan 3, 2020 8:48:51 GMT -8
Unfortunately my fears got verified. It's nearly impossible to keep .NET like this. It needs "Windows Features" to be present, which itself needs "WinSxS" to exist, which is 4Gigabytes in itself. And I really doupbt I can Junction that one. It's the most mysterious Windows conjuration. Anyhow. Thanks for all the help. You managed to delete WinSxs. Man your talking REALLY compact installations. Why would you ever need such a compact install xD. |
|
|
|
Post by faenus on Jan 4, 2020 1:56:28 GMT -8
btw the application works just fine, it just throws a .NET exception whenever the /enableauto is used, I am guessing with probably other switches too, but still very much usable. Wish I knew what "enableauto" does and try to do it manually if possible.
|
|
|
|
Post by anixx on Jan 4, 2020 2:40:37 GMT -8
Since the application is .NET, will it work on Android processors?
|
|
|
|
Post by leet on Jan 4, 2020 4:53:35 GMT -8
Since the application is .NET, will it work on Android processors? Assuming your talking Windows IoT: No, the problem with that is that .NET Framework 4 isn't compatible with ARMv7 or even ARM64 chipsets. |
|
|
|
Post by leet on Jan 4, 2020 5:03:18 GMT -8
btw the application works just fine, it just throws a .NET exception whenever the /enableauto is used, I am guessing with probably other switches too, but still very much usable. Wish I knew what "enableauto" does and try to do it manually if possible. What is the exception? If your running it first time: you have to run it without any arguments so that the GUI will load. Btw don't run the command line switches, they are currently broken. |
|
Jack
New Member
Posts: 5
OS: Windows 10 LTSC 2019 (1809) / macOS 10.15 Catalina
|
Post by Jack on Jan 5, 2020 3:33:52 GMT -8
Hi all, this is my first post on this forum, so I hope I can get some help with the issue I'm experiencing with trying to run SCT. OS: Windows 10 1809 LTSC SimpleClassicTheme version: SCT 1.0.5.0 Describe the bug/problem: The issue I'm experiencing with SCT is in regards to File Explorer freezing whenever I try and launch an instance of it once the classic theme is enabled. At first I couldn't even get Explorer to work with SCT, as every other program I would launch would work just fine with the classic theme enabled except File Explorer which had the default Win10 UI, however then I realised I had to enable "Launch folder windows in a seperate process" in Folder Options to resolve that problem, but once enabled, any Explorer window I now try and open will just hang.  This is a clean install of Win10 1809 LTSC in a VM (sorry about the Mac screenshot lol, my daily PC is down so my only computer at this time is a MacBook) and I followed the SCT guide to a tee just to make sure I'm doing everything correctly. Is there anything I'm doing wrong or may have missed? Is LTSC an issue, as I do prefer it to the normal versions of Windows 10 due to its simplicity. Another issue I noticed is upon a reboot, the classic theme will not auto-enable despite having clicked the "Install" button which in theory should auto launch the theme, unless I'm mistaken and it's by design that I have to open it every time to enable the theme. Anyways any help would be much appreciated. Thanks. |
|
|
|
Post by frankyjackson on Jan 5, 2020 20:29:31 GMT -8
For some reason "Install Required Stuff" is greyed out for me.  |
|
|
|
Post by faenus on Jan 6, 2020 7:36:31 GMT -8
Having the same problem as Jack, but I thought is meant to happen for all new Metro Apps and Immersive Control Panel, also happening with all those other tools suspending window manager, so I thought is normal.
I too use LTSC, if that's making any difference, and explorer actually totally hangs and needs either log off or restart.
|
|
|
|
Post by anixx on Jan 6, 2020 7:41:11 GMT -8
Having the same problem as Jack, but I thought is meant to happen for all new Metro Apps and Immersive Control Panel, also happening with all those other tools suspending window manager, so I thought is normal. I too use LTSC, if that's making any difference, and explorer actually totally hangs and needs either log off or restart. I think your problem has been described: www.winclassic.net/thread/343/1809-kills-explorer-classic-themeIt affects only one of the Win10 builds (unfortunately, the one on which LTSC is built). |
|
|
|
Post by leet on Jan 6, 2020 10:12:40 GMT -8
faenus and JackAs anixx said this problem is a known issue for Win10 LTSC. Currently not sure if there's a fix though. frankyjackson Do you have Open-Shell and StartIsBack++ already installed?
|
|
|
|
Post by The Jackal on Jan 6, 2020 14:02:43 GMT -8
LTSC 2019 is based on build 1809, the same build MS screwed up and removed a dll in their efforts to appease the masses with Dark theme, only to correct it in the next build and restore it. That dll is needed for Classic theme to show properly, so that's why File Explorer hangs. Downgrade to LTSB 2016 or "upgrade" to Home/Pro on 1903+.
|
|
|
|
Post by anixx on Jan 7, 2020 7:40:22 GMT -8
I think on Win 8.1 SCT should not install Startisback or whatever but run before the taskbar and then make the necessary fixes to taskbar (setwindowcompositionattribute and fixstrips). Particularly, to fix the taskbar appearance on Win 8.1 the following two steps are enough: 1. SetWindowCompositionAttribute.exe class Shell_TrayWnd blur false
using this program: www.glass8.eu/files/SetWindowCompositionAttribute.7zI think the same can be done using purely APIs, without calling the utility though. 2. Run fixstrips.exe www.winclassic.net/attachment/download/168Again, the same can be done using APIs, fixstrips.exe contains the following AHK script: WinSet, Style, +0x400000 , ahk_class Shell_TrayWnd
WinSet, Style, -0x400000 , ahk_class Shell_TrayWnd
|
|
|
|
Post by leet on Jan 7, 2020 7:56:11 GMT -8
anixx I've already stated that I'm currently working on a fix for it. Also completely redesigning the UI because it was cluttered. BTW Both of those taskbar fixes are completely implemented via API calls. And last but not least: from now on I want issues on the github issue tracker, mainly because it keeps track of what is solved and what bugs are still there.
|
|
|
|
Post by leet on Jan 7, 2020 11:06:11 GMT -8
OK, The Win8.1 support works beautifully. 1 issue I need to fix before release: Metro apps Metro apps require explorer to be running WITHOUT admin privileges.
The problem is that when you run Process.Start("cmdline"); in a .NET application that has admin privileges, the created process will inherit those administrator privileges. Does ANYONE know how to fix this?
Solution: Run that process via explorer
|
|
|
|
Post by leet on Jan 7, 2020 11:56:21 GMT -8
- Actual support for Windows 8.1 (Not with Windows 8!!!!)
- Now includes Open-Shell instead of manual download
- Added auto-updater
- Revamped UI
|
|
|
|
Post by Splitwirez on Jan 7, 2020 14:52:42 GMT -8
|
|
|
|
Post by anixx on Jan 8, 2020 4:22:35 GMT -8
It seems your Win8.1 screenshot does not include ClassicShell for whatever reason, which would be useful.
|
|
|
|
Post by anixx on Jan 8, 2020 4:41:32 GMT -8
Some comments regarding your guide. 1. You put "make borders 3D" into "installing utilities" section. I think this may be confusing because it is a purely registry tweak. 2. Removing the folder band (navbar). You suggest <Element padding="rect(0rp,0rp,0rp,-28rp)"/> We with ROB found that this still leaves 2px from navbar, one should better use rect(0rp,0rp,0rp,-30rp) instead. You may also want to include some info on how to fix the problematic control panel pages: www.winclassic.net/thread/459/fixed-control-panel-pages-win8 |
|
|
|
Post by leet on Jan 8, 2020 10:45:16 GMT -8
anixx, First of all, by default SCT doesn't install any additional software on Win8.1. I will make an option though for installing Open-Shell. Secondly, I changed the two things you noted in the guide, though I currently don't have time to write up on the control panel pages so I'll do that later.
|
|
