Has anyone tried to activate Windows 10 with Microsoft Toolkit by CODYQX4. I wonder if the likes of CODYQX4 and DAZ are working on it yet
I think Daz sorta gave up. Windows 8's activation threshold doesn't comply with the activation tricks he was using and it wasn't really worth digging into. KMS activation is the current way of easy activation.
Ok guys for this timebomb just give up. Yes I ran the old glitch that Cody just described but the windows boot loader is digitally signed. That means the signing is the timebomb essentially. If you go outside the date (say 2016) then the system will BSOD saying the digital signature for winload.exe is no longer valid. I'll get back to you if I figure out how to get past that. Some of the smart people may ask well what happens if you disable the integrity checking for BCDEdit during the boot up. Well it does boot but all the text for the operating system is gone so we get one really screwed up operating system that is completely impossible to use. I have a few ideas on how to bypass the timebomb but I need a little more time lol. Check it out: Also the guys who were looking at disabling the search in the task bar. That fancy thing is called Windows Embedded Search... go luck.
"but it screwed me over by locking me to 2GB or RAM and god only knows what other side effects." Yikes that sucks, locking to 2gb only? ... what is that, punishment for being a "bad boy" ?
You might say that lol but it was funny to try out. And then we see why I went with the title of Glitcher.
My best guess on why that happens is that... When you boot the OS winload.exe does not function properly to make winlogon.exe trigger. This means Shell32.exe does not load properly either. In other words you get cascading errors across the entire operating system according to what I have listed in my notes. This is probably because the entire bootup process is digitally signed or a significant portion of it is. That being said there is no clean way to get around that.
We have to know what timebomb do ? do it just restart all 1H if we use it after the date Or totally stuck the os ? It is possible to dump memory of the system in a VM ( and physical maybe ), so we can analys how boot process is managed. From what I guess it is just a little thing like if date > timebombdate then stuck the os else standard boot so we just have to find the switch and bypass it ( then resign it if possible )
Are there any longterm implications of this or it just something that seems like it'll only matter to the preview builds?
Yeah, I have test it, not really good, I will try to replace winload.exe from TP by winload from 8.1. Maybe it can work who know XD EDIT : auto-repair .. Not working XD