Is it good idea to intergrate .msp updates to the Updates folder in the volume edition of office 2010 without taking the risk of getting this version bricked? Thanks
Just when I thought I beat the system about to release I find it's useless all this time. I managed to patch MSO.DLL and get office to take all 0's for phone activation, but the activation means are wise to it, so it doesn't really activate. I'm trying to see what it changes but I think it won't help. 0's didn't work with KMS already activated. Blind luck last time? PS: Seems only to take it when bricked. It's useless anyway because OSPPSVC can tell an all zero activation code does not a real activation make, and therefore it never leaves notifications mode. Strange it doesn't auto repair or give notifications, but says cannot verify license, and closes.
OMG How is telling someone this app is not virus be mean? This same question arrises cause no one reads and out of most I thought I was most kind Banned for mis-percieving me actually being kinda nice
Tried it with MAK which is effectively retail. You can't phone activate KMS. I thought MS would be smart enough to solve this way. I still believe a real keygen could work, but an all 0's that only patches the dialog is what this is, it doesn't fool OSPPSVC into activating you.
Adding Keys.ini checking for backups and a universal list inside same folder as the toolkit (Keys.ini just a simple line by line list of keys). This will be in V2.1 final. There will be no further betas and this feature is for batch key checking. Note that key checking tools are slow so it may take awhile to do a list.
Yes because VL is better than retail, and we don't even have leaked keys for some retail versions to install them. Is isn't necessary if you have a retail key and you installed already though.