dhjohns

Huh, it sounds like there's a wide variety of results with Aero Glass following the 10586 installation. It worked for you, it didn't work for me, and @truexfan81 reports above that his computer was borked. Wonder what might account for the differences. --JorgeA Maybe, because there is no Aero Glass designed for build 10586? I really do not understand why the people still mess this forum with build 10586 when it has been million times said that this is for build 10240 only Because we can!

Huh, it sounds like there's a wide variety of results with Aero Glass following the 10586 installation. It worked for you, it didn't work for me, and @truexfan81 reports above that his computer was borked. Wonder what might account for the differences. --JorgeA I don't know how anyone else installed it, but I had the version 1.4.1 installed, and as BM kept releasing the experimental builds, I just kept replacing the files, one by one. So, basically I suppose, I am running a conglomeration of testing versions. It works great, and there are no watermarks, ever. Just a debug window.

It works fabulously! Did it "just work" for you when you installed 10586, or did you have to re-do any Aero Glass settings? In my case, I'm going to have to reconstruct the settings and choices I'd made. Shoulda taken notes when I did it the first time, as talk about "theme atlases" and so forth doesn't exactly roll off my tongue. --JorgeA It worked straight away. No issues.

It works fabulously!

You press cancel.

It works fine, but msstyles is different, so you need to wait for themes to be updated.But even on windows 10, windows 8, 8,1 msstyles are working, Is the TH2 that different?Why do you even ask that? The answer is yes.

It works fine, but msstyles is different, so you need to wait for themes to be updated.

Where did I hide it?

Sorry Google translator I couldn't help but notice you had a watermark with a donation key. I don't have it with mine. Very strange. Show as a screenshot of you running Windows 10 Build 10586 with areoglass experimental build with no watermark. As bigmuscle always make his watermark permanently show on experimental builds regradless if you have a license key or notPlease do not question me in the future. It is not productive. But, here is the screenshot.

Sorry Google translator I couldn't help but notice you had a watermark with a donation key. I don't have it with mine. Very strange.

Ah yes, but it is working great in build 10586 none-the-less!

Yup, it works great!

I don't have that with experimental build 447.

Danm (sic) shame. The colored buttons are the best part of the theme, and the only reason I am using it.

No, that would not be the problem. Are you sure you replaced it? What build are you using? To replace mine I just booted to another OS I have installed, and copied it over.

Of course I HAD to try it in build 10576, and it works wonderfully! Thanks bigmuscle! No flickering, No watermark (with license,) and I just move the debug window to desktop 2!

You can always open task manager, go to details, then end aerohost.exe. Then you can end dwm.exe. It will restart, and aeroglass won't be running. Perhaps you can create a batch file to do this automatically. I would think this is possible. To restart it go to task scheduler, and highlight aeroglass task, and click run.

Everything is on that page. There are even suggested donations. Yes, the watermark is removed with your license. Once you donate, and get a password you can logon to your support profile and submit your machine code for a key.

You can get rid of the borders, and shadows, plus have some really cool glow effects by changing layout file to this!

Probably just because they can! lol

Log on to your Support Profile

This is exactly what I was looking for! Thank you so much. I can now export my registry settings, incorporate it into my main regedit file. Put the command to register dlls in my batch file, and one more manual customization is now automated. Thank you!

To help prevent irreversible damage, this program is designed to be non-invasive. This program is solely reliant upon itself in terms of functionality hence why you can't rename, move nor delete the file while in use.. A similar effect can be done using other means but, this program isn't designed to be deployed in such a fashion. Especially with Windows 10, M$ has interwoven so many aspects of OS to the point where only soft changes are safe. If you were to get any more abrasive than that, you can potentially brick your OS.. That being said, by automated integration, do you mean like a custom .wim file? If so, that would be very counterproductive for the aforementioned reasons. You see, any soft (non-permanent) or hard (permanent) change, mod or customization can lead to 1 of 2 scenarios: 1) a soft change even if in a custom .wim file can be undone by any update or patch by M$. 2) You get too deep in the coding of Windows and run the risk of permanently damaging dependent components of the OS. What I mean is command line. I would like to be able to deploy is with command line arguments. You know, in a command window. As in a bat file. How difficult is this to understand? I don't know of any command line tools that will engage the necessary files and functions to achieve the same output as ONE. I am looking for command line tools that will configure ONE, NOT to replace it.

To help prevent irreversible damage, this program is designed to be non-invasive. This program is solely reliant upon itself in terms of functionality hence why you can't rename, move nor delete the file while in use.. A similar effect can be done using other means but, this program isn't designed to be deployed in such a fashion. Especially with Windows 10, M$ has interwoven so many aspects of OS to the point where only soft changes are safe. If you were to get any more abrasive than that, you can potentially brick your OS.. That being said, by automated integration, do you mean like a custom .wim file? If so, that would be very counterproductive for the aforementioned reasons. You see, any soft (non-permanent) or hard (permanent) change, mod or customization can lead to 1 of 2 scenarios: 1) a soft change even if in a custom .wim file can be undone by any update or patch by M$. 2) You get too deep in the coding of Windows and run the risk of permanently damaging dependent components of the OS. What I mean is command line. I would like to be able to deploy is with command line arguments. You know, in a command window. As in a bat file. How difficult is this to understand?