I was just having fun that day searching for GUI's in the .mui's and came up with some ways to prevent the nags and finally concluded this was by far the simplest method, originally I renamed slui.exe to slui.exe.bak but that gave nags to activate when opening applications like notepad which I solved by removing if I remember correctly the #7170 and 7071 diologues from the .mui's of those apps which worked great but I had to modify about 10 files so I scratched that method and am now more focused on the method which involves deleting one file and patching another. Patching the "user32.dll.mui" by modifiying string table 45 and 47 isn't really nessesary since everything works without it but I always do to remove the activation messege from the desktop in any case. For some reason "sppcomapi.dll" was included with the operating system but I don't see why when all it seems to do is annoy the user if he or she does not activate the system online so the logical thing to do for me anyway is delete it so I can continue with my daily activities without the activation reminders which I don't see much use for.
There's no need for safe mode as long as you are an administator and take ownership of both files there should be no problem. I wrote a batch script which patches the system automatically. You could use the script by itself or optionally with a copy of mcbuilder.exe and a modified user32.dll.mui to remove the lower right desktop watemark. I also made a self extracting executible which works well with one click and does all the dirty work for build 7100 and would probably most likely work with build 7600 as well but to be on the safe side I will make another one with the right version of use32dll. for build 7600.
kewl any chance for a upload of a test i have no troubles modding the files if that's the only file i need to mod
Looking forward to a link - will this only work on an OEM edition of Windows 7? Any chance you can provide instructions on how to run this when available? does this have a time bomb?? Thanks in advance
I will get back to you on this becouse I will first have to obtain the 64 bit client to and examine it's directories.
There shouldn't be. I leave my computer running overnight just to test and still works without any warnings or messeges. I set my BIOS clock for the year 2020 and un-inistalled the product key with slmgr.vbs and it's working so far, but time will tell.
One thing I forgot to mention is there is no genuine plaque in system properties that you would see after succesfull activation but this does not matter becouse the whole idea is to use it with out ever activating.
i played around also like you do.. and mine box is randomly giving messages.. no big deal atm... But i will do a new install. because i did to much poking around in the system files
@maddog so, at the beginning you said only one file must be renamed...now it mutaits to a batchscript whats concretly to do? or is it not enough to modify the one file.... in my x64 i have much dll´s like this