UCyborg

Member
  • Content count

    85
  • Joined

  • Last visited

Community Reputation

24 Excellent

1 Follower

About UCyborg

  • Birthday

Profile Information

  • OS
    Windows 10 x64
  • Country

Recent Profile Visitors

426 profile views
  1. This version still has the bug with debug.log being created in root of C drive, seems to happen when aerohost.exe starts, easy to reproduce by stopping and restarting it via Task Scheduler. Can also be triggered by registering/unregistering DWMGlass.dll, regardless of whether aerohost.exe runs or not.
  2. Is there any difference between older UxTSB64.dll and newer UxTSB.dll besides compilation date? If not, then I suppose I'm not missing out on anything by using older UxTSB32.dll renamed to UxTSB.dll to utilize new injection method on my 32-bit system. It does seem to work, can't reproduce that DLL injection failure bug on that machine neither.
  3. And we're still missing x86 version of UxTSB.dll.
  4. I noticed the similar problem as CKyHC once, it occurred around Christmas time, I would get the usual spinning circle indicating logging in, then, instead of desktop showing up, I'm thrown back to the login screen, having to enter the password. I usually don't have to since I have auto-login enabled for my account. There is the same VirtualAllocEx error logged at said time frame. Cold vs fast startup doesn't change anything either, would probably have to keep rebooting PC (for cold startup to be effective) or turning it off and on again (for fast startup to be effective) all day before the bug would occur again, if at all.
  5. Then I'm afraid I can't help you with this one as I'm unable to reproduce it on my end.
  6. I cannot confirm DWMGlass.dll has any effect on those options whatsoever. Registered or not, if starting point in Explorer is This PC before navigating anywhere else, they will remain disabled until navigating to an actual folder/drive on PC. You can't cd to This PC from command line I think. And it's logical since they're meant to open the command line in directory you're currently in. And if it can't use that, it uses last valid location from navigation history (back/forward buttons).
  7. This is fixed in latest experimental version: http://www.glass8.eu/beta If you don't want to use experimental versions, you must wait for the new stable version.
  8. Sounds like you're trying to use the atlas that's not compatible with Win10 Anniversary Update.
  9. Oh right, you need another DLL for that: http://glass8.eu/out/ModernFrame-2016-10-22.7z Drop it in AeroGlass folder, then add C:\AeroGlass\ModernFrame-x64-Release.dll to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs. Paths to multiple DLLs must be separated with space or comma. Then reboot.
  10. Here's a screenshot of interesting experiment, I ran Paint with CustomNCRender option from Compatibility Administrator, part of Windows 10 ADK. Regular applications will just get the frame you got on Windows 7 with disabled DWM, aka. Windows 7 Basic, not Aero. I could grab it by the invisible frame, resize it, but couldn't close it by clicking where close button would normally be. Process Hacker's window commands weren't effective neither. Anyway, I think this clearly demonstrates what is under DWM control and what isn't. CustomNCRender option supposedly leaves entire non-client area of the window under application control, though regular applications still get backup basic frame without fancy effects. I forgot to mention that CustomNCRender is available only for 32-bit applications. And strangely, it doesn't do anything for the Wordpad.
  11. Yes, the only reason Explorer is handled differently is because UxTSB.dll is injected in Explorer and it hooks DrawThemeText/DrawThemeTextEx function to change the text appearance, which I suppose is called by the underlying ribbon framework. But even there, eg. if you click any hard drive in my PC, Drive Tools appear in the title bar and I don't think that's supposed to have its drawing parameters changed. But given the purpose of those APIs, you can't tell from the parameters they take what exactly is it being used for, so I think it would appear properly only if you intercepted at the exact place where call is being made, not when when you're already in the function. But that's probably cumbersome to implement and isn't solving the problem that the text is still under user application control making the call, in this case indirectly via ribbon framework. I'm not really knowledgeable about how these thing actually work under the hood, so I can only point at stupidities from the user perspective. There is also this oddity in Firefox for example, unless you set it to use regular titlebar without extras like tabs and buttons on it etc., hovering the mouse over close, min. and max buttons will overlay ugly blue rectangles over them, instead of simply taking light-up versions of those buttons from the theme. Even if you use stock Win10 theme, hover-over version of buttons is inconsistent with the rest of the system, at least if you have good eyes to notice. GlassMyFox is apparently only able to restore non hover-over versions of the buttons. But with ribbon windows, title text has to be special, even though other elements on the frame are fine.
  12. About #1, active text can also be black, depends on colorization gathered from desktop background. What's funny about this whole thing, when no tweaks are applied, both normal and ribbon title text appear the same. Only when you start tweaking, it becomes apparent ribbon text is actually managed separately, I assume by the Ribbon framework. https://officeribbon.codeplex.com/releases/view/113126 Judging by this demo, whenever window has extra buttons on the title bar, it will have its own title text colorization.
  13. You must make sure LoadAppInit_DLLs is set to 1, I was just trying to say that this isn't mentioned in the linked post with instructions. So to recap: Drop the UxTSB32.dll and UxTSB64.dll in C:\AeroGlass Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows Set AppInit_DLLs to C:\AeroGlass\UxTSB64.dll Make sure LoadAppInit_DLLs is set to 1. Make sure RequireSignedAppInit_DLLs IS NOT PRESENT and if it is, either delete it or set it to 0. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion\Windows Set AppInit_DLLs to C:\AeroGlass\UxTSB32.dll Make sure LoadAppInit_DLLs is set to 1. Make sure RequireSignedAppInit_DLLs IS NOT PRESENT and if it is, either delete it or set it to 0. Reboot the computer.
  14. We had discussion about the mysterious Microsoft.Windows.Explorer console and what triggers it a page or two back. The ApplicationFrameHost one, that's logical since ApplicationFrameHost.exe hosts modern app frames. Starting Calculator makes both pop up here. Another scenario that triggers it is changing the screen resolution.
  15. Just for informational purposes, starting modern Calculator will open the Microsoft.Windows.Explorer console.