Now isn't the thread you kill supposed to return some value to somewhere else? Will that caller function just wait forever or can it cause problems after a long uptime?
Ok guys, latest version sendspace .com/file/o60clx Execute it with install argument and it will copy itself to Startup folder Ex: "Thread Killer.exe" install Or execute with remove argument to remove it. Ex: "Thread Killer.exe" remove And here is the source to who want to take a look it and help improve it. sendspace .com/file/dvq5sf
what you do is you place the program in your startup folder. the program kills the thread that will call the thread to show the activation watermark. and the program will quit. so there is no active application then. (when you restart explorer you will need to rerun the program once) and yes its for x64 and x86
No closing a thread will not cause a Waiting loop in this usage, it closes the thread that was causing the waiting bug in the old patched .dll version so no problems with CPU usage (look at my top post picture for proof). The link in my previous post will take you to the solution, and it is a AIO, has x86 and x64 in one file, I just wrapped it into a SFX that places it in your startup folder. it will work on all Windows 8 RTM versions.
I know, thread A will call thread B which in turn shows the watermark. But where does thread A come from? Are we sure there isn't some thread X that has previously called thread A? And isn't that X waiting for something? I also know it won't loop, but is a thread that's waiting for a return forever considdered "healthy"? Not that I can do better, it's just a question I had.
Ok I updated my SFX with the new version, it now extracts to the current user too (I had it go to All Users in v1) Thread X doesn't exists The activation routine is started from an Explorer Thread, nothing waits for Explorer.exe to return info except itself and the only part of explorer that worries about activation is in the thread they kill It's tested as safe, if you still don't trust it then there is little more I can do to persuade you, just try it yourself. You no longer have to place it in Startup UnknownRE (as per your sig advice), mine is a SFX and does that for you and with the new (install or remove) command arguments he added to the new version it's even easier if you choose not to use the SFX one. Strange you are having problems with Classic Shell - it's been rock solid here for me. -EDIT- BTW, I thought it better to use All Users because if your using a multi user Install, you'll have to run it once per person, any reason you chose to use current user?
But this isn't so good. KMS isn't reliable because it can be down every Minute. If we can unlock the customization Options now, nobody Needs a activated Windows 8.
Ok what about this I booted -up my computer just now and the activationmark appeared before the program was started could we wrap it in a service so it works al the time
WTH, never seen the watermark before the 4 hour mark, maybe it does have a counter that makes it appear instantly... If so, you've obviously just booted your PC and it would be easy to: 1.Run Task Manager 2.Right Click on "Windows Explorer" and pick Restart 3.Run Thread Killer.exe manually A hidden service would be ok to run all the time, the app is only 30kb, but I don't mind doing it the manual way... gotta be some reason to activate legally right we won't all be purchasing Win 8 for the Start Screen after all.