Zacharee Posted August 18, 2015 Share Posted August 18, 2015 I went from build 120 the build 149, hoping to be able to use the possible improvements on title bar button sizing, but when I updated and restarted aerohost.exe everything froze except my cursor. The only way I can fix this is by taking out my battery and forcing my computer to go into the advanced boot options by unplugging it during boot and renaming the folders using CMD. My question is, is there any reason for this? Are there any ways to fix it? I can provide more details if needed. Link to comment Share on other sites More sharing options...
Katsinwater Posted August 18, 2015 Share Posted August 18, 2015 I was actually updating to the latest 64-bit build 149 version myself when a Windows update came in all of a sudden...I had just finished replacing all of the new files and went to perform a restart when Windows update wanted to install their own update, once the system began to restart, I only got up to a light blue screen with very small code populating the screen. I had to remove my AeroGlass directory from my C:\ into my 2nd hard drive and restart my laptop. That was my fix... So it seems this latest Windows 10 update, which I didn't even write down is breaking my AeroGlassTesting Laptop...just when it was starting to look really good.. Link to comment Share on other sites More sharing options...
Zacharee Posted August 18, 2015 Author Share Posted August 18, 2015 It's annoying isn't it? It's a good thing the old build can still be downloaded. I guess we just have to wait for 150. Link to comment Share on other sites More sharing options...
GreyFox_1987 Posted August 18, 2015 Share Posted August 18, 2015 i got always an error if i try to inject the build 149 dll file. Any way to fix this? Link to comment Share on other sites More sharing options...
Zacharee Posted August 18, 2015 Author Share Posted August 18, 2015 You can't do that. It tells you in bold text on the Windows 10 page that you can't use the AppInit_DLLs method to enable Aero. You have to schedule a task that will run at startup and will run aerhost.exe. Link to comment Share on other sites More sharing options...
GreyFox_1987 Posted August 18, 2015 Share Posted August 18, 2015 You can't do that. It tells you in bold text on the Windows 10 page that you can't use the AppInit_DLLs method to enable Aero. You have to schedule a task that will run at startup and will run aerhost.exe.Thank you for your answer! Can you please explain how can i do that? Link to comment Share on other sites More sharing options...
Zacharee Posted August 18, 2015 Author Share Posted August 18, 2015 Open the start menu. Search "Task Scheduler." Click "Task Scheduler Library" under "Task Scheduler (Local)." Click "Create Task" on the right. Set the user for it to run as to "SYSTEM," set the trigger to startup or log on, and set the action to point to aerohost.exe inside of your aero glass folder. Either run the task or reboot. Link to comment Share on other sites More sharing options...
GreyFox_1987 Posted August 18, 2015 Share Posted August 18, 2015 Open the start menu. Search "Task Scheduler." Click "Task Scheduler Library" under "Task Scheduler (Local)." Click "Create Task" on the right. Set the user for it to run as to "SYSTEM," set the trigger to startup or log on, and set the action to point to aerohost.exe inside of your aero glass folder. Either run the task or reboot.Thank you very much! I get it to work! But what is the difference between this method and traditional one? Link to comment Share on other sites More sharing options...
Zacharee Posted August 18, 2015 Author Share Posted August 18, 2015 I don't know, but I guess it's more reliable and safe than the registry way. It also opens that spot up to the ModernFrame DLL. Link to comment Share on other sites More sharing options...
NoelC Posted August 22, 2015 Share Posted August 22, 2015 The reason is: The more recent Aero Glass for Win 8+ software (since WAY back when the Win 8 version was under development) is simply designed to be loaded by the AeroHost executable. The author says it should no longer be loaded via AppInit_DLLs. Note the bold wording on this page: http://www.glass8.eu/win_future.html Just for reference, Zacharee, you can have multiple DLLs listed in the AppInit_DLLs entry - just separate them with spaces. -Noel Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now