Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


JTB3

Member
  • Content Count

    81
  • Donations

    $0.00 
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by JTB3

  1. Bizarre! I've run/tested the PDBDownloader on my Win10 laptop, which does NOT have the debugging tools installed on it, and it runs/downloads the symbols perfectly (without any need to run as admin)! I'm not sure what's different on your system or what could be causing that CMD window to appear. Even the Github home page for the repository says specifically that 'No Debugging tools are Required' and 'No Admin access' required. https://github.com/rajkumar-rangaraj/PDB-Downloader ...
  2. I've had the same issue with the symbols not downloading after Win 10 cumulative updates. Here's a very simple tool/method to manually download the symbols without the need to install the Windows Debugging Tools. Simply: Download the free/open-source 'PDB Downloader' here: https://github.com/rajkumar-rangaraj/PDB-Downloader/releases Run the standalone program and set the 'Saving To:' directory to your local AeroGlass/Symbols location: Next, in the PDB Downloader, open the following 2 files: • C:\Windows\System32\dwmcore.dll • C:\Windows\System32\uDWM.dll Press the 'Start' button at the bottom to begin the download process (see screenshot below). Voila! Now simply hit 'Retry' on the Aero Glass error window, kill/restart dwm.exe in Task Manager, or reboot. You are now 'good to go!' The above 'works like a charm' in just seconds anytime there is an issue with the AeroGlass symbols and requires no installation of the win debugging tools. Hope this helps! -JT
  3. This post listed above gives instructions to manually download the latest W10 symbols to work with any version of AeroGlass. I recently used this technique after the previous cumulative update, and I expect it should work fine for the 19H2 update... -JT
  4. Yes, the script only gets run 'on logon', just before Chrome auto starts. If one manually exits Chrome, the shortcut used to relaunch (as mentioned previously) must also contain the additional startup switch(s). As far as your closed tabs are concerned, I recommend the awesome 'session buddy' Chrome extension: https://chrome.google.com/webstore/detail/session-buddy/edacconmaakjimmfgnblocblbcdcpbko
  5. Great @AdamW! Hope it all installs smoothly for you... -JT
  6. @gitit20, The last file is the .XML/task profile to be imported into the Windows Task Scheduler. Nothing else needs to accompany the .exe file. After importing the 'ChromeAutoLaunch' task scheduler profile, check that the 'Run with highest privileges' security option is also checked and that the profile is indeed being run from your Windows user account. Also double check that the .exe has been copied to the 'C:\System\Scripts' directory and that this matches the ChromeAutoLaunch.exe location in the Task Scheduler. The icon file is only needed if one edits and then re-compiles the script. Hope this helps. Everything works flawlessly on all of my PCs -JT
  7. @gitit20, In the 'ChromeAutoLaunch' task scheduler profile, check that the 'Run with highest privileges' security option is checked and that the profile is indeed being run from your Windows user account. Also double check that the .exe is indeed located in the 'C:\System\Scripts' directory.
  8. For anyone that's using AeroGlass with Chrome Browser (v76+) configured to startup with windows and run in the background, you've probably noticed that the required command line switch --disable-windows10-custom-titlebar is NOT remembered at startup time. Unfortunately, if you manually edit the ChromeAutoLaunch registry key, it will get overwritten every time Chrome exits. To address this issue, I created a simple AutoHotkey script that is run 'on login' as a Scheduled Task that automatically adds the necessary startup switch to the required 'ChromeAutoLaunch...' registry key (which has a custom suffix for different users). I also added a 2nd useful switch --save-page-as-mhtml as well. The compiled script, source code, task scheduler (xml) import file, and installation instructions can all be found at this Link. Cheers, -JT
  9. For anyone that's using AeroGlass with Chrome Browser (v76+) configured to startup with windows and run in the background, you've probably noticed that the command line switch --disable-windows10-custom-titlebar is NOT remembered at startup time. Unfortunately, if you manually edit the ChromeAutoLaunch registry key, it will get overwritten every time Chrome exits. To address this issue, I created a simple AutoHotkey script that is run 'on login' as a Scheduled Task that automatically adds the necessary startup switch to the required 'ChromeAutoLaunch...' registry key (which has a custom suffix for different users). I also added a 2nd useful switch --save-page-as-mhtml as well. For the benefit of the AeroGlass community, I've attached the complied script and source code in a Zip file. Installation Instructions: 1) Create directory: C:\System\Scripts 2) Copy ChromeAutoLaunch.exe into this directory 3) Open Windows 'Task Scheduler' and import and save the ChromeAutoLaunch.xml task file. The scheduled task will run both at startup and every time the registered user logs in and will insert the switch(s) into the reg key before chrome starts. If one manually exits Chrome, the shortcut used to relaunch (as mentioned previously) must also contain the additional startup switch(s). Feel free the edit the code (+task) and recompile it if you would like to customize either the script directory or the switches to be inserted. Cheers, -JT ChromeAutoLaunch_AHK.zip
  10. Tested the new AeroGlass v1.5.12 all day yesterday and today. Working flawlessly on both of my computers running BOTH 1809 and 1903. Great work @bigmuscle!
  11. Many thanks for this latest release, @bigmuscle I'll be installing this later today after my 1903 upgrade! -JT
  12. No issues on my end either. Hopefully we are close to a full release @bigmuscle If more time is still needed, pls consider releasing a 'beta' for registered license keys w/o the debug window & watermark. Thx for your continued work on AG!
  13. Thanks! Another breath for Aero Glass on Chrome!
  14. @UCyborg In which Chrome version does this new parameter/switch go into effect? I just tested it in Chrome 75 and it doesn't work. Perhaps Chrome 76?
  15. @UCyborg Is this good news? Does it mean that the 'disable-windows10-custom-titlebar' parameter/feature will still be available in Chrome 76? (and beyond?)
  16. Can anyone summarize the 'negative' side-effects of using 'Win 8' compatibility mode with Chrome / AeroGlass. I for one, noticed significantly slower page reloads and new tab/window creation. What other side-effects have been observed? Thx!
  17. Thx for confirming this @UCyborg, Sad to hear... So much of my desktop experience is in Chrome-based browser and app windows (I'm sure this is also true for many others). This makes me think twice now about using (and waiting months) for delayed Aero-Glass updates. -JT
  18. Thanks @Wolfshadow! Looks like the 'writings on the wall' with this capability then. The 'Win 8 Compatibility" method is a poor substitute. Perhaps someone will discover another workaround... -JT
  19. @Wolfshadow Curious - Where did you read that the flag functionality will end with Chrome v76?
  20. Here's a solution for one remaining issue with the new command-line fix... @UCyborg If your Chrome browser is set to start in the background automatically with Windows (for certain extensions like Hangouts, etc.), Here's how one can edit the Chrome AutoLaunch command line in the registry: Open Regedit.exe and navigate to the following key : HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run Find the string named: "GoogleChromeAutoLaunch_......" and right-click to modify the text/command line to add the new parameter: (Here's what mine looked like when finished:) "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" --no-startup-window --disable-features=Windows10CustomTitlebar /prefetch:5 Now Chrome will autostart in the background with the AeroGlass compatible title bars. -JT
  21. OMG @UCyborg !!! I'm just seeeing this awesome solution now!!! You are a shooting star!!! ★★★ Thank you sooooo much! -JT
  22. @UCyborg I just solved the window border issue by using "Winaero Tweaker" and adjusting the Customize Windows Borders "Border Padding" slider down to 0 (initially it was set to 4, the exact width of the problematic new borders highlighted in the image above). I hope this info helps anyone else attempting to work around these annoyances! -JT
  23. @UCyborg The (Win 8) compatibility setting almost worked, now these annoying black borders are appearing below the Chrome top frame (see screenshot - border bars circled in green). Do you have any suggestions on how to remove these border bars introduced by the compatibility setting? Many thanks! -JT
  24. Thank you soooo much, @UCyborg! The compatibility mode setting (for Win 8) worked like a champ!
  25. Chrome was recently updated to version 74 and appears to no longer support native W10 title bars (and the AeroGlass effect). The #windows10-custom-titlebar flag is also no longer available along with the ability to 'Disable' it. Does anyone know of an alternative/workaround to re-enable AeroGlass support for the new Chrome 74 title bars?
×
×
  • Create New...