just noticed that explorer.exe is using constantly high cpu load so maybe its trying to display the activation nag and its looping if that's the reason and not some weird coincidence then patching by betonesto would be useless and we are back to square one more people should check and confirm
Yes, confirmed. The patch removes the watermark, but the cpu load is after 3 hours very high (46,7%). The process which causes the load is Explorer.exe.
C:\Windows\System32 and C:\Windows\WinSxS\amd64_microsoft-windows-twinui_31bf3856ad364e35_6.2.9200.16384_none_cc711f1543255f99 That wont work it still is coming back for me after a few hours (im running another machine now for 7 hours and no watermark yet (My WCP Editor 1.1 and my patched X64 dll (in the system32 folder) that's it .. (Will keep you posted)
Try out our AutoPatcher and see if it stays modded. BTW, you can't edit or even read twinui.dll while it's in C:\Windows... subfolders, in my code I move it to %Temp% it works as intended there. Even if you rename the file, it act very strange if you use a hex editor on it while it's in C:\Windows\System32\ going to the patch offset in the files while they are there showed totally different code to the real stuff, so move your files out of there if doing manual edits, exit explorer and delete the .dll, then copy the patched dll from a fully writable source (such as %Temp%\). That is how I got mine working with that patch. Trust me, I was confused for ages after monitoring a live system, so the patch works, just getting it to stick is harder, thus the need for the automation
yeah... nice question LiveFreeDead.... We must clear the matter: who make what and when. Then, all of us we can make the right choose. Now its very confusing.... What is working, it is based on another work of another people? Including detailed extractions for newbies or for peoples which are confused about different folders like System32, SysWOW64, WinSxS. What they must do and what they do not touch. That is my kindly suggest...
I agree, there are so many different files and information posted in this thread that I don't even know where to start? What is the best working solution?
I'd suggest at page 1. If you read everything you'll understand who made what based on what. The only confusing thing is who copied what where and all the reports of stuff working and not working
the best one is 32 bit patched dll by woot332 there is link on the first post all other are not working, broken, doing high cpu load in some time and there is one other unconfirmed does it work correctly or does not
@dummekuehe nope the first post does not including infos about x64 version... We know about x86, it is working, etc etc, its ok its enough. For x64 the thread is confusing others. "Test my file, no test my file, not working, oh working, etc etc...." We must clear out what is working, if it based on another work (for minimizing the useless downloading and patching the same files) etc etc...