Windows 10 DEVELOPMENT

[Hadden]

Yes, this is ok. UxThemeSignatureBypass.dll is not fully compatible with current version of aeroglass/modernframe yet.

 

EDIT: It means, it ignores atlas layout file.

 

Ok. Thank you for the patience and thanks for your work =)

[dhjohns]

 

Hello, I just installed 32-bit+64-bit (Updated on 14th August 2015) on an installation clean (build 10240 64-bit) and this is what I get:

 

 

I would like to know If this is normal At this stage of development or if I forget something ?

 

I must admit that I don't understand this. Why non-advanced users bother with non-finished development version if they are not even able to read instructions, guide, notes etc. before downloading? What is the sense in using installer on Win10 if it is marked as "IMPORTANT: Do NOT use on Windows 10 RTM 10.0.10240." ???? And it is not only this... why some users are injecting DWMGlass.dll via old AppInit_DLLs on Win10 when nobody says it to do it so? Why? .... I'm asking because every while I get some bug reports where the only cause it that user was not able to install it correctly.

 

So again for everyone:

 

!!! IF YOU ARE NOT ADVANCED USERS AND YOU ARE NOT ABLE TO INSTALL THE DEBUG VERSION PROPERLY THEN DO NOT USE IT !!!

 

Here is what I use to inject AeroGlass.  

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]@="mnmsrvc""AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass64.dll C:\\AeroGlass\\DWMGlass.dll C:\\AeroGlass\\ModernFrame.dll""LoadAppInit_DLLs"=dword:00000001"RequireSignedAppInit_DLLs"=dword:00000000

I have no trouble with Modern Apps or regular windows.  EDIT:  I do install OldNewExplorer, and a Black Theme from MrGRiM, and that resolves the issue for the ModernFrame not picking up the png.layout.  Otherwise, there is an issue in the title bar.

Edited August 15, 2015 by dhjohns

[dhjohns]

I looked in the Details tab in Task Manager, and I noticed that when I install AeroGlass the "normal" way that both aerohost.exe, and dwm.exe are running, but if dwm.exe is injected in AppInit_DLLs then just dwm.exe is running.

 

My question BigMuscle is "what is the difference?"  What does aerohost.exe do, and why does everything seemingly behave the same when it is not running?

[My1]

I think the difference is the injection, in case of AppInit all processes get the dll and in case of aerohost.exe, it somehow manages to inject just into DWM, also iirc aerohost works fine even with secureboot, not sure about that, by the way.

[Hadden]

I looked in the Details tab in Task Manager, and I noticed that when I install AeroGlass the "normal" way that both aerohost.exe, and dwm.exe are running, but if dwm.exe is injected in AppInit_DLLs then just dwm.exe is running.

 

My question BigMuscle is "what is the difference?"  What does aerohost.exe do, and why does everything seemingly behave the same when it is not running?

 

Thanks for tips!

I'm using the same inject config.. Could you link MrGrim atlas? I'll try it.. I'll also try to "skip" .layout scheme

I'll look at the oldnewexplorer too (it'll disable ribbon, it is?). I used it a long time ago - on win 8, but then I rollback to 7. (But honestly I never liked the command bar)

At the time I also used a .dll hack (with resource hacker) to hide/disable (not recommended) the command bar WITH classic shell enabled, resembling the explorer look of xp (but with more customizations).

The titlebar issue in explorer I posted above, seems be caused by ribbon: while I was testing, the network connections page - that doesn't use ribbon but command bar - was correctly rendered with no "glitches".

Edited August 15, 2015 by Hadden

[TheClock]

I found a minor bug. Some minor artifacts are created when a Universal app is on top on one another. Since the screen refreshes once I make a screenshot, I couldn't get any images. However, it can be replicated pretty easily.

[dhjohns]

 

I looked in the Details tab in Task Manager, and I noticed that when I install AeroGlass the "normal" way that both aerohost.exe, and dwm.exe are running, but if dwm.exe is injected in AppInit_DLLs then just dwm.exe is running.

 

My question BigMuscle is "what is the difference?"  What does aerohost.exe do, and why does everything seemingly behave the same when it is not running?

 

Thanks for tips!

I'm using the same inject config.. Could you link MrGrim atlas? I'll try it.. I'll also try to "skip" .layout scheme

I'll look at the oldnewexplorer too (it'll disable ribbon, it is?). I used it a long time ago - on win 8, but then I rollback to 7. (But honestly I never liked the command bar)

At the time I also used a .dll hack (with resource hacker) to hide/disable (not recommended) the command bar WITH classic shell enabled, resembling the explorer look of xp (but with more customizations).

The titlebar issue in explorer I posted above, seems be caused by ribbon: while I was testing, the network connections page - that doesn't use ribbon but command bar - was correctly rendered with no "glitches".

 

Here is the link to MrGRiM  http://virtualcustoms.net/showthread.php/69707-Windows-10-Black-Edition  I am sure you will need to register to get the downloads.  Also, if you choose NOT to use png.layout everything will be helter skelter!  LOL

[dhjohns]

I think the difference is the injection, in case of AppInit all processes get the dll and in case of aerohost.exe, it somehow manages to inject just into DWM, also iirc aerohost works fine even with secureboot, not sure about that, by the way.

I would not know about secure boot, since I am on a MB with just BIOS.

[Chris123NT]

Had a dwm crash earlier, here's the event log data from it:

 

Faulting application name: dwm.exe, version: 10.0.10240.16384, time stamp: 0x559f3907

Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3

Exception code: 0xe0464645

Fault offset: 0x000000000002a1c8

Faulting process id: 0x764

Faulting application start time: 0x01d0d7011377511a

Faulting application path: C:\Windows\system32\dwm.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 682b25f6-1fcb-440d-87e7-4771f05948cb

Faulting package full name: 

Faulting package-relative application ID: 

[mikedigitize]

A way to restore

 

Here‘s another tutorial, looks more detailed: http://winaero.com/blog/get-colored-firefox-title-bar-in-windows-10/

Thanks for the link

Back to normal again!

[shelter]

 

Had a dwm crash earlier, here's the event log data from it:

 

Faulting application name: dwm.exe, version: 10.0.10240.16384, time stamp: 0x559f3907

Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f38c3

Exception code: 0xe0464645

Fault offset: 0x000000000002a1c8

Faulting process id: 0x764

Faulting application start time: 0x01d0d7011377511a

Faulting application path: C:\Windows\system32\dwm.exe

Faulting module path: C:\Windows\system32\KERNELBASE.dll

Report Id: 682b25f6-1fcb-440d-87e7-4771f05948cb

Faulting package full name: 

Faulting package-relative application ID: 

 

 

Try posting debug.log info too.

[arifkarim]

 

Here is what I use to inject AeroGlass.  

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]@="mnmsrvc""AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass64.dll C:\\AeroGlass\\DWMGlass.dll C:\\AeroGlass\\ModernFrame.dll""LoadAppInit_DLLs"=dword:00000001"RequireSignedAppInit_DLLs"=dword:00000000

I keep getting this error while using above registry merge:

[MDJ]

 

 

Here is what I use to inject AeroGlass.  

 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]@="mnmsrvc""AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass64.dll C:\\AeroGlass\\DWMGlass.dll C:\\AeroGlass\\ModernFrame.dll""LoadAppInit_DLLs"=dword:00000001"RequireSignedAppInit_DLLs"=dword:00000000

I keep getting this error while using above registry merge:

 

Add this line before creating a REG file:

Windows Registry Editor Version 5.00

Also, at least for me "RequireSignedAppInit_DLLs" entry isn‘t needed at all.

[daveo76]

 

Here is what I use to inject AeroGlass. 

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows]@="mnmsrvc""AppInit_DLLs"="C:\\AeroGlass\\UxThemeSignatureBypass64.dll C:\\AeroGlass\\DWMGlass.dll C:\\AeroGlass\\ModernFrame.dll""LoadAppInit_DLLs"=dword:00000001"RequireSignedAppInit_DLLs"=dword:0000000

You don't need to inject C:\\AeroGlass\\DWMGlass.dll

[bigmuscle]

AppInit_DLLs registry value:

* security risk (aerohost verifies if DLL is correct)

* secure boot must be turned off

* loads DLL into any process -> DLL can negatively influence behaviour of any application on your system

* loads DLL very early in main thread -> race condition can cause any application to deadlock (e.g. black screen on startup etc.)

* does not have access to user session -> per-user settings won't be loaded