All Keys listed for Home premium, Enterprise, Professional, Ultimate and KMSkeys

[Snuffy]

Windows 7 Ultimate 
FHY4Q-VB63H-XK8VD-9Y68P-RFQ43   -   Retail  -  MSDN Key
J6C9R-C9HHG-3CWTY-Y4MPW-CD72J  -  Retail   -  MSDN Key

so you know if you want to use. 

[gijs007]

I tried the ultimate keys but they don't work any more, not even with telephone activation. (I got windows 7 sp1 slipstreamed)

[Samtastic]

We'll need some more keys.

[Snuffy]

Seems that M$ has blocked all the MSDN & Technet keys...
There is a super good activator that has passed evry thing M$ offers.
It also does not take away anything... its called
uOdin by Secr9tos... I have tested version 1.0.0.2 and it works.
easy to find with Google.

[javajolt]

Total Virus Scan can be seen here

1. FIRST STEPS

1.1 What is uODIN?

uODIN is a derivative of "ODIN - The hardware independent - activator"
and is a new way in activating Windows 7 & Windows Server 2008 R2 as OEM.

Once activated you can enjoy your genuine Windows and can update using
"Windows Update", m$ online service, etc. without any issues.

1.2 What gets modified on my OS?

During the installation process a boot-driver gets applied to your system.
In addition any watermarks related to "Test Mode" get removed.

1.3 What are the supported OS?

• Windows 7 Starter x86
• Windows 7 Home Basic x86
• Windows 7 Home Basic x64
• Windows 7 Home Premium x86
• Windows 7 Home Premium x64
• Windows 7 Professional x86
• Windows 7 Professional x64
• Windows 7 Ultimate x86
• Windows 7 Ultimate x64
• Windows Server 2008 R2 Standard
• Windows Server 2008 R2 Foundation
• Windows Server 2008 R2 Enterprise

NOTE: The application refuses to run on an OS which is not listed above.

2. UN/INSTALL uODIN

2.1 GUI Interface "Basic"-Tab

The GUI in this tab is kept as simple as possible, but with the idea to
provide a basic overview about all important status-informations.

[button] "Install"
Well all it does is executing the required steps to apply the driver on
your system.

[button] "Uninstall"
As the caption of the button says, it reverts all changes completely.

[label] "Operation System Name"
This can either be "Windows 7" or "Windows Server 2008 R2".

[label] "Operating System Edition"
This field is e.g Ultimate or Professional

[label] "BIOS Vendor"
This represents the vendor of your BIOS, e.g INTEL or ACER

[label] "SLIC Status"
Normally this field has only two different of values.

1. e.g "SLIC2.1 is healthy, ACRSYS". This means that SLIC2.1 with OEM ID
ACRSYS ( =ACER ) is present on your system.

2. "SLIC2.1 not present". This should only appear if you have either
no SLIC2.1 per default in your BIOS or you have not installed uODIN.

[label/pic] "uODIN Install Status"
This field speaks for itself & is linked to O.I.S Status-Shield

[label/pic] "Windows Activation Status"
This field speaks for itself & is linked to W.A.S Status-Shield

2.2 GUI Interface "Advanced"-Tab

Well this tab offers the possibility to change what's gonna be installed.
In general, uODIN tries to find the best config for your system. If you
intend to modify it's behaviour, you should at least know what SLIC, Cert
& OEM:SLP means. Otherwise it's recommended to stick with the default
settings.

[drop-down menu] "Software Licensing Table"
aka SLIC, this drop-down menu let's you choose from all supported OEMs.

[drop-down menu] "Certificate"
This field must match with SLIC if no SLIC v2.1 is present on your PC

[drop-down menu] "OEM:SLP Productkey"
Basically you can't do anything wrong here. If you want to use a different
key, just select it. uODIN refuses to install not-correct keys through GUI

[checkbox] "Skip uODIN install on existing SLIC2.1"
This option is enabled by default and has the function to skip the install
of the driver if you PC is ready to support OEM activation. In this case
the correct Cert & OEM:SLP keys get's installed.

[checkbox] "Restart after un/install automatically"
As it says, after un/install you PC will be restarted without any notice.
So only pic this opt after you have saved your work.

[checkbox] "Create logfile at "%systemroot%\Logs"
This opt creates a logfile at the given path. This is checked by default,
coz if something goes wrong, this helps the author to see what went wrong.

THINGS TO KNOW FOR ADVANCED USERS

If you attach a kernel debugger during boot e.g you issue a HalBreakPoint,
uODIN driver refuses to run and therefore you will become non-genuine.

If your Windows installation gets booted with /DEBUG your system will
freeze at uodin driver initialisation if no KDBG is connected

This is a sort of protection to avoid modification of the code while
it is running. It's also digitally signed to guarantee the integrity
and to prove that only with the correct signature it comes from secr9tos.

Installation-:

Read Included .nfo File(s)

Always keep this in mind when installing releases....

.....Remember to block applications (or go off line) from calling home 'during install'.
Once installed, disable 'check for automatic updates' option if available, so that you don't get it blacklisted.....Where Applicable!!

PLATFORM: Windows
FILES : 1.25mb
COMPRESS: WinRar - Added Recovery Record
LANGUAGE: English

PassWord:- Code: 4shar1ng
 
have a look here

[gijs007]

I tried uloader 8.0.0.0, but it crashes one of my pc's(works fine on the others) because it has some broken sectors.
uloader seems to ignore these broken sectors and thus my system fails to boot.
it already took my a lot of time(3 days) to get it running(had to use bartpe which takes ages to load and then do a chkdsk) and then run windows 7 setup again.

so that's why im trying out serial keys...

[sankar_45]

Uodin does not seem to work for reactivation of MSDN keys.

[Snuffy]

uOdin converts all to OEM.... and uses the proper OEM Keys...

[sankar_45]

uOdin converts all to OEM.... and uses the proper OEM Keys...

Thank you. May be something else has gone wrong. It is not activated. The key is changed to OEM key.

[Snuffy]

Uodin does not seem to work for reactivation of MSDN keys.

I would highly recommend that you run and fix the bad sectors... usually mark them as BAD so they do not corrupt. 

I prefer this method.

Instructions
 
 1.  Click on the "Start" button and then click on the "Computer" icon.

 2.  Right-click on your hard drive and click on the "Properties" tab from the menu that appears.

 3.  Click on "Tools" and then go under the "Error-Checking" text.

 4.  Click on the "Check Now" button and check the boxes next to the "Automatically fix file system errors" and "Scan for and attempt recovery of bad sectors."

 5.  Click on the "Start" button and wait for the computer to scan your hard drive.

This might take some time... but if you have BAD Sectors...

Read more: How to Mark Bad Sectors on a Hard Disk | eHow.com

[Snuffy]

uOdin has support... it also has a how to make the report... it does make it as a .7z which many forums do not allow... make the report, change the extension to.zip or .rar
then submitt to Secr9tos.

you also might try this....
1. uninstall uODIN.....
2. Reboot,
3. check your status.... 
4. post here so I can see what #3 is....

[sankar_45]

uOdin has support... it also has a how to make the report... it does make it as a .7z which many forums do not allow... make the report, change the extension to.zip or .rar
then submitt to Secr9tos.

you also might try this....
1. uninstall uODIN.....
2. Reboot,
3. check your status.... 
4. post here so I can see what #3 is....

Thank you, Snuffy.

No bad sector in hard disk.

1. Uninstalled uODIN.
2. Rebooted.
3.Status: 28 days to activate. Activate Windows now.

This is the same status which was there earlier.

But the product ID is changed to OEM key.

[Snuffy]

Sorry for the delay... but when the sink starts leaking.... it does get Priority...
Normally if the ?KEY is OEM and it says OEM only not Activated....
you might see a popup from M$ stating your not Genuine - whould you like to get Genuine.
click YES. Then M$ will verify that you changed your KEY from Retail or MAK to OEM...
then you will next  find your Genuine and Activated.

[sankar_45]

Sorry for the delay... but when the sink starts leaking.... it does get Priority...
Normally if the ?KEY is OEM and it says OEM only not Activated....
you might see a popup from M$ stating your not Genuine - whould you like to get Genuine.
click YES. Then M$ will verify that you changed your KEY from Retail or MAK to OEM...
then you will next  find your Genuine and Activated.

Sorry. It does not work. There are no pop ups. Going to the Microsoft site and validating the OS (as suggested by the readme.txt of uODIN) confirms that it is Genuine. The OS is Genuine, but not activated.

[javajolt]

Checking your status of your installation

1. Click on the Start Orb and in the Search Box type winver when it displays at the top right click on it and Run as administrator.  The dialog box will display the version number at the top and the computer name at the bottom.

winver dialog box


2. Click on the Start Orb and in the Search Box type cmd when it displays at the top right click on it and Run as administrator.

3. Copy and Paste the following command slmgr /xpr and press enter a dialog box will be displayed saying Windows(R)     edition: This machine is permanently activated

xpire dialog box

[javajolt]

uODIN - The nested activation by secr9tos

1. FIRST STEPS

1.1 What is uODIN?

uODIN is a derivative of "ODIN - The hardware independent - activator"
and is a new way in activating Windows 7 & Windows Server 2008 R2 as OEM.

Once activated you can enjoy your genuine Windows and can update using
"Windows Update", m$ online service, etc. without any issues.

1.2 What gets modified on my OS?

During the installation process a boot-driver gets applied to your system.
In addition any watermarks related to "Test Mode" get removed.

1.3 What are the supported OS?

• Windows 7 Starter x86
• Windows 7 Home Basic x86
• Windows 7 Home Basic x64
• Windows 7 Home Premium x86
• Windows 7 Home Premium x64
• Windows 7 Professional x86
• Windows 7 Professional x64
• Windows 7 Ultimate x86
• Windows 7 Ultimate x64
• Windows Server 2008 R2 Standard
• Windows Server 2008 R2 Foundation
• Windows Server 2008 R2 Enterprise

NOTE: The application refuses to run on an OS which is not listed above.

_____________________________________________________

2. UN/INSTALL uODIN

2.1 GUI Interface "Basic"-Tab

The GUI in this tab is kept as simple as possible, but with the idea to
provide a basic overview about all important status-informations.

[button] "Install"
Well all it does is executing the required steps to apply the driver on
your system.

[button] "Uninstall"
As the caption of the button says, it reverts all changes completely.

[label] "Operation System Name"
This can either be "Windows 7" or "Windows Server 2008 R2".

[label] "Operating System Edition"
This field is e.g Ultimate or Professional

[label] "BIOS Vendor"
This represents the vendor of your BIOS, e.g INTEL or ACER

[label] "SLIC Status"
Normally this field has only two different of values.

1. e.g "SLIC2.1 is healthy, ACRSYS". This means that SLIC2.1 with OEM ID
  ACRSYS ( =ACER ) is present on your system.
 
2. "SLIC2.1 not present". This should only appear if you have either
no SLIC2.1 per default in your BIOS or you have not installed uODIN.

[label/pic] "uODIN Install Status"
This field speaks for itself & is linked to O.I.S Status-Shield

[label/pic] "Windows Activation Status"
This field speaks for itself & is linked to W.A.S Status-Shield

2.2 GUI Interface "Advanced"-Tab

Well this tab offers the possibility to change what's gonna be installed.
In general, uODIN tries to find the best config for your system. If you
intend to modify it's behaviour, you should at least know what SLIC, Cert
& OEM:SLP means. Otherwise it's recommended to stick with the default
settings.

[drop-down menu] "Software Licensing Table"
aka SLIC, this drop-down menu let's you choose from all supported OEMs.

[drop-down menu] "Certificate"
This field must match with SLIC if no SLIC v2.1 is present on your PC

[drop-down menu] "OEM:SLP Productkey"
Basically you can't do anything wrong here. If you want to use a different
key, just select it. uODIN refuses to install not-correct keys through GUI

[checkbox] "Skip uODIN install on existing SLIC2.1"
This option is enabled by default and has the function to skip the install
of the driver if you PC is ready to support OEM activation. In this case
the correct Cert & OEM:SLP keys get's installed.

[checkbox] "Restart after un/install automatically"
As it says, after un/install you PC will be restarted without any notice.
So only pic this opt after you have saved your work.

[checkbox] "Create logfile at "%systemroot%\Logs"
This opt creates a logfile at the given path. This is checked by default,
coz if something goes wrong, this helps the author to see what went wrong.

[javajolt]

Using your Windows 7 disc  will remove most loaders but will not remove exploits that use other methods.
 
 To remove a loader.
 
 1 boot to the windows's DVD
 2 Selectrepair PC
 3 In the console type this:
 
 bootsect.exe /nt60 all
 bootrec /fixmbr
 bootrec /fixboot
 bootrec /rebuildbcd
 this will clean all the loaders that may be installed. BUT ONLY do this if you have reason to suspect that a loader was previously used, as I  said, I do not know what that error code means.

[Snuffy]

Also as stated by JavaJolt... you might simply try an do a manual Activation.
Cmd -> run as admin -> slmgr /ato

also you might check your KEY - to validate it matches the License.
M$ has implimented a check to verify the KEY = Certificate/License.
if the KEY is Acer the Certificate must be Acer...
there are several method to verify the FULL KEY... one is a FREE Belarc. It will check and in the report give you the FULL KEY...
The KEY and Certificate used "Should match your BIOS." if your BIOS is Acer use ACER  Not Asus. 
so again... If you failed to select the proper KEY/Certificate when you first install uOdin.... Uninstall uOdin, then verify that uOdin is not installed.
the program it self will do that.... next - REBOOT - then install uODIN and select the KEY/Certificate which match your Manufacture Bios...
give uOdin the proper full length of time to fully install.... it then should when you click OK on the final... AUTO REBOOT....

[fdhealy4]

Are there any keys for Home Premium 32 bit. All I see are 64 bit ones, or do they work for both.

[javajolt]

32 bit & 64 bit keys are not interchangable.