Whether you like it or not....it is a false alarm...there are no trojans in it....sorry to see your attitude in the way that you came off here but you are dead wrong about trojans in the KMS Activators.
No one here said you needed to do anything.....this is my last time to say anything but you are dead wrong and your McAfee is not the best of the antivirus programs that are available....sorry to burst your bubble but you need to learn more about your own antivirus program before accusing anyone on this forum of purposely uploading trojans to a computer...and if you had done your research you will find that McAfee, AVG and Kaspersky are the worst of the virus programs that are out there....the only one worth its salt is NOD32 and I would say that Microsoft's Security Essentials is not a bad one in itself and it is free to all authentic windows users. So, be careful of what or who you accuse of maliciously harming anyone's computer.
Just one remark. In step 2 : "Step 2:Now run the installer as administrator,wait till the yellow screen appears asking for Product Key,now take start menu and type "%temp%" without ",you may see a folder named "OWP6FC3.tmp" (may differ),now copy the entire folder to C:\ or other(NOTE: you should not close the installer till you finish copying)" It's ok but you can directly extract the content with this command. Code: filename.exe /extract:{path to extract} example: en_office_professional_plus_2010_x86_515486.exe /extract:C:\Office2010
Where is the connection with the subject of post : How to convert Office 2010 Retail Installation to Office 2010 VL ??
There are now "Combo" or "Dual" versions of Project and Visio released on MSDN. These are retail license iso's that contain both x86 and x64 in the same image. Can the "change folders" method described in this thread be used to convert these Combo editions to Volume License?
Well, As everyone said befor the only difference between Retail and VL version is between "ProPlusr.WW" and "ProPlus.WW" folders. But I was not satisfied yet and I started to conduct some experiments with Microsoft Office 2010 files. here are some results: (I am still conducting more and more experiments) Files that are the same: Name Size CRC ----------------------------------------------------------------------------------------------- OWOW64WW.cab 23,865,400 EF914B32 osetup.dll 5,789,544 35109001 Office64WW.msi 3,025,408 DE63CE01 PidGenX.dll 1,248,016 03D9EF29 pkeyconfig-office.xrm-ms 715,834 732A7FD0 ose.exe 149,352 8D3DAEF9 Office64WW.xml 4,685 A8CD6917 ----------------------------------------------------------------------------------------------- Files that are the same size but have differant CRC values: Name Size CRC ------------------------------------------------------------------ ProPrWW2.cab 197,934,115 35566CBA ProPrWW.cab 149,278,843 BF5CC15C *** ProPsWW2.cab 197,934,115 D654DACB ProPsWW.cab 149,278,843 4F696588 ----------------------------------------------------------------------- The rest of the files are differant both in size and CRC. Then I felt like comparing files in the second group to see why CRC's are different. I saw that ONLY the last 6KB of these files are different. After a little bit of playing around with files I found that only their Digital Signature is different. If you are familiar with CAB file format you know that offset 08-0B stores the filesize. If you take a look at them you see: 149,272,875 for ProPsWW2.cab and ProPrWW2.cab And: 197,928,147 for ProPsWW.cab and ProPrWW.cab If you subtracted the real filesize with this filesizes, you would find: 197,934,115-197,928,147 = 5,968 149,278,843-149,272,875 = 5,968 This is digital signature that has been addede to these files. Next, I removed digital signature from both "ProPsWW.cab and ProPrWW.cab" pair and "ProPsWW2.cab and ProPrWW2.cab" pair. Guess what? The new files are identical. I am currently still working on this thing but the files inside MSI are really interesting. I am working on them at the moment. Will let you know about new things soon. ********** Update: This path is able to change the two above files from Retail to VL for you. This is a very early stage patch. so I am gonna change it as I am finding new things.
Well that's interesting, what about the files that also differ in size? Probably just 1 file inside the cab?
Difference between config.xml files of Retail and VL The only difference between config.xml of Retail and VL is in line 1: Retail: <Configuration Product="ProPlusr"> VL: <Configuration Product="ProPlus"> As you see, Retail one has 1 more character and hence the difference in size and CRC: Retail: Size: 914 byte CRC: 97AAE097 VL: Size: 913 CRC: CD848B7C After removing "r" from Retail: Size: 913 CRC: CD848B7C