Can't rearm my Win

[AndreuT]

Hey everyone,

so i tried to rearm my Win7 Prof 32bit for the very first time with the "slmgr -rearm" command.
When i run the "slmgr -dlv" command it now shows me a remaining time of 29 days. That's ok.
But when i go to control panel/system it still shows me "2 days left".

Anybody experienced the same? Did the rearm work or should i worry about what happens in 2 days?

For reference here's what i did: link

 

[Brink]

Hello Andreu, and welcome to Seven Forums.

If you activate Windows 7 with your product key, then you would not need to worry about it.

http://www.sevenforums.com/tutorials/3408-activate-windows-7-online.html

http://www.sevenforums.com/tutorials/18715-activate-windows-7-phone.html

 

[AndreuT]

Thanks for the welcome and the ultra-fast answer Brink

I eventually will activate it.
I'm a valid member of the Dreamspark-Licence program, but we currently have a problem with the Webstore of our faculty our Admin is trying to sort out.

Unfortunately i'm in the need of the webstore right now (see above) so i decided to just rearm my windows for the next 30 days until all problems are sorted.

 

[Kari]

Hi Andreu, welcome to the Seven Forums.

Sometimes the most obvious things go unnoticed so I have to ask this: did you reboot after the rearm command? A reboot is needed to update the rearm status.

Kari

 

[AndreuT]

Thanks for jumping in Kari and for your welcome.

Yes, i did reboot after the rearm command.

 

[Kari]

OK. Not knowing what causes this there is a workaround. Please notice that if you decide to try this it is in your own risk.

Give the following command in an elevated Command Prompt:

%windir%\system32\sysprep\sysprep.exe /generalize /oobe /reboot

This will generalize your Windows (remove all hardware related information like drivers) and reboot to OOBE, the Welcome Mode seen when newly installed Windows is booted first time.

Notice that OOBE setup will ask you to create a new user account but as your old user account still exists in system (together with all your apps, programs and files), you cannot use that username now. Create a dummy account which you can later remove.

   Note

What does Sysprep generalizing do to my Windows 7 setup?

• All system specific information is removed or uninstalled
• Security ID (SID) of your hardware setup is reseted
• All system restore points are deleted
• All event logs are deleted
• All personalization is removed (taskbar, toolbars, folder options, start orb etc.)
• Built-in administrator account is disabled (if it was enabled) and needs to be re-enabled again if needed

This way your Windows is like new giving you a fresh 30 day grace period.

Kari

 

[Indianatone]

Kari, can this be run from the command prompt on a repair install boot if you forgot to do it before removing the drive from the old PC?

 

[Kari]

Kari, can this be run from the command prompt on a repair install boot if you forgot to do it before removing the drive from the old PC?

Theoretically yes, in practice no. The Sysprep sees in case you described the recovery system as OS and tries to sysprep it.

I do not recommend trying, it can have catastrophic consequences...

 

[Indianatone]

Kari, can this be run from the command prompt on a repair install boot if you forgot to do it before removing the drive from the old PC?

Theoretically yes, in practice no. The Sysprep sees in case you described the recovery system as OS and tries to sysprep it.

I do not recommend trying, it can have catastrophic consequences...

OK thanks for that, I have a HD which was replaced by SSD and want to reuse the install (with different keys) so I'll put it back in the old box and do it there.

 

[Kari]

Yes, exactly. Here's a tutorial for that, Method One is for you: http://www.sevenforums.com/tutorials/135077-windows-7-installation-transfer-new-computer.html

 

[Kaktussoft]

Kari, can this be run from the command prompt on a repair install boot if you forgot to do it before removing the drive from the old PC?

Theoretically yes, in practice no. The Sysprep sees in case you described the recovery system as OS and tries to sysprep it.

I do not recommend trying, it can have catastrophic consequences...

OK thanks for that, I have a HD which was replaced by SSD and want to reuse the install (with different keys) so I'll put it back in the old box and do it there.

Or do this http://www.sevenforums.com/tutorials/292068-make-windows-7-bootable-after-motherboard-swap.html

 

[NoelDP]

Let's have a look at your real situation....

Any installation of Windows will allow THREE re-arm attempts, and then lock down - in the case of Windows 7, all that means is a black background and a nag (and inability to do non-security updates or install MSE)

Please follow this tutorial and post an MGADiag report - then we can see what the problem is.

http://www.sevenforums.com/windows-updates-activation/234159-windows-genuine-activation-issue-posting-instructions.html

Ignore errors produced when clicking on the Copy button - they simply mean that the tool could not create the backup files for some reason. The data is still copied to the clipboard for pasting to your response.

Please also state the Version and Edition of Windows quoted on your COA sticker (if you have one) on the case of your machine (or inside the battery compartment), but do NOT quote the Key on the sticker!
http://www.microsoft.com/en-us/howtotell/Hardware.aspx

 

[AndreuT]

Despite the thread derailed a bit i want to give some feedback.
Firstly thanks @ Kari and NoelDP for providing help.

After another abnormal rearm try i decided to just wait and see and its all okay.
No black desktop just the nag bubbles are popping up again. Maybe no non-security updates, maybe no MSE, we'll see, these dont have priority to me currently.

 

[NoelDP]

Please post the MGADiag report - you may just be back in a grace period.

 

[AndreuT]

?

Yes thats what i intended for now.

I eventually will activate it.
I'm a valid member of the Dreamspark-Licence program, but we currently have a problem with the Webstore of our faculty our Admin is trying to sort out.

Unfortunately i'm in the need of the webstore right now (see above) so i decided to just rearm my windows for the next 30 days until all problems are sorted.