UMSKT
UMSKT copied to clipboard
UMSKT
What about Windows 7 & Office2010 supporting?
This is being looked at, but windows vista-7 era activation is much more complicated. Getting results may take some time.
mmm... i don't know if adding ms products that use the PiDX licensing system is a good idea as PiDX is still being used by ms
my recommendation is to NOT look in to it. i don't want this awesome project get taken down by ms and there legal team.
PidgenX is used by Windows Vista and 7. For Windows 8-11, there is a separate algorithm called PidgenX2, as exported by Windows 10's pidgenx.dll. Due to the introduction of a new character set and radically different encoding scheme, it's safe to say that reverse engineering PidgenX will not have too much of an effect on the security of modern Windows keys.
The main problem is that Windows 7 keys work on Windows 11. If you could make your own Windows 7 keys, Microsoft would have to either stop allowing upgrades from Windows 7 to 11 for free, or worse, invalidate every Windows 7 -> 11 license made in the past something days.
But I know somebody have generateted vaild win7 or office keys, but these keys can't activate systems, MS's server verify these keys as faked ones. So the key generatating is one thing ,but the most important one is how to calculate the activation ID.
@thepwrtank18 i think you already [digitally] walked in the landm-[This Account Has Been Locked Due To A DMCA Compliant From Microsoft]
@thepwrtank18 i think you already [digitally] walked in the landm-[This Account Has Been Locked Due To A DMCA Compliant From Microsoft]
The amount of landmines per sq. meter goes up as you go towards the destination, in this case we're not completely covered (yet)
I Think You [Digitally] Stepped On Another Landm-TAKE DOWN THIS DAMN REPOSITORY YOU SON OF A GUN!
I was about to ask about Windows 7, Windows Server 2008 R2 and Microsoft Office 2010.
There's also Windows Server 2008 R2 which is based on Windows 7 and loses any form of support from Microsoft at the end of this year. I think there should be rules regarding what versions of Windows and Office that this project supports, either end of lifecycle or end of lifecycle plus 2 years or more. Under the less conservative version of that rule, Windows Server 2008 R2 could be supported by this project soon.
All support for Windows 7 has ended but it's a special case vs Windows Server 2008 R2 because of the fact that Windows 7 keys can be used to activate Windows 11. I would want to be really certain that this project cannot be used to activate Windows 10 or Windows 11 and verify that's true for many months before including support for Windows 7 and the code for it.
As far as take down notices, I'm a little surprised that this project is solely hosted on GitHub, a Microsoft entity.
As far as take down notices, I'm a little surprised that this project is solely hosted on GitHub, a Microsoft entity.
So is MAS: https://github.com/massgravel/Microsoft-Activation-Scripts
Not Related But I Have A Spreadsheet Containing Alot Of The Necessary Channel IDs
Check It Out If Your Interested: https://docs.google.com/spreadsheets/d/1YQQpolvfqAW6bJhKLVjVYxrmJhX_Za0l/edit#gid=39725250
Related to this, there's also the ESU keys and activation for Windows 7 and Windows Server 2008 R2.
Not Related But I Have A Spreadsheet Containing Alot Of The Necessary Channel IDs
Check It Out If Your Interested: https://docs.google.com/spreadsheets/d/1YQQpolvfqAW6bJhKLVjVYxrmJhX_Za0l/edit#gid=39725250
do u know what version these softwares are? retail, oem, vlk etc
oh... i did not think about that.
well, to be honest with you, oem & retail keys are very similar
oh... i did not think about that.
well, to be honest with you, oem & retail keys are very similar
in what way?
I did make a gist from that sheet with what they were (retail, oem, etc..). Look at my public gists.
All support for Windows 7 has ended
That's not entirely true. Windows Embedded POSReady 7 is still getting monthly security updates, until Jan. 9th 2024, and those can be made to work on other versions of Windows 7.
I Forgot To Mention One Thing: The pkeycofig Files!
techguy16: The pkeyconfig Files? TrialMedusa64: The pkeyconfig Files!? Both: THE PKEYCONFIG FILES!!!
Lets Focus On Vista & Office 2010, Remember! We Don't Wanna Get Into Legal Trouble With Microsoft!
Got That @techguy16?
Also How In Holy World Do You Get Channel IDs From Those pkeyconfig Files?
Windows 7 key validation has been reverse engineered: https://github.com/UMSKT/writeups/blob/main/PKEY2005.md
WHAT THE HEEEEEEEECK is "PKEY2005"? I Think Calling It "PiDX" Would've been a better name
Ohhh! I Get It Now! Where Going By Codenames! I Can See Where This Going! :D
TrialMedusa64: I Still Think PiDX Is A Better Titl-[Gets Cut Off] Pretty Much Everyone: OK WE GET IT ALREADY! TrialMedusa64: ok
also i have a question: HOW IN THE BLODDY WORLD DO YOU KNOW THAT "PKEY2005" IS A REAL MICROSOFT CODENAME!?