![]() So if you have an HP, but the loader is using SLIC data from a Dell, that could be detected. 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. A loader does essentially the same thing. Secondly, you're using a third-party program that could be infected and that actually modifies your boot record. For one, with loaders, last time I checked, no GPT partitions. I know people can use loaders, but I think that's a very wrong way of doing it. If my friend ever wants to go back to 7, no problem, because the BIOS still has the 7 SLIC data now. 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. I went into Windows, clicked on Start and then typed check activation status, just to be sure. ![]() It showed the same product key that people get when they did the free upgrade. On this computer, the thumb drive was drive letter e:, so I did it like this:Ĭode: slmgr.vbs /dliThis verified the copy of 10 was fully activated. I popped in the thumb drive and copied the GenuineTicket.xml file to the c:\ProgramData\Microsoft\Windows\ClipSVC\GenuineTi cket\ directory. After it was installed, I went to an elevated command prompt window again. I did a custom install and deleted all partitions on the hard drive and created new partitions. When it asked for a product key, I picked skip this part. Then, I installed Windows 10 64-bit Home. It created a file called GenuineTicket.xml. I went to the \sources\ directory on the disk and found the gatherosstate.exe file. So I download the Windows 10 ISO using the Microsoft Download Tool or whatever it's called and burned the ISO to disc. Then I used slmgr.vbs to install the matching certificate for the SLIC data that was in the BIOS. I went back to the elevated command prompt and used slmgr.vbs to install the pre-activation product key that HP uses. ![]() I reran the SLICK Toolkit to verify that the SLIC data was in fact v2.1. I than copied the modified BIOS back to the temp directory and hit continued. 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. ![]() The BIOS was called something like BEN5.43, I renamed it to BEN5.rom.īeing 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 copied the contents to the c:\bios directory I made. Sure enough, it was the extracted contents of the sp file. Dir /a /odI looked at the directory that was created last, which was around the time I ran the program and cd'd into it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |