bigmuscle

check debug.log, it should provide error code when reflection is not properly loaded P.S. I just found a bug that custom reflection won't load under some conditions and it will always use the default image

Actually, any update which breaks something on which the hooking depends will result in hook failure and black screen on startup. My solution just hooked LoadLibraryExW function in every process and redirected to my DLL anytime it wanted to load some of the theme service's library. Because LoadLibraryExW is called very often, it degraded performance of every process a lot.

No, it can't. WIC hook is actually one line only to ensure that alpha channel on windows captions will be used. It has no other task thus hook failure just makes the captions non-transparent (that's why black rectangle will be seen). Thanks, I will check it.

It will be here soon.

I already said it many times how it works and it works the same way since WinVista. Application, which wants some of its control to get blur behind, simply calls DwmEnableBlurBehindWindow(hwnd, TRUE) for this control. DWM then just renders glass effect on such marked region (and if transparency is enabled, it will render blur effect behind). So in Win7, Explorer.exe just calls DwmEnableBlurBehindWindow(hwndTaskbar, TRUE). But in Win8.x, explorer.exe calls DwmEnableBlurBehindWindow(hwndTaskbar, FALSE). Nope, the goal of this project is to implement extension for Desktop Windows Manager to get blur effect on glass regions.

please provide debug.log and version number of your dwmcore.dll and udwm.dll.

Nope, it is not. Blur behind taskbar has nothing to do with DWM. It's Explorer's task to enable it.

I can't, because a) Aero Glass is DWM hook only and B) there is no correct way how to inject DLL into all processes in the system. I don't undestand - in rc1 and early builds you make it and all works fine. Why you can't do this in release for thom who use registry injecting? Because it requires old unsecure injecting into every process which only messes your system and is against the logic of my Aero Glass extension. And as I said many times - my Aero Glass is only extension to Desktop Window Manager and not multi-functional software which is even able to make a coffee.

If you are not advanced user (which understands registry editing) and you have no problems with Aero Glass then you don't need any tweaker because there is no settings which you should change.

I can't, because a) Aero Glass is DWM hook only and b) there is no correct way how to inject DLL into all processes in the system. You installed glass theme although you use your own theme. It's incompatible (I should add a notice into the installer). To change glass custom theme, read the guide on the website. I don't understand you much. Your screenshot shows that Aero Glass works as expected, so where's the problem? In the same way how to add blur into any other window. You must use some tool which calls DwmEnableBlurBehindWindow for that window.

There is no dwm.exe window in final release. It can only show up when symbols are needed to be downloaded to display downloading progress but it can be closed after finishing and does not appear anymore.

dwm.exe process is responsible for desktop composition and it always must be active. The only difference will be that running on battery should disable transparency. If it does not work and windows frames are still transparent on battery, it can be because your battery does not correctly report its status (it means system receives "AC power" or "unknown status" instead of "on battery").

Each settings (except of those intended for HKLM only) is read from HKCU at first. If the value is not found, it falls back to HKLM. This allows specifying each value on per-user and global basis separately. E.g. setting some value in HKCU and HKLM to same value brings no result and only creates redundant data.

This is what I have noticed after I did some testing. When I get "Black box" I see the following (extra lines) in the debug.log DBGHELP: .\uDWM.pdb - file not foundDBGHELP: .\dll\uDWM.pdb - file not foundDBGHELP: .\symbols\dll\uDWM.pdb - file not foundDBGHELP: udwm - public symbols C:\AeroGlass\symbols\uDWM.pdb\4588A14F9B8E4824B21524CD279E1EFF2\uDWM.pdbSymbols loaded for udwm.dll as 3 (#0)And when I get the normal "Aero glass" I don't see the above stuff. Everything else in the log between the two is same.Then send me your uDWM.dll via PM please. You either have some old version of UDWM or there is some new update. Symbols should normally be needed at this time. Hello, I have installed AG81 (by setup.exe) as registered user in W81x64 and graphically everything works fine, but I need to fix two minor issues with the app: 1) The SearchIndexer.exe proces crashes after every reboot once, but then it auto-restarts and works OK until next reboot. When AG81 is unistalled, then it no longer crashes. PopisCesta k chybující aplikaci: C:\Windows\System32\SearchIndexer.exePodpis problémuNázev události problému: APPCRASHNázev aplikace: SearchIndexer.exeVerze aplikace: 7.0.9600.16384Časové razítko aplikace: 5215d4c4Název chybného modulu: MSSRCH.DLLVerze chybného modulu: 7.0.9600.16384Časové razítko chybného modulu: 5215d425Kód výjimky: c0000005Posun výjimky: 0000000000006dbeVerze operačního systému: 6.3.9600.2.0.0.256.4ID národního prostředí: 1029Další informace 1: 6d41Další informace 2: 6d41e4396d81642d19366c6551ed1668Další informace 3: e03aDalší informace 4: e03a041bd62db5852c187261b2519512Další informace o tomto problémuID sady: e25ae552d453d49eddf5ca482dea705d (125837385)I doubt that it can cause crash in totally unrelated application. I just guess that Aero Glass causes that SearchIndexer loads into some corrupted memory part. I do not understand this much. Playing with ColorizationColorBalance and ColorizationColorBalanceInactive does not do what you need?

AppInit_DLLs method works, I tested and there is no reason why it should not, because the "blocking" check which causes the problems on some localized systems happens in aerohost.exe which is not used in other injection methods.

Then it must be worse than I thought. The report error just means that COM library has not been initialized by CoInitialize function. This would be obvious mistake except that CoInitialize is called and other COM calls works correctly. I must find a way to reproduce it so I can step into WIC code to see where the error is created.

Please, stop spamming and read the forum. I already answered this many times.

illuzi0n: could you (and others with same problem) try at least temporary solution by editing "Aero Glass" task in Task Scheduler and setting some startup delay? E.g. 10 seconds (page Triggers > Edit > check Delay task for) Soilbreaker: please enable verbose logging (see website guide how to that) and then provide full debug.log. Your symbols seems not to be loaded for some reason.

I would just append that if he uses different way of injection (e.g. old AppInit_DLLs) then he must disable this injection first before dwm.exe restart. And no, you don't have to restart PC. You can just start the task in Task scheduler.

Thanks, I finally found the problem. Your aerohost.exe is not running under SYSTEM account, but under its localized version СИСТЕМА which is the problem. Does certain localization really translate even default system names? I guess that everyone who has the same problem just use Russian localization. Well, I tried this. But dwm.pdb has not changed since 26/08/2013 and other people have said that black box happened in RC3 too (I didn't notice it in RC3 but I was not testing Aero Glass, just using PC normally). Why would dwm.pdb cause the black box problem? Don't afraid, it has nothing to do with the symbols. Symbols can just slow down DLL injection which will result in working behaviour in case it is really caused by race condition (sometimes DLL injection is faster than system initializes WIC library).

and still does not work? Could you generate minidump for aerohost.exe with this debug build, it should provide more verbose output than release.

Only one idea comes to my mind - on some systems, installing DWM hook is so fast that it happens before the WIC component is initialized. It would explain why it works with debug build (which is a bit slower than release). Now I need to find a fix.

Thanks. Log shows: CoCreateInstance(CLSID_WICImagingFactory, NULL, CLSCTX_INPROC_SERVER, IID_PPV_ARGS(&pImageFactory)) failed with 0x800401F0now I am interested what causes the error

It seems that it failed to hook WICImageFactory (it works here, but if I remove this hook it behaves the same way). When my s***ty internet connection starts working, I will upload debug build if shows if it is this problem. So please, download this build: http://glass8.berlios.de/stuff/DWMGlassDebugBuild.7z and provide debug log after the error appears. This build is intended to generate error log when glow hook fails and also to generate more startup logs (so if anyone has problem that glass is not working but aerohost.exe is running, use it too and provide debug.log). Just replace DWMGlass.dll and restart aerohost.exe and dwm.exe.

And what happens when glow mode is set to zero (to completely disable it)?