My program acting as a service is being capable of killing the activation thread, even for multiply users. I still need to do some testing.
The watermark is still here after the patch. I've deleted the basebrd.dll.mui and now shows only the build Looks good removing this file
WHICH watermark are you talking about? The Windows 8 Pro Build 9200 one or the Activate Windows overlay? This patch only addresses the Activate Windows watermark.
Josh, that Desktop Build Watermark is non invasive, I am not even bothered by that one, even tho woot332 has offered a shell32.dll replacement that will stop it showing if it bothers you that much, we're talking about the Activation Overlay Watermark, it will show on top of Metro, Videos, Windows, Desktop the lot, this one is much more invasive and the one we're working on removing, it will appear after 3 hours (for some) and 4 hours for others), sometimes it will wait 6 or 8 hours, but this is even rarer. The Activation Overlay has the picture of 2 keys on it, if you've not had a system running long enough to see it your in for a nice surprise and will thank woot332 instead I am just about to run a x64 VM to verify the result woot gets, with the CPU usage testing, Metro app tests etc, I'll report the results here and in the Release thread I started (not a dev thread like this one). woot332 is the patch for x64 the same method as the x86 one, or a new one that might be adopted by x86? just curious for more details at the moment. BTW, I plan on running both Woot332's patches and sep's Thread Killer at the same time (why not), so having it as a service sounds good to me, as I know memory usage will be low and you'll be keeping an eye on CPU usage (please let me know your intended check delay in Micro seconds so I can tell people the correct method you'll be using in your service release, when you post it). I'll also be using My WCP Watermark Editor and woot's shell32.dll to remove the desktop one, that way if an MS update attempts to bring them back it'll have to update both things, I doubt they'll be updating the .mui's any times soon, but the shell32.dll gets updated all the time. That you both for coming back before new releases to share your progress, makes the thread more interesting when we know it's still getting improved upon.
I left my service running for hours in my computer, it's using around 13 MB of memory, 0 cpu usage. I'm also implementing a configuration file, so some options can be configured.