Unable to activate

[Guest]

I have added another drive to my unit through a scisi card, as this is not
the c drive I did not foresee any problems. When I rebooted the system it
told me I have three days to activate "no problem" I thought. When I try to
activate my system nothing happens, the keys on the taskbar disappear but the
wizard does not start, there fore I have no phone numbers to contact. I have
searched the knowledge base and can find no answer to the problem although I
have checked to see if Active Scripting was disabled as suggested in one
article, any ideas please?

 

[Ron Martell]

I have added another drive to my unit through a scisi card, as this is not
the c drive I did not foresee any problems. When I rebooted the system it
told me I have three days to activate "no problem" I thought. When I try to
activate my system nothing happens, the keys on the taskbar disappear but the
wizard does not start, there fore I have no phone numbers to contact. I have
searched the knowledge base and can find no answer to the problem although I
have checked to see if Active Scripting was disabled as suggested in one
article, any ideas please?

Try repairing the registry entries for the .DLL files used by
activation.

Use Start- Run and enter the following text in the dialog box:
regsvr32.exe regwizc.dll

Then do it again with the following text:
regsvr32.exe licdll.dll

Launch activation manually:
%SYSTEMROOT%\system32\oobe\msoobe.exe /A

Good luck

Ron Martell Duncan B.C. Canada

 

[Guest]

Try repairing the registry entries for the .DLL files used by
activation.

Use Start- Run and enter the following text in the dialog box:
regsvr32.exe regwizc.dll

Then do it again with the following text:
regsvr32.exe licdll.dll

Launch activation manually:
%SYSTEMROOT%\system32\oobe\msoobe.exe /A

Good luck

Ron Martell Duncan B.C. Canada

Cheers for the help, you were spot on with the solution, the licdll.dll file
was missing from the system32 folder.
Windows is now activated
Many thanks
Mike

 

[Guest]

Ron,

Is M$ aware that law abiding paying customers such as Mikey don't have to go
throuigh this routine everytime they decide to change something on their
system. Where is that thingy called freedom and free choice?

It is ridiculous to be treated as a criminal when your only crime is to pay
for a new hardware for a system which has legal OS.

I have to say that your instructions are quite good and straight forward.
Easy for novices to follow.

DW

 

[Ron Martell]

Ron,

Is M$ aware that law abiding paying customers such as Mikey don't have to go
throuigh this routine everytime they decide to change something on their
system. Where is that thingy called freedom and free choice?

It is ridiculous to be treated as a criminal when your only crime is to pay
for a new hardware for a system which has legal OS.

I have to say that your instructions are quite good and straight forward.
Easy for novices to follow.

DW

Actually instances that require this fix are relatively rare, and
usually occur because something malfunctioned in some way so that
these .DLL files were never properly registered during the Windows
install or upgrade process; or something deleted or damaged the
registry entries in some way. I would suspect "registry cleaning"
utilities as the most likely culprit for the registry changes but I
have no factual evidence to substantiate this.

Ron Martell Duncan B.C. Canada