Oms, indeed. Probably should read his post better next time. Not that his post was that long in anyway. Guess I was still asleep.
I can pass the security essentials WGA check now and 4 months into the future. MGADiag reports genuine.
this is purely theorical... Where is the proof??... So lets see : u deni access to sppcomapi.dll.. U move the date to say 2019... Windows will enter in notification mode.. So how can it be genuine.. Ok just suppose that it is genuine..just let it run for at least 30 days to see if it's still genuine.. So what do you say?
ran in 2099 no nags, Have been running hack for over a month on the real PC, stil receiveing updates both critical and optional, no nags nothing. There is your proof.
So this not removing any activation necessity, so in reality it fools the os and of course m$..that window is still in trial..so it can be passed as genuine isn't it?
You must be using an OEM key for MGADiag to report as genuine. I am talking about using the default key which after trial period goes into notification mode. Notification == Non-Geniune
Hazar- Ok I'm waiting.. thank you Hazar.. btw- there is a bug in your 7Loader 1.6, unicode problems, see my post in your 7Loader thread.
Actually the initial grace period is constantly postponed. Is this the goal ? Won't it creates problems with Microsoft or inside the OS ?
It can be obvious but you shouldn't move the date after that indicated in slmgr -xpr or the watermark "this copy of windows is not genuine" will appear. I say it because sometimes you need to change the date. BTW I'm doing some test to your procedure under a VM but if you're right I think you've found the Philosopher's Stone (and someone in Redmond won't sleep well tonight).
So hazar i've remarked something..in the past when i was experimenting chew wga 0.7.. The only thing that I was unsatisfied of was the red invalid licence showing up in mga instead of genuine when going to yr 2099 (initial grace period expired, so the counter was still there)... So i did a s.restore which reverted the patch and returned to initial grace period... As i had the orbit activator 10.0.. I was playing with the "plus patch" I installed it in my grace period yr 2009, aka genuine in mga.. Then i re-installed chew wga...and set the date to 2099..mga was still showing genuine... Just understand 1 thing. When installing pluspatch in ini.grace.period then immediately before restarting i set the date to yr 2099 (i was in 2009).. After restarting it was genuine..but when I made an activation report with toolkit 1.8 suprise windows was still in ini.g.period..but it will end in 2099..same date but different year.. So windows wasn't in notification mode yet.. So when i returned in 2009.. Licence status with Activation report was empty... Checked it with w7ldr extreme edition from napalum..and it showed "notification " and no days was left.. But in mga windows was still genuine even in notification mode... So what did the pluspatch did ????
So your app is gonna use the bspatcher and just patch the files, or are you included the actual dll's
64bit and 32bit systemcpl prepatched dlls bundled along. 32bit is 100% perfect so far, just need to get 64bit dll from nononsence
I moved my date ahead a month then installed the trial key, I got the water mark then patched it, then as I find more nags Ill patch them. I have all these file on my desktop slcext.dll slmgr.vbs slui.exe slwga.dll spp.dll sppcc.dll sppcext.dll sppcomapi.dll sppcommdlg.dll sppinst.dll sppnp.dll sppobjs.dll sppsvc.exe sppuinotify.dll sppwinob.dll sppwmi.dll so far only updates are broken and the nags when I run these files. notpad wordpad calculator control panel after looking through the notpad code it really looks like these files have somthing to do with putting the system into notification mode.