Hello,
I know this probably wasn't legal at all, but I had a friend who brought me an old HP Pavilion a6712f that his friend gave him. He doesn't got any money and is on disability. He asked if I could try to get 7 or 10 on it. It came with Vista. I said I'd try my best. The first thing I did was download a new version of the BIOS. I ran the SLIC Toolkit and saw it had v2.0 SLIC data in the BIOS.
V2.0 is for Vista
V2.1 is 7
V2.2 is 8/8.1
V3 I believe is for 10, but don't quote me on that. I believe they changed 10's activation a bit and if a system comes with 10 pre-installed, there's more than just SLIC data in the BIOS. I think a product key is in there as well, same with 8.
Anyway, the BIOS for the HP was in one of their sp<somenumber>.exe file. I ran that. First thing it said was close all programs before continuing. At that point, I went to the an elevated command prompt and typed:
I looked at the directory that was created last, which was around the time I ran the program and cd'd into it. Sure enough, it was the extracted contents of the sp file. I copied the contents to the c:\bios directory I made. The BIOS was called something like BEN5.43, I renamed it to BEN5.rom.
Being an AMI BIOS, I ran the AMI BIOS tool I have and injected the SLIC v2.1 data that I have for the same machine. I guess this machine came with 7 or Vista, so I was lucky and able to put the exact SLIC data in the BIOS that would have come with this machine if it came with 7.
I than copied the modified BIOS back to the temp directory and hit continued. It flashed the BIOS. I reran the SLICK Toolkit to verify that the SLIC data was in fact v2.1. It was. I went back to the elevated command prompt and used slmgr.vbs to install the pre-activation product key that HP uses. Then I used slmgr.vbs to install the matching certificate for the SLIC data that was in the BIOS. Is pre-activated Windows 7.
He really wanted Windows 10 though. So I download the Windows 10 ISO using the Microsoft Download Tool or whatever it's called and burned the ISO to disc. I went to the \sources\ directory on the disk and found the gatherosstate.exe file. I copied this to the Desktop and ran it. It created a file called GenuineTicket.xml. I copied this to a thumb drive.
Then, I installed Windows 10 64-bit Home. When it asked for a product key, I picked skip this part. I did a custom install and deleted all partitions on the hard drive and created new partitions. I installed 10. After it was installed, I went to an elevated command prompt window again. I popped in the thumb drive and copied the GenuineTicket.xml file to the c:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\ directory. On this computer, the thumb drive was drive letter e:, so I did it like this:
At this point, I rebooted the computer. I logged back into Windows 10 and ran the elevated command prompt again and typed:
This verified the copy of 10 was fully activated. It showed the same product key that people get when they did the free upgrade. I went into Windows, clicked on Start and then typed check activation status, just to be sure. Sure enough, fully activated.
I'm curious though, if I have to reinstall Windows 10, if I have the ethernet cable plugged in and install, will it automatically activate? Or will I have to copy that file again? Hopefully, it's registered on the Microsoft servers for life now. If my friend ever wants to go back to 7, no problem, because the BIOS still has the 7 SLIC data now.
I know people can use loaders, but I think that's a very wrong way of doing it. For one, with loaders, last time I checked, no GPT partitions. Secondly, you're using a third-party program that could be infected and that actually modifies your boot record. A loader does essentially the same thing. It looks for calls to the BIOS, so when a program asks for the SLIC data, instead of letting the program retrieve it from the BIOS, it intercepts and replaces it with 7 SLIC data, making the program think it got the real Windows 7 SLIC data from the BIOS. Those loaders use the same SLIC data. So if you have an HP, but the loader is using SLIC data from a Dell, that could be detected. My way, there's no way to tell the computer didn't come with 7.
Just thought I'd share. If anyone wanted to give it a shot, I could share the programs I have and the knowledge on how to do it and walk you through it.
I'm pretty certain it's illegal because you're not paying for the OS, but if you're okay with breaking the law, eh.
I know this probably wasn't legal at all, but I had a friend who brought me an old HP Pavilion a6712f that his friend gave him. He doesn't got any money and is on disability. He asked if I could try to get 7 or 10 on it. It came with Vista. I said I'd try my best. The first thing I did was download a new version of the BIOS. I ran the SLIC Toolkit and saw it had v2.0 SLIC data in the BIOS.
V2.0 is for Vista
V2.1 is 7
V2.2 is 8/8.1
V3 I believe is for 10, but don't quote me on that. I believe they changed 10's activation a bit and if a system comes with 10 pre-installed, there's more than just SLIC data in the BIOS. I think a product key is in there as well, same with 8.
Anyway, the BIOS for the HP was in one of their sp<somenumber>.exe file. I ran that. First thing it said was close all programs before continuing. At that point, I went to the an elevated command prompt and typed:
Code:
cd %temp% dir /a /od
Being an AMI BIOS, I ran the AMI BIOS tool I have and injected the SLIC v2.1 data that I have for the same machine. I guess this machine came with 7 or Vista, so I was lucky and able to put the exact SLIC data in the BIOS that would have come with this machine if it came with 7.
I than copied the modified BIOS back to the temp directory and hit continued. It flashed the BIOS. I reran the SLICK Toolkit to verify that the SLIC data was in fact v2.1. It was. I went back to the elevated command prompt and used slmgr.vbs to install the pre-activation product key that HP uses. Then I used slmgr.vbs to install the matching certificate for the SLIC data that was in the BIOS. Is pre-activated Windows 7.
He really wanted Windows 10 though. So I download the Windows 10 ISO using the Microsoft Download Tool or whatever it's called and burned the ISO to disc. I went to the \sources\ directory on the disk and found the gatherosstate.exe file. I copied this to the Desktop and ran it. It created a file called GenuineTicket.xml. I copied this to a thumb drive.
Then, I installed Windows 10 64-bit Home. When it asked for a product key, I picked skip this part. I did a custom install and deleted all partitions on the hard drive and created new partitions. I installed 10. After it was installed, I went to an elevated command prompt window again. I popped in the thumb drive and copied the GenuineTicket.xml file to the c:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\ directory. On this computer, the thumb drive was drive letter e:, so I did it like this:
Code:
cd \ProgramData\Microsoft\Windows\ClipSVC\GenuineTicket\ e: copy GenuineTicket.xml c:
Code:
slmgr.vbs /dli
I'm curious though, if I have to reinstall Windows 10, if I have the ethernet cable plugged in and install, will it automatically activate? Or will I have to copy that file again? Hopefully, it's registered on the Microsoft servers for life now. If my friend ever wants to go back to 7, no problem, because the BIOS still has the 7 SLIC data now.
I know people can use loaders, but I think that's a very wrong way of doing it. For one, with loaders, last time I checked, no GPT partitions. Secondly, you're using a third-party program that could be infected and that actually modifies your boot record. A loader does essentially the same thing. It looks for calls to the BIOS, so when a program asks for the SLIC data, instead of letting the program retrieve it from the BIOS, it intercepts and replaces it with 7 SLIC data, making the program think it got the real Windows 7 SLIC data from the BIOS. Those loaders use the same SLIC data. So if you have an HP, but the loader is using SLIC data from a Dell, that could be detected. My way, there's no way to tell the computer didn't come with 7.
Just thought I'd share. If anyone wanted to give it a shot, I could share the programs I have and the knowledge on how to do it and walk you through it.
I'm pretty certain it's illegal because you're not paying for the OS, but if you're okay with breaking the law, eh.
Comment