|
Post by anixx on May 31, 2022 3:31:30 GMT -8
I may be wrong, but my impression is that Ribbon Disabler changes system files (replaces resources in a dll), while ONE replaces the resource in memory, while EP only changes the registry. EP doesn’t work in a separate process: ExplorerPatcher only exists in the shell process, when you have a separate process for a file window, it won’t hook EP into it. No, this is wrong. It injects in all processes, even in open/save dialogs.
|
|
sbal
Freshman Member
Posts: 28
|
Post by sbal on Jun 23, 2022 8:10:42 GMT -8
This doesnt work. I followed the tutorial step by step and ended up with this As you can see, I have a Windows 10 desktop, File Explorer is completely unchanged, and my taskbar is white on white. What did I do wrong here?
|
|
|
Post by anixx on Jun 23, 2022 8:56:47 GMT -8
I do not know, what you did wrong. Evidently, you do not have classic theme enabled. Does it get enabled if you manually run the Classic task in task scheduler?
|
|
|
Post by anixx on Jun 23, 2022 8:58:15 GMT -8
Make sure you have changed the userinit key in the registry (point 6) - do it manually.
|
|
sbal
Freshman Member
Posts: 28
|
Post by sbal on Jun 27, 2022 5:51:03 GMT -8
Make sure you have changed the userinit key in the registry (point 6) - do it manually. I did check that, and I did have to set it manually, which I did. I right clicked the Taskbar Icon and selected "Classic mode". When I run Notepad, I get a "pseudo classic mode" with some odd border, but nothing like the picture in the OP. I did not see any instruction to run the scheduled tasks, and also did not see any instruction on when to set them to run, that seems to be missing. Can we update the guide to include those steps? I understand the difficulty in making comprehensive guides (I write them as part of my job) and it is easy to assume folks know what steps to take, and there seems to be a few of those in the guide. For example, I don't know what that "AHK" script is or what it does or how to run it. I have restored an earlier version of the Windows 10 VM and will try these steps again.
|
|
|
Post by anixx on Jun 27, 2022 7:00:45 GMT -8
Make sure you have changed the userinit key in the registry (point 6) - do it manually. I did check that, and I did have to set it manually, which I did. I right clicked the Taskbar Icon and selected "Classic mode". When I run Notepad, I get a "pseudo classic mode" with some odd border, but nothing like the picture in the OP. I did not see any instruction to run the scheduled tasks, and also did not see any instruction on when to set them to run, that seems to be missing. Can we update the guide to include those steps? I understand the difficulty in making comprehensive guides (I write them as part of my job) and it is easy to assume folks know what steps to take, and there seems to be a few of those in the guide. For example, I don't know what that "AHK" script is or what it does or how to run it. I have restored an earlier version of the Windows 10 VM and will try these steps again. The classic theme should be run from the task, not from a tray icon. All necessary steps are already in the guide, just follow it precisely. Other users (as you can see from comments) had set up it successfully.
|
|
sbal
Freshman Member
Posts: 28
|
Post by sbal on Jun 27, 2022 11:12:13 GMT -8
I did check that, and I did have to set it manually, which I did. I right clicked the Taskbar Icon and selected "Classic mode". When I run Notepad, I get a "pseudo classic mode" with some odd border, but nothing like the picture in the OP. I did not see any instruction to run the scheduled tasks, and also did not see any instruction on when to set them to run, that seems to be missing. Can we update the guide to include those steps? I understand the difficulty in making comprehensive guides (I write them as part of my job) and it is easy to assume folks know what steps to take, and there seems to be a few of those in the guide. For example, I don't know what that "AHK" script is or what it does or how to run it. I have restored an earlier version of the Windows 10 VM and will try these steps again. The classic theme should be run from the task, not from a tray icon. All necessary steps are already in the guide, just follow it precisely. Other users (as you can see from comments) had set up it successfully. Am I reading the right set of instructions? Maybe I am looking at the wrong place? I saw these steps: Those steps do not say to run the task, or when to set the task to run (at startup?). It just says to turn on the any power source option, which I did. Do I set it to run at startup? A log on? Do I run it manually?
|
|
sbal
Freshman Member
Posts: 28
|
Post by sbal on Jun 27, 2022 11:45:57 GMT -8
So I started with a fresh Win 10 VM I followed the steps precisely. I did the following: - I installed classic Task Manager
- I put ClassicThemeTray.exe into C:\Classic
- I created the three Scheduled Tasks, copy and pasting each action exactly, and set them to run at any power source
- I manually set the Userinit registry key
I then ran the "Classic" Task. This is what I got winver and notepad look "classic-ish", explorer looks the same as always. Did I miss a step?
|
|
|
Post by OrthodoxWin32 on Jun 27, 2022 13:43:23 GMT -8
So I started with a fresh Win 10 VM I followed the steps precisely. I did the following: - I installed classic Task Manager
- I put ClassicThemeTray.exe into C:\Classic
- I created the three Scheduled Tasks, copy and pasting each action exactly, and set them to run at any power source
- I manually set the Userinit registry key
I then ran the "Classic" Task. This is what I got winver and notepad look "classic-ish", explorer looks the same as always. Did I miss a step? I think yours is that the explorer starts before Classicthemetray. Normally, it should be the opposite. Have you configured the task (the one that contains the three commands) with the "Execute with maximum authorizations" option and the "Execute only if the user is connected" option ?
|
|
|
Post by ihatemetro on Jun 27, 2022 15:56:32 GMT -8
So I started with a fresh Win 10 VM I followed the steps precisely. I did the following: - I installed classic Task Manager
- I put ClassicThemeTray.exe into C:\Classic
- I created the three Scheduled Tasks, copy and pasting each action exactly, and set them to run at any power source
- I manually set the Userinit registry key
I then ran the "Classic" Task. This is what I got winver and notepad look "classic-ish", explorer looks the same as always. Did I miss a step? Go to File Explorer Options and enable "Launch folder windows in a separate process". This will make file explorer have the classic theme. You also need OldNewExplorer. The ribbon is slightly broken in classic theme. Also, to make the theme look even more classic you need the classic desk.cpl and some registry file which allows you to select the colour schemes from said desk.cpl. Edit: If you also want the taskbar to be classic as well, use something like retrobar and create a scheduled task (or just a script) that restarts explorer after the classic theme gets enabled. To have retrobar start on startup simply just paste its exe into "shell:common startup" (just type that in the explorer address bar).
|
|
|
Post by anixx on Jun 27, 2022 17:24:27 GMT -8
winver and notepad look "classic-ish", explorer looks the same as always. Did I miss a step? You should re-login to have everything Classic-themed. After you did all the steps, exit session end re-login. If you did all right, it will be classic.
|
|
|
Post by anixx on Jun 27, 2022 17:27:10 GMT -8
Go to File Explorer Options and enable "Launch folder windows in a separate process". This will make file explorer have the classic look. You also need OldNewExplorer. The ribbon is slightly broken in classic theme. Also, to make it look even more classic you need the classic desk.cpl and some registry file which allows you to select the colour schemes. This will NOT affect the Explorer's look. Please don't tell what you do not know. The ribbon can be removed by Explorer Patcher, this is in the manual, p.13. One does not need OldNewExplorer. The deskn.cpl is linked in the manual at p.10.
|
|
|
Post by anixx on Jun 27, 2022 17:34:24 GMT -8
I think yours is that the explorer starts before Classicthemetray. Normally, it should be the opposite. Have you configured the task (the one that contains the three commands) with the "Execute with maximum authorizations" option and the "Execute only if the user is connected" option ? It seems, he did not re-login after doing the steps, so the tasks never get started.
|
|
|
Post by ihatemetro on Jun 28, 2022 6:20:39 GMT -8
Go to File Explorer Options and enable "Launch folder windows in a separate process". This will make file explorer have the classic look. You also need OldNewExplorer. The ribbon is slightly broken in classic theme. Also, to make it look even more classic you need the classic desk.cpl and some registry file which allows you to select the colour schemes. This will NOT affect the Explorer's look. Please don't tell what you do not know. The ribbon can be removed by Explorer Patcher, this is in the manual, p.13. One does not need OldNewExplorer. The deskn.cpl is linked in the manual at p.10. I'm talking about how it will make it actually HAVE the classic theme instead of the default Windows 10 theme. I am not saying that it will make file explorer look like it did in previous versions of Windows.
|
|
|
Post by OrthodoxWin32 on Jun 28, 2022 6:31:56 GMT -8
This will NOT affect the Explorer's look. Please don't tell what you do not know. The ribbon can be removed by Explorer Patcher, this is in the manual, p.13. One does not need OldNewExplorer. The deskn.cpl is linked in the manual at p.10. I'm talking about how it will make it actually HAVE the classic theme instead of the default Windows 10 theme. I am not saying that it will make file explorer look like it did in previous versions of Windows. Check this option applies the classic theme in the windows of the file explorer, but has no effect on the taskbar and on the desktop. I therefore consider that this "solution" is not one.
|
|
|
Post by ihatemetro on Jun 28, 2022 6:34:20 GMT -8
I'm talking about how it will make it actually HAVE the classic theme instead of the default Windows 10 theme. I am not saying that it will make file explorer look like it did in previous versions of Windows. Check this option applies the classic theme in the windows of the file explorer, but has no effect on the taskbar and on the desktop. I therefore consider that this "solution" is not one. I never said that it will affect the taskbar or desktop. The original question was about the file explorer and not about the taskbar/desktop. Even then, if you use a third-party taskbar such as retrobar, this solution is invalid anyways, as you can just restart explorer and everything will be classic-themed without needing to worry about the taskbar being broken. Edit: Just realized that the original question is also about the taskbar and desktop as well, oops. But still, using something like retrobar and having a task scheduler script to restart explorer after classic theme gets enabled would mostly solve the issue.
|
|
|
Post by OrthodoxWin32 on Jun 28, 2022 6:43:32 GMT -8
Check this option applies the classic theme in the windows of the file explorer, but has no effect on the taskbar and on the desktop. I therefore consider that this "solution" is not one. I never said that it will affect the taskbar or desktop. The original question was about the file explorer and not about the taskbar/desktop. The problem is that this is implied, because the process that manages the file explorer also manages the desktop and the taskbar. In addition, Anixx's method is made to explore.exe starts with the classic theme. In this context, opening the windows of the explorer in a different process does not change anything, since the first process is already supposed to open on the classic theme. EDIT: I just saw your edition of yours message: Using a task bar as retribar partially solves the problem of the taskbar, but not everything, because RetroBar does not have all the features of the original task bar.
|
|
|
Post by ihatemetro on Jun 28, 2022 6:47:00 GMT -8
I never said that it will affect the taskbar or desktop. The original question was about the file explorer and not about the taskbar/desktop. The problem is that this is implied, because the process that manages the file explorer also manages the desktop and the taskbar. In addition, Anixx's method is made to explore.exe starts with the classic theme. In this context, opening the windows of the explorer in a different process does not change anything, since the first process is already supposed to open on the classic theme. I read the question again and realized that it was also talking about the taskbar and desktop (as they just said "explorer"). So it was just a misunderstanding on my part.
|
|
sbal
Freshman Member
Posts: 28
|
Post by sbal on Jun 28, 2022 6:55:34 GMT -8
I think yours is that the explorer starts before Classicthemetray. Normally, it should be the opposite. Have you configured the task (the one that contains the three commands) with the "Execute with maximum authorizations" option and the "Execute only if the user is connected" option ? It seems, he did not re-login after doing the steps, so the tasks never get started. I manually executed the task, but either ay, I logged out, logged back in, and now File Explorer looks "classic-ish". So progress! I am just doing small batches at a time and testing so I know the taskbar and start menu are not going to be different yet. I'll move onto the next batch of instructions and see if that works. While they look "classic ish" my window borders look nothing at all like they should.
|
|
|
Post by anixx on Jun 28, 2022 7:02:49 GMT -8
This will NOT affect the Explorer's look. Please don't tell what you do not know. The ribbon can be removed by Explorer Patcher, this is in the manual, p.13. One does not need OldNewExplorer. The deskn.cpl is linked in the manual at p.10. I'm talking about how it will make it actually HAVE the classic theme instead of the default Windows 10 theme. I am not saying that it will make file explorer look like it did in previous versions of Windows. Whether you check "run in separate processes" or not does not affect whether it runs in classic theme. How it even can???
|
|