CKyHC

That's why I prefer UxTSB by BigMuscle insteed of file patching. Even if after Windows update AeroGlass became incompatible with new updated Windows build, DWMGlass.dll injects UxTSB.dll in this case, and visual style loads...

Wich way and what exactly you modify in themes? We means there that visual style file .msstyle not signed by MS didn't loads without way to bypass signature checking... If you modify colors, mouse pointers, sounds, screensaver, but didn't modify .msstyle file - theme modified that way will work without problems...

You can try to increase dedicated to GPU memory via BIOS to 256Mb. But on my Intel HD 2000 Sandy Bridge on my work comp 128Mb didn't cause a problem...

Problem was solved by replacing theme files and UxTSB.dll via file manager program. Before it theme files and UxTSB.dll was copied in their locations via windows explorer. I think that problem was in that. I just deleted theme and UxTSB.dll. Opened Far Manager and copy theme and dll again and all start to work. Thanks to all who tried to help!

What GPU and how much videomemory? Maybe lack of videomemory?

Thanks for advices! Comp is at home now. After work I will try to use via AppInit_Dll, will try other theme. Can you give me anyone of them to try, please? Via this old personalization panel I'm always appliing the 3rd party themes. I know that through modern personalization themes didn't applies, because UxTSB.dll didn't injects into it, only in explorer.exe. Another one thought: Intel® TXE: Intel® Trusted Execution Engine I use one of the latest Core i3-6100 CPU with Intel HD 530 integrated GPU with full latest set of drivers on Asus H110 MB. May this TXE technology brokes theme signing bypassing? Anyone use Windows 10 x64 on Core i3-6xxx CPU? Can theme be applied on safe mode somehow?

This means that problem is in my system... But what can be wrong? I run AG through service, UxTSB.dll injects.... But visual style didn't loads... Maybe some settings or polices editing need to be done? I long time didn't tune up system on new install... Is there is some setting needed for AG and UxTSB.dll?

Checked style on 32-bit Windows 10 17134.191. Even on older 1.5.2 x86 version of AG (it didn't give aero effect on latest build of W10, I use it for 3rd party themes and atlases) my style loads normal... And as @UCyborg checked, problem is not in style... What else can be a cause of my problem? AeroGlass works normal, theme atlases works, no errors in debug.log. UxTSB.dll injects normal, on explorer ribboned windows titles text with glow - this is possible using atlas+UxTSB.dll injected... Without UxTSB text glow only on usual window titles, not ribboned... When I try to load visual style via old personalization panel, screen became black and it's sound that device is disconnected - after reboot video driver wrote that it was restored after fail... If style load through ediding registry (ThemeManager) - Windows not logons - winlogon.exe drops when try to load style... I didn't know where I can dig else... System is almost new. Not much programs installed... No AV installed, using Windows Defender... Maybe I frogot something to tune? What else need to do to 3rd party themes work?

I didn't care about security. But loading dll through AppInit_DLLs leads to loading it into all the processes. But loading visual style didn't need that, it's needto inject only in winlogon.exe and explorer.exe, what AeroGlass doeng... But I don't think that the problem is in way to inject UxTSB.dll... It injects without problems into all nececcary process, Problem accures on applying style, not on injecting... So I think that loading through AppInit gives me nothing... Can it be somehow connected with display driver? It's integrated Intel HD 530... Maybe problem is in style itself? Can someone check loading style on 17134.191? Thats the file of style I trying to load: http://rusfriends.clan.su/Other/Aero_Glow_Square_10.rar

You want to say that on 17134.191 build you can use 3rd party theme working on previous versions? For me on 17134.165 all works fine, on 17134.191 themes didn't work.

But it can't help with secure boot enabled... And... You use different visual style? Not atlas? What theme you're use?

But many time up to 17134.165 UxTSB works fine... Only on 17134.191 stop to work... Maybe MS changed something in signing visual styles?

UxTSB stops to work on build 17134.191 3rd party visual styles didn't work. On applying screen is goes black and my integrated Intel HD 530 driver stops to work! In log all right, UxTSB injects into all processes normal without errors. I tried to add visual style to registry manually and reboot, but it leads to neverending logon with black screen. On 17134.165 all works fine, 3rd party visual styles works. Looks like it's need to update UxTSB.dll

UxTSB stops to work on build 17134.191 3rd party visual styles didn't work. On applying screen is goes black and my integrated Intel HD 530 driver stops to work! In log all right, UxTSB injects into all processes normal without errors. I tried to add visual style to registry manually and reboot, but it leads to neverending logon with black screen. On 17134.165 all works fine, 3rd party visual styles works. Looks like it's need to update UxTSB.dll

BigMuscle please compile 32-bit version!