Problem is preventing windows from accurately checking the license

B

Beemer Biker

"A problem is preventing Windows from accurately checking the license for
the computer. Error Code:8007007F"

I googled this message and read up on the possible solutions...

I dont have the keys
HKEY_USERS\.DEFAULT\Software\Microsoft\Cryptography\Providers
....or...
HKEY_USERS\S-1-5-20\Software\Microsoft\Cryptography\Provider

so there are none to delete. In addition, I have the files oembios.dat and
secupd.dat. They are not missing from system32 which was also listed as a
problem.


I did find that the "D" drive was being used for the reinstall of XP home.
It was not supposed to have "windows" and I pulled out the "D" drive when I
discovered this (after about 3 re-installs). There is an article here
http://support.microsoft.com/?kbid=310794 that mentions replaceing D with C
or viceversa on some dell or gateway computers.

I have an oem copy of windows XP that I bought in 2000 and put on one of my
kids computers. I bought that oem copy with the motherboard and cpu from a
vendor in a single order. That motherboard finally went out, the capacitors
blew. It was a pentium III 1ghz socket 370 and it lasted about 5 years. I
bought an ASUS A7N8X with athlon cpu and substituted it for the defective
motherboard. I booted the OEM cd and when told there was an existing
windows, I selected repair. The installed seemed to go just fine but when I
rebooted I got that error message and am unable to log into windows. I
tried two additional installs includeing first building a slipstream OEM
"sp0" (my original home xp from 2000) and the latest SP2 from microsoft.
Same problem but when booting into the safe mode I discovered that windows
at somehow been put onto the "D" drive instead of the "C".

I pulled out the "D" drive and repeated the install with the oem cd. I
failed with the same problem. I booted into the safe mode and verified that
the new nvidia & asus chipset drivers had indeed been loaded and there were
no yellow bangs in "system". The START-PROGRAM shows that all my son's
stuff is still there, this system should boot up and run but I cant get past
that license check failure.

This microsoft article talks about what happends when the "D" is used
instead of the "C"
http://support.microsoft.com/kb/223188
I have drives listed from DosDevice\A thru DosDevice\J or maybe higher as
there is an 8-in-one flash memory adapter, two cdroms and (now) only one
hard drive. It would appear that "devices mounted" key listes all devices
even though I pulled the USB cable from the internal flash.

Does anyone know what is going on? How can I get past that license check
and re-active XP. Could the XP SP2 download have been only for XP Pro and
not XP Home? Maybe I should not have slipstreamed Home with SP2. I have
done this (sliipstreaming) once before on another son's computer when we
replaced an IDE with SATA and the original XP oem would not boot as it didnt
see the SATA. XP Sp2 slipstream solved that problem. He only had one hard
drive while this system had two. Could that have triggered the problem?
None of these are dell or gateway and both copies of XP were bought from the
same vendor (PcProgress) when I got the motherboards.

...thanks for reading this post..
 
B

Beemer Biker

Apart from the fact that you have just advised the world that your activities
are in fact contrary to the term of the OEM EULA what other concerns do you
have.

At http://www.microsoft.com/windowsxp/home/eula.mspx look at the paragraph
16. To keep this really simple, like a BAR joke, here it is:
"You may move the Software to a different Workstation Computer"

WTF do you think that means? The software stayed on the same workstation,
a defective motherboard was replaced. The software never left the hard
drive. I "moved" it to the same workstation.
Don't get too far ahead of yourself here.

Spend some thought next time before you post, not that a usenet post
requires thought.
If the XP install CD is faulty, then even if you slipstream SP2 into a new
set, then you are taking bad news forward and won't fix the problem.

Try a basic install from the original CD again.

WTF do you think I did 3 times already.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top