@chbaldo: no problem, create automated installer if you want. @LiveFreeDead: x86 code patched, might be usefull locating the x64 code
Did you try this? For how many hours? Did you check if it does weird things with memory? Thanks for your work.
just don't post the link as a link and you can post it FYI : paste this in notepad en put it in the registry : Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\*\shell\runas] @="Take Ownership" "NoWorkingDirectory"="" [HKEY_CLASSES_ROOT\*\shell\runas\command] @="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F" [HKEY_CLASSES_ROOT\Directory\shell\runas] @="Take Ownership" "NoWorkingDirectory"="" [HKEY_CLASSES_ROOT\Directory\shell\runas\command] @="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t" "IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
one foolish question from me if you don't mind What will be happen if windows update install updates for that file for example...?
as I expected for the result. The problem is with the patching of system files, you must be there, again and again, doing the same procedure after some updates which may affect the patched files Another "prob" is the possibility, when updated file which comes with the Windows Update, adding more features, is more stable, adding more security etc. When copying an older file, is a possible security breach. Hackers searching many times in that... areas. Anyway, I want to thank from my side, UnknownRE for his work. Thank you, i'll try to use it. Personally, I don't care if the windows will be stay unactivated, just I cant live with the annoying watermark For the activation ok, I can wait like the rest of us, or maybe buying is the best solution. For now, until windows 8 will be released to the public on October, the watermark is really.... pain on the.... a#2#@#@#
well, I'm reporting back, according to the UnknownRE file. I have take the ownership of the file in C:\Windows\System32. I have rename it, and copy the patched file there. I have kill explorer, and run again explorer from Task Manager. The key watermark disappeared. Now... the sad is, after reboot, windows metro apps going crazy... Weather cannot opened at all, others can opened but boing to... the background after some seconds, (they do not close, just is there in background. when you going left to the screen to select them again, the same thing again and again...) It seems, the patched file affecting the use of Windows Metro apps. (in my case of course...) Can someone have the original x64 file, because after the reboot, I delete it accidentally, and I want it back, to test if... the problem with metro Is by.... this change... Update: I was copy the patched file, in the wrong place? for that windows metro apps going crazy? My god... I didn't see other posts where I was have to copy it. Anyway, From System32 someone which may have the file?
When you're going beyond patching strings and images in resources anyway and have started to add jump instructions and skip entire routines, why not directly patch the activation checking code? If the activation check always returns activated you won't have the watermarks and get a working customization as a surplus. Both are then handled instead of having to fix them separately. They might have used different ways of checking activation, but in the end there should be 1 function (or some more who work together) that rules them all. Of other things, like what does the ruling function check and patch those things. @ odiebugs: syswow64 contains x86 files. System32 is the usual folder with all the x64 files, but the original name is kept. x86 programs use functions and stuff from the x86 twin files in syswow64. EDIT: Lol, now I accidentally switched x64 and x86 myself
"syswow64 contains x64 files" WHAT? xD syswow64 contains x86 files, for WOW64 emulator syswow64 contains ONLY 32-bit libraries and executables