New
#300
Update:
If having issues installing Build 14986: Build 14986 - Error Code 80240031 - Microsoft Community
Update:
If having issues installing Build 14986: Build 14986 - Error Code 80240031 - Microsoft Community
Bwahahahahahahahahahahahah!
I got 2 VMs with the keys edited and one without - let's see what happens down the road....**NOTE** In this thread and on a few websites, there have been recommendations to edit your registry and set two regkeys to zero. While this may have helped for this particular build, it is important that you restore these regkeys back to their original value if you changed them. This will impact your ability to receive future updates. If you did not make any registry edits, no changes are required and you may skip this note.
It was bound to happen! From the solution to error code 80240031:
Actually, I'm in agreement with them. Once you've gotten your install.esd, I had been thinking the Registry should be changed back to its original state.**NOTE** In this thread and on a few websites, there have been recommendations to edit your registry and set two regkeys to zero. While this may have helped for this particular build, it is important that you restore these regkeys back to their original value if you changed them. This will impact your ability to receive future updates. If you did not make any registry edits, no changes are required and you may skip this note
But . . . with the next drop, am I correct in thinking we'd just do the Registry Hack again, etc.?
Odd. In both of my VMs created yesterday, I was able to get them activated using my old Win7 TechNet keys (I still have 3 or 4 more Win7 Pro keys to use, and I have a couple of Win7 Ultimate that I can reuse as they have not been installed on a machine in a long time).
But neither VM allows me to use a PIN. I did not know that was a limiting factor of VMs. Because it is a major PITA to have to enter my generated 20 character password every time to log into the VMs....
Hi,
Sure but even if it's not hard to do it would still involve the ADK running in a VM I guess.
BTW, there an IP ADK available too.
No idea what Kari's using...
O, any of you guys that caught the ESD file by using the registry hack received that error message ? I doubt it.
MS is just playing scarecrow, me thinks.
Cheers,