• Content count

  • Joined

  • Last visited

Community Reputation

32 Excellent

1 Follower

About UCyborg

  • Birthday

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

627 profile views
  1. PE Viewer, the one bundled with Process Hacker.
  2. Is it just me or do the executables have random future timestamps in the PE header?
  3. 18 March, 21:58
  4. Would be nice if people bothered to read the whole thread, it hasn't grown into a super long thread. There was a hint on the first page that the Creators Update compatible version is in the works, it'll just take a while. So it'll turn to 1704 when it releases.
  5. You could try and see if it works in safe mode. There is a trick to get Aero Glass working in safe mode, first, install it as the service just to get rid of dependency on Task Scheduler (see http://www.msfn.org/board/topic/170945-uxtheme-signature-bypass/?do=findComment&comment=1136296), maybe you could just enable Task Scheduler in safe mode instead (I haven't tried), but this way, you keep things to a minimum, then, you have to add both Aero Glass and Themes services to the list of safe-mode enabled services (see the attachment). AeroGlassSafeMode.zip
  6. Agreed. This feature for restoring modern app frames to have theme defined appearance has been considered experimental for quite a while and it seems it's not quite there yet. I think that detail about tablet mode is important to know for testing purposes, otherwise one could suggest just running Edge, since it's one of the apps that don't require Microsoft account, but guess what, it doesn't have full-screen toggle AFAIK. Don't forget you can just turn that particular Aero Glass feature off (http://www.msfn.org/board/topic/176569-aero-glass-for-win81-153/?do=reportComment&comment=1136963), so at least the functionality isn't effected in negative way. There is also a minor bug with caption centering feature, when application resizes its own window and TextGlowMode is set to 0 or 3, the caption isn't always centered right afterwards. The easiest way to reproduce the bug is with Command Prompt window. Right-click on its frame, go to Properties->Layout then change Width under Window Size to something smaller than default eg. 80 and confirm the new setting. Then return to Properties dialog and set it back to 120.
  7. You can create new DWORD EnableLogging in registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\DWM and set it to 1. Although I'm afraid it won't give any more useful info for this scenario, but worth a try I suppose.
  8. No. Here's a hint for everyone, this isn't app-specific issue. It can be reproduced in any modern app, simply activate Tablet mode. A note about SeDebugPrivilege, it seems it's enabled by default when running under SYSTEM account.
  9. Yes, 0x00000000 is okay, my point was, 0x00000003 no longer produces glow effect, have to set it explicitly to 0x000c0003. I played with DrawThemeTextEx a bit and from what I've observed, if you don't enable DTT_GLOWSIZE flag in struct member DTTOPTS.dwFlags, then the function will use TEXTGLOWSIZE value from .msstyles, otherwise, it takes DTTOPS.iGlowSize. Just so that we're on the same page, I tested with modified aero 2.msstyles from Aero 7 Clear theme. Your guide also says for TextGlowMode: 0x3=Composited glow effect using your theme settings. HIWORD of the value specifies glow size (0 = theme default). That's why I think something strange must have happened from 1.5.1 -> 1.5.2. I was also curious about the possibility of Aero Glass controling GLOWINTENSITY property, but it looks like DrawThemeTextEx doesn't offer any control over it, bummer. So subtracting a little from RECT.left is not a solution in this case?
  10. Aero Glass is not your ordinary type of software. Ordinary applications don't care about Windows internals, so things are simpler. I still didn't get symbols on my 32-bit installation this morning, but version 1.5.3 which knows everything it needs to work is released.
  11. Which can look pretty ugly, but the composited glow effect looks nice: It seems you have changed the behavior when registry setting TextGlowMode is set to 3. In 1.5.1 and earlier, the size WORD set to 0 meant use the value from .msstyles, in 1.5.2 and 1.5.3 zero means no glow. Old behavior seems to make more sense. For this setting to have any effect at all, GLOWINTENSITY property in .msstyles must be non-zero in .msstyles (http://i.imgur.com/McXdF28.png) so if the person doesn't use custom .msstyles, he doesn't have access to this kind of glow. Is intensity something Aero Glass could control if the user desires? As long as people understand there is no clean way to control these parameters for applications that draw captions on their own, as those questions have arised in the past and you don't really get an answer unless you dig into the whole theme hacking and related matters. If you use TextGlowMode set to 3 and leave caption text left-aligned, there remains the bug with text being shifted slightly to the right, the same problem you've fixed in 1.5.2 for glow effect from atlas image. It only shows when both size setting in UI and GLOWINTENSITY property from .msstyles are non-zero. A note about things to come, it seems changes in current Creators Update builds are extensive enough that will once again require modifications to Aero Glass internals when it releases. If I remember the build number correctly, there were symbols available for 15055, and it crashed with an error saying it couldn't find symbol CGeometry::GetShapeDataNoRef. It's great to see a new update! I noticed the bug with debug.log being created in the root drive is gone as well. I wonder about the practical effects of SeDebugPrivilege addition, supposedly being mandatory to inject code in critical system processes, one would assume it was there before.
  12. Regarding registry settings, it was never stated they're supposed to be there, you have to create them yourself or use GUI. And no need to create new topic, these things have been discussed before. You can't do much but wait and hope for a new bug-fixed version to come out. Aero Glass on Windows 8.1 is a better experience, though that fact doesn't help us much on Windows 10.
  13. I think we're lucky if we get fixes for existing issues. It's so close to perfect. This auto-update idea reminded me of another possibility, would it be possible for DWMGlass.dll to clean-up after itself on unload? That'd be neat. It crashes if you unload the DLL. I wonder why in recent Windows versions Unload option in Process Hacker works for dwm.exe while in regular processes it throws "Unable to find the module to unload."
  14. Would be a nightmare if it was one window per process and you had a lot of windows open.
  15. Because that's not the job of theme signature bypass tool. By original design, applications that draw controls on window frame, must then also draw window caption using DrawThemeText API. UxTSB.dll just hooks that function and if random application uses it for something else, you get unexpected results like these: The cleanest solution for the most consistent experience accross applications is modifying theme to enable text glow like it was on Windows 7, take note of TEXTGLOWSIZE and GLOWINTENSITY properties: Then set "Caption glow effect mode" in Aero Glass GUI to "Use theme settings". At least that is supposed to get you default Windows 7 behavior, the problem is the long-present bug in Aero Glass with text not being rendered at correct position. For now, I use the option that takes glow from atlas image, so I have one type of glow for regular windows and the other for ribboned windows. Though it's not connected to ribbons, it's the customized frame. The other type you get is composited glow controlled by those two properties I mentioned. Aero Glass only overrides TEXTGLOWSIZE, so no glow if GLOWINTENSITY is 0. I think the glow from atlas image is exclusive to captions of regular windows. And so is custom colored caption text without UxTSB.dll in every process (AppInit_DLLs method). Not in Creators Update.