Jevil7452
Regular Member
Posts: 432
OS: Windows Vista Enterprise (6.0.6003)/Windows 7 Enterprise (6.1.7601)
Theme: Windows Aero by Microsoft Corporation (on both)
CPU: Intel Core i7-3770k
RAM: 32GB (4x8GB DDR3)
GPU: NVIDIA GeForce GTX 980 Ti + Intel(R) HD Graphics 4000
Computer Make/Model: OEM0
|
Post by Jevil7452 on Mar 2, 2023 13:53:58 GMT -8
Hello, I've found a workaround for some apps using the dialog icons from user32, which are Windows 7 icons that can't be edited by anything, as any attempt to modify user32.dll will cause a system crash Doesn't look really great, does it Here's how it'll look with the fix: The solution involves adding a Common Controls (comctl) manifest to the application, an example manifest can be found here: files.catbox.moe/mbxy8t.resNote, if the app already has a manifest, then you'll need to combine the two, by adding the part that enables Common Controls to the existing manifest. Also, this might have some side effects with making the app less classic-styled. Changing the comctl version to 5.0.0.0 MIGHT solve this, but i haven't even confirmed that this happens at all. So, try with the 6.0.0.0 comctl version first Also, not all apps will get affected by this, even with the manifest added. This is also recommended to apply only on classic theme, as applying it when a msstyles-based theme is active will cause the rest of the app to be themed too, which will look inaccurate to how the app would've looked on the operating system. With classic theme, it doesn't matter if the app would get themed.
|
|
|
|
Post by The Jackal on Mar 3, 2023 9:39:36 GMT -8
How would one apply this?
|
|
Jevil7452
Regular Member
Posts: 432
OS: Windows Vista Enterprise (6.0.6003)/Windows 7 Enterprise (6.1.7601)
Theme: Windows Aero by Microsoft Corporation (on both)
CPU: Intel Core i7-3770k
RAM: 32GB (4x8GB DDR3)
GPU: NVIDIA GeForce GTX 980 Ti + Intel(R) HD Graphics 4000
Computer Make/Model: OEM0
|
Post by Jevil7452 on Mar 3, 2023 10:33:48 GMT -8
How would one apply this? You can apply it through Resource Hacker, or any other resource editor capable of importing .res files If a manifest already exists, you should instead check if there is a Microsoft.Windows.Common-Controls dependency. If there is, this already won't work, but if there isn't, you'll need to combine the dependency with the rest of the manifest The code to just enable ComCtl 6 is:
<dependency>
<dependentAssembly>
<assemblyIdentity
type="win32"
name="Microsoft.Windows.Common-Controls"
version="6.0.0.0"
processorArchitecture="*"
publicKeyToken="6595b64144ccf1df"
language="*"
/>
</dependentAssembly>
</dependency>
|
|
|
|
Post by The Jackal on Mar 3, 2023 12:00:02 GMT -8
Thank you, I appreciate it.
|
|
ecp
New Member
👅
Posts: 20
OS: Windows 10 21H2
Theme: Win9x
CPU: R5-7535HS
RAM: 16GB
|
Post by ecp on Mar 23, 2023 3:50:53 GMT -8
Hi i also found out if you remove common controls from manifest and PBS_SMOOTH style from progressbar styles it reverts to old segmented progress bars. It breaks some programs. So far i tested 7z, IDM and PerigeeCopy and didn't encounter any errors.
This is what i replaced manifest with
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" </assembly>
  EDIT: Fixed images in post.
|
|
|
|
Post by The Jackal on Mar 23, 2023 4:43:58 GMT -8
Hi i also found out if you remove common controls from manifest and PBS_SMOOTH style from progressbar styles it reverts to old segmented progress bars. It breaks some programs. So far i tested 7z, IDM and PerigeeCopy and didn't encounter any errors.
This is what i replaced manifest with
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" </assembly>
Oh wow, this is fantastic. If this could be turned into a Windhawk mod, you could get around the issue by disabling it for those problematic programs. Really nice find btw, and welcome to the forums. |
|
ecp
New Member
👅
Posts: 20
OS: Windows 10 21H2
Theme: Win9x
CPU: R5-7535HS
RAM: 16GB
|
Post by ecp on Mar 23, 2023 6:12:27 GMT -8
Thanks. I also tried to just change comctl verison from 6.0.0.0 to 5.0.0.0 but it returned errors about side-by-side configuration. Sadly i lack the skills to create a such mod.
|
|
AnyKey
Sophomore Member
Posts: 248
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 23, 2023 8:59:29 GMT -8
Hello, I've found a workaround for some apps using the dialog icons from user32, which are Windows 7 icons that can't be edited by anything, as any attempt to modify user32.dll will cause a system crash Doesn't look really great, does it Here's how it'll look with the fix: Note, if the app already has a manifest, then you'll need to combine the two, by adding the part that enables Common Controls to the existing manifest. Also, this might have some side effects with making the app less classic-styled. Changing the comctl version to 5.0.0.0 MIGHT solve this, but i haven't even confirmed that this happens at all. So, try with the 6.0.0.0 comctl version first Also, not all apps will get affected by this, even with the manifest added. This is also recommended to apply only on classic theme, as applying it when a msstyles-based theme is active will cause the rest of the app to be themed too, which will look inaccurate to how the app would've looked on the operating system. With classic theme, it doesn't matter if the app would get themed.
Can Windhawk do this?
And, I'm also looking a solution for these.
- The message and button font is 1pt smaller than it should be.
- Background is white.
- Buttons are right aligned.
So what I mean is how can W2K/XP style dialog be restored. Here's the both of dialogs for comparison.
Left:W2K Right:Windows 11
I'd be happy if there's a mod that solves these.
|
|
|
|
Post by The Jackal on Mar 23, 2023 11:43:02 GMT -8
Thanks. I also tried to just change comctl verison from 6.0.0.0 to 5.0.0.0 but it returned errors about side-by-side configuration. Sadly i lack the skills to create a such mod. No, it's cool, no mod is needed. I was too stupid to read the thread properly, I thought this needed to be applied to a system file, and not to each seperate program's executable. |
|
|
|
Post by TechSalt on Mar 23, 2023 12:09:28 GMT -8
Hello, I've found a workaround for some apps using the dialog icons from user32, which are Windows 7 icons that can't be edited by anything, as any attempt to modify user32.dll will cause a system crash Doesn't look really great, does it Here's how it'll look with the fix: Note, if the app already has a manifest, then you'll need to combine the two, by adding the part that enables Common Controls to the existing manifest. Also, this might have some side effects with making the app less classic-styled. Changing the comctl version to 5.0.0.0 MIGHT solve this, but i haven't even confirmed that this happens at all. So, try with the 6.0.0.0 comctl version first Also, not all apps will get affected by this, even with the manifest added. This is also recommended to apply only on classic theme, as applying it when a msstyles-based theme is active will cause the rest of the app to be themed too, which will look inaccurate to how the app would've looked on the operating system. With classic theme, it doesn't matter if the app would get themed.
Can Windhawk do this?
And, I'm also looking a solution for these.
- The message and button font is 1pt smaller than it should be.
- Background is white.
- Buttons are right aligned.
So what I mean is how can W2K/XP style dialog be restored. Here's the both of dialogs for comparison.
Left:W2K Right:Windows 11
I'd be happy if there's a mod that solves these.
Making the msgbox font 9pt in deskn.cpl should fix the font issue on msgboxes |
|
Alcatel
Freshman Member
Posts: 89
OS: Windows 10 Enterprise LTSC IoT 2021
Theme: Windows 7 Aero
CPU: i9-8950HK
RAM: 32GB DDR4
GPU: Nvidia Quadro P3200
|
Post by Alcatel on Mar 23, 2023 19:21:32 GMT -8
Can't you just throw them in the MUI
|
|
|
|
Post by The Jackal on Mar 24, 2023 10:52:25 GMT -8
Hi i also found out if you remove common controls from manifest and PBS_SMOOTH style from progressbar styles it reverts to old segmented progress bars. It breaks some programs. So far i tested 7z, IDM and PerigeeCopy and didn't encounter any errors.
This is what i replaced manifest with
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0" </assembly>
I was able to produce the same results in PerigeeCopy, but my version of IDM refuses to show the old progress bars. What version number are you using? |
|
ecp
New Member
👅
Posts: 20
OS: Windows 10 21H2
Theme: Win9x
CPU: R5-7535HS
RAM: 16GB
|
Post by ecp on Mar 24, 2023 11:20:23 GMT -8
v6.41 Build 7
|
|
