crabsynth
Freshman Member
Posts: 57
OS: Windows 11
Theme: Windows Vista
CPU: I5 9600k
RAM: 32gb
GPU: RTX 4060
|
Post by crabsynth on Mar 1, 2024 11:50:16 GMT -8
Hi! So I just want to know if there is a way to bring this back to Windows 10/11? The default explorer looks fine enough on its own but I just want to bring back that small feature if I can  if anyone knows any way to do it I would really appreciate the help Attachments:
|
|
Jevil7452
Sophomore Member
Win10toVista = Vista's "poor performance and stability" without feeling you're actually using Vista
Posts: 195
OS: Windows 10 1703 (15063)
Theme: WinTango Patcher (Shiki-Colors Noble)
CPU: 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz
RAM: 32GB
GPU: Intel Iris Xe Graphics G7 80EU
|
Post by Jevil7452 on Mar 1, 2024 13:15:37 GMT -8
Yes. Now there are 3 choices. 1. Use OldNewExplorer and apply the theme with it activated, it will cause UIFiles to get redirected to the ones in ShellStyle, and you will get it automatically 2. Extract Shell32 UIFILE 52, from Windows Vista version of the theme: shellstyle.dll, and insert it in shell32.dll.mun (for 1903 and up only) 3. Extract Shell32 UIFILE 52, from Windows Vista version of the theme: shellstyle.dll, and insert it in shell32.dll in System32 and Syswow64 both (for 1809 and below only). In this method you will need to unsign shell32 and enable no_integrity_checks
|
|
ephemeralViolette
Sophomore Member
Posts: 183 
OS: Windows 10 (20H2), Windows 10 (22H2)
Theme: Windows XP Luna, Windows 7 Aero
CPU: AMD Ryzen 9 5900X
RAM: 64 GB
GPU: Radeon RX 580
|
Post by ephemeralViolette on Mar 1, 2024 13:24:54 GMT -8
Yes. Now there are 3 choices. 1. Use OldNewExplorer and apply the theme with it activated, it will cause UIFiles to get redirected to the ones in ShellStyle, and you will get it automatically 2. Extract Shell32 UIFILE 52, from Windows Vista version of the theme: shellstyle.dll, and insert it in shell32.dll.mun (for 1903 and up only) 3. Extract Shell32 UIFILE 52, from Windows Vista version of the theme: shellstyle.dll, and insert it in shell32.dll in System32 and Syswow64 both (for 1809 and below only). In this method you will need to unsign shell32 and enable no_integrity_checks
It is also possible to use something like Windhawk in order to redirect resource APIs, in case you're stuck on 1809 and below and don't want to boot with integrity checks disabled every time. |
|
AnyKey
Sophomore Member
Posts: 229
OS: Windows 10 Pro 22H2
Theme: XP Classic Theme
CPU: AMD Ryzen 7 3700X
RAM: 16 GB 1333 MHz DDR4
GPU: Nvidia Geforce RTX 2070 Super
|
Post by AnyKey on Mar 5, 2024 8:09:57 GMT -8
It is also possible to use something like Windhawk in order to redirect resource APIs, in case you're stuck on 1809 and below and don't want to boot with integrity checks disabled every time. Is it also helpful for user32.dll icons? |
|
ephemeralViolette
Sophomore Member
Posts: 183
OS: Windows 10 (20H2), Windows 10 (22H2)
Theme: Windows XP Luna, Windows 7 Aero
CPU: AMD Ryzen 9 5900X
RAM: 64 GB
GPU: Radeon RX 580
|
Post by ephemeralViolette on Mar 5, 2024 12:48:20 GMT -8
It is also possible to use something like Windhawk in order to redirect resource APIs, in case you're stuck on 1809 and below and don't want to boot with integrity checks disabled every time. Is it also helpful for user32.dll icons? Yes, but only in certain circumstances. For example, if a message box is created by CSRSS, then it's impossible for Windhawk to modify it at all. |
|
crabsynth
Freshman Member
Posts: 57
OS: Windows 11
Theme: Windows Vista
CPU: I5 9600k
RAM: 32gb
GPU: RTX 4060
|
Post by crabsynth on Mar 9, 2024 17:09:16 GMT -8
Yes. Now there are 3 choices. 1. Use OldNewExplorer and apply the theme with it activated, it will cause UIFiles to get redirected to the ones in ShellStyle, and you will get it automatically 2. Extract Shell32 UIFILE 52, from Windows Vista version of the theme: shellstyle.dll, and insert it in shell32.dll.mun (for 1903 and up only) 3. Extract Shell32 UIFILE 52, from Windows Vista version of the theme: shellstyle.dll, and insert it in shell32.dll in System32 and Syswow64 both (for 1809 and below only). In this method you will need to unsign shell32 and enable no_integrity_checks
Thanks for the help  should I move the UIFILE 52 into the 52 part of shell32.dll.mun?
Edit: Just tried. it thank you so much!!
Attachments:
|
|
if anyone knows any way to do it I would really appreciate the help
should I move the UIFILE 52 into the 52 part of shell32.dll.mun? 