DWMBlurGlass - No auto start

[DumboNY]

While I appreciate everything you´re doing here and I love DWM BG in itself, I simply cannot understand why you don´t have a SINGLE word in your instructions about DWM Blur Glass and how to run it automatically, if even possible

For now I have not found any solution, neither online nor in the software itself. Which means that every single time I restart/shut down my PC I have to manually run DWM Blur Glass, then change any parameter and save it - in order for it to run!

Soooooo

1. Is there an option to have DWM Blur Glass to run automatically on Windows start-up, as any OTHER software?
2. If yes., how?

Thx

[Maplespe]

By design, clicking "Install" creates a scheduled task that runs automatically every time the system starts.
You should be able to find a task named DWMBlurGlass_Extend (or something similar) under Computer Management -> System Tools -> Task Scheduler.

If you cannot find it, please check the following:

• Is your Windows Task Scheduler service running normally?
• Was the task creation blocked by any third-party software or antivirus?
• Are you logged in with an Administrator account?

[DumboNY]

By design.......your or whoever design it is, is flawed!! Also by asking me a question such as "Was the task creation blocked by any third-party software or antivirus" - even though I told you that you can run it manually. Which already means that it is not blocked by anything!
Basic software knowledge

I did some more investigating myself, and the scheduled task you have built in was defined as "at log-on" which is absolute BS! If you have a user which has no password set-up for the log-on, many software will never regonize a "log-on" when starting up Windows. Again basic PC/hardware/software knowledge

What I did now is the proper thing, I created a new task for DWMBlurGlass_Extend to run "at startup" - which should have been done from the beginning
Programs do not run "on log-on", programs run "on start-up"

You´re welcome for solving your own issues,. share it with other users

[Maplespe]

I believe there is a fundamental misunderstanding here.

First, this is a standard procedure for troubleshooting software issues. Secondly, launching the software manually and automatically starting at boot are two completely different mechanisms. Antivirus software might not block the application from running directly, but it may block the specific action of registering a startup item (registry key or scheduled task). When you click "Install" inside the software, it launches immediately for the current session, while simultaneously registering a scheduled task in the background for future boots. These are separate actions unrelated to the current successful launch.

Regarding your claim: "If you have a user which has no password set-up for the log-on, many software will never recognize a 'log-on' when starting up Windows" — this is factually incorrect.

Even if no password is set, Windows still performs a "Log on" event. On our test machines, we never set passwords, and the automation works perfectly.
The technical definition of "Log on" in Windows is "entering a Desktop Session," not "whether a character string was entered for authentication."

Microsoft's official documentation clarifies this: accounts with blank passwords can run tasks, but they are restricted to Console Logons (physical access) and are prevented from running in remote/network scenarios (like FTP or Remote Desktop) or as batch jobs. It does not mean they cannot run; it simply means the security policy is stricter regarding the login context.

Why do we not choose the "At Startup" trigger?

"At Startup" refers to the point where the system kernel has loaded, but the graphical user interface (GUI) has not fully initialized. This trigger is typically intended for background services or system-level processes that do not require a GUI.

DWM (Desktop Window Manager) is the core system GUI process, and it enforces strict privilege isolation. When you log in, DWM assigns a specific virtual sandbox user for that session. It is isolated from your standard user permissions.

You can verify this yourself: Open Task Manager -> Go to Details -> Find dwm.exe. Look at the User Name column. You will see names like DWM-1, DWM-2, DWM-3, etc., instead of your username.

For your reference:

• Accounts: Limit local account use of blank passwords to console logon only
• AppContainer Isolation
• Virtual Accounts

If we choose "At Startup," it introduces a race condition (timing issue). The software might work purely by luck if the system loads slowly enough that the GUI happens to be ready before the program launches, but this is not a reliable or stable solution.

Furthermore, due to DWM's privilege isolation mechanism where different users spawn distinct dwm processes, the application should logically be launched per user (At Log on), not per machine (At Startup).

[DumboNY]

You got the wrong guy to be explaining wannabe IT knowledge, which you picked up somewhere online by some experts. I have probably more years experience in IT than you have been living on this planet

You have no idea what you´re talking about, otherwise your software which is supposed to do basic stuff without even touching beneath the surface of the OS, is simply NON-FUNCTIONAL!

Windhawk has no problems running and auto-starting on my PC, uxthemepatcher never had. NOT A SINGLE program and software I had used within the past 20+ years for Windows customization had neither issues running nor auto-starting

Uninstalled, that easy.
Close the topic