DWMSuite

I don't think so, mainly because nobody has managed to simply get an older version of DWM working by swapping the binaries. This tool is mostly useful for disabling and reenabling DWM rather than changing the version.

Although nobody really knows that much about how DWM works internally, we do know that it is integrated with NT USER which is a kernel module. DWM is still mostly a userland application, hence why it is a standard exe you can close and why tools like Glass8 can modify it.

The source trees of some Windows releases can be obtained (presumably from chk builds) which has led to us finding files like:

(Note that the contents of these files aren't known, but the relationship can be proven.)

Speaking of Glass8 and 2004, as it is understood, they ended up heavily modifying DWM in 2004 according to valinet (the developer of ExplorerPatcher) in the MSFN thread for Glass8:

> Now, regarding DWM, it changed quite a bit in Windows 10 2004. A good couple of the methods BigMuscle hooked in pre-2004 are simply not there in the new DWM. Microsoft actually changed a lot of the underlying architecture. What exactly, for what purpose, what is the high level meaning behind it? I did not have time to look enough at it to figure it out.

If I had to guess, a lot of the reason for DWM's incompatibility between builds is syscalls changing, but I haven't looked into it.