New
#1
Windows not genuine, error 0xC004F057 after migrating OS to SSD
Hey everyone,
I recently bought a Samsung 850 EVO SSD (500GB) to upgrade my 2 year-old machine with. I've tried to migrate Windows to the SSD ever since I installed, first by hand (messing with cloning and EasyBCD), but when that didn't work out, I bought a copy of "Paragon Migrate OS to SSD". This worked like a charm, and I could boot into my SSD. However, booting into Windows 7 on the SSD gives me the old familiar black background, and the pop-up "Windows 7 Home Premium could not be activated with the submitted product key" [paraphrased, as it's a translation]. I get the option to submit a different product key, and when I entered mine, it told me that "a problem has occured during activation" with the errorcode 0x00C4E003. Googling this error tells me that this code means the product key is already in use.
Running MDADiag gives me the following report:
Apologies for the Dutch report. The License entry reads "gemeld dat Windows niet legitiem is", which roughly means "reported that Windows is not legitimate/genuine".Code:Diagnostic Report (1.9.0027.0): ----------------------------------------- Windows Validation Data--> Validation Code: 50 Cached Online Validation Code: 0x0 Windows Product Key: *****-*****-WJ2H8-R6B6D-7QJB7 Windows Product Key Hash: ckKNc+BBPDWmo1LUlOkraNjlQ34= Windows Product ID: 00359-OEM-8992687-00006 Windows Product ID Type: 2 Windows License Type: OEM SLP Windows OS version: 6.1.7601.2.00010300.1.0.003 ID: {12079FB0-5611-4405-A401-0E6C6F9027D6}(3) Is Admin: Yes TestCab: 0x0 LegitcheckControl ActiveX: N/A, hr = 0x80070002 Signed By: N/A, hr = 0x80070002 Product Name: Windows 7 Home Premium Architecture: 0x00000009 Build lab: 7601.win7sp1_ldr.160408-2045 TTS Error: Validation Diagnostic: Resolution Status: N/A Vista WgaER Data--> ThreatID(s): N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 Windows XP Notifications Data--> Cached Result: N/A, hr = 0x80070002 File Exists: No Version: N/A, hr = 0x80070002 WgaTray.exe Signed By: N/A, hr = 0x80070002 WgaLogon.dll Signed By: N/A, hr = 0x80070002 OGA Notifications Data--> Cached Result: N/A, hr = 0x80070002 Version: N/A, hr = 0x80070002 OGAExec.exe Signed By: N/A, hr = 0x80070002 OGAAddin.dll Signed By: N/A, hr = 0x80070002 OGA Data--> Office Status: 109 N/A OGA Version: N/A, 0x80070002 Signed By: N/A, hr = 0x80070002 Office Diagnostics: 025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3 Browser Data--> Proxy settings: N/A User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32) Default Browser: C:\Users\MY PC\AppData\Local\Google\Chrome\Application\chrome.exe Download signed ActiveX controls: Prompt Download unsigned ActiveX controls: Disabled Run ActiveX controls and plug-ins: Allowed Initialize and script ActiveX controls not marked as safe: Disabled Allow scripting of Internet Explorer Webbrowser control: Disabled Active scripting: Allowed Script ActiveX controls marked as safe for scripting: Allowed File Scan Data--> Other data--> Office Details: <GenuineResults><MachineData><UGUID>{12079FB0-5611-4405-A401-0E6C6F9027D6}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010300.1.0.003</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-7QJB7</PKey><PID>00359-OEM-8992687-00006</PID><PIDType>2</PIDType><SID>S-1-5-21-2870121302-1064334643-1053606723</SID><SYSTEM><Manufacturer>To Be Filled By O.E.M.</Manufacturer><Model>To Be Filled By O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>P1.50</Version><SMBIOSVersion major="2" minor="7"/><Date>20131002000000.000000+000</Date></BIOS><HWID>C8FA3007018400F2</HWID><UserLCID>0413</UserLCID><SystemLCID>0413</SystemLCID><TimeZone>West-Europa (standaardtijd)(GMT+01:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> Spsys.log Content: 0x80070002 Licensing Data--> Versie van Software Licensing-service: 6.1.7601.17514 Naam: Windows(R) 7, HomePremium edition Beschrijving: Windows Operating System - Windows(R) 7, OEM_SLP channel Activerings-id: d2c04e90-c3dd-4260-b0f3-f845f5d27d64 Toepassings-id55c92734-d682-4d71-983e-d6ec3f16059f Uitgebreide PID: 00359-00178-926-800006-02-1043-7601.0000-2012016 Installatie-id011831873303341716114434103453295683977991772553447582 URL van processorcertificaat: http://go.microsoft.com/fwlink/?LinkID=88338 URL van computercertificaat: http://go.microsoft.com/fwlink/?LinkID=88339 URL van gebruikte licentie: http://go.microsoft.com/fwlink/?LinkID=88341 URL van productcodecertificaat: http://go.microsoft.com/fwlink/?LinkID=88340 Gedeeltelijke productcode: 7QJB7 Licentiestatus: gemeld dat Windows niet legitiem is Reden van melding: 0xC004F057. Resterend aantal nieuwe Windows-activeringen: 3 Vertrouwde tijd: 21-7-2016 14:37:58 Windows Activation Technologies--> HrOffline: 0x00000000 HrOnline: 0xC004C533 HealthStatus: 0x0000000000000000 Event Time Stamp: 7:21:2016 13:40 ActiveX: Registered, Version: 7.1.7600.16395 Admin Service: Registered, Version: 7.1.7600.16395 HealthStatus Bitmask Output: HWID Data--> HWID Hash Current: NgAAAAIAAwABAAEAAAAEAAAAAQABAAEAln0mUXqHdxZsfhpIEDMwQI7jCkPogqYt5/3yc251 OEM Activation 1.0 Data--> N/A OEM Activation 2.0 Data--> BIOS valid for OA 2.0: yes, but no SLIC table Windows marker version: N/A OEMID and OEMTableID Consistent: N/A BIOS Information: ACPI Table Name OEMID Value OEMTableID Value APIC ALASKA A M I FACP ALASKA A M I HPET ALASKA A M I MCFG ALASKA A M I FPDT ALASKA A M I AAFT ALASKA OEMAAFT SSDT AMD POWERNOW BGRT ALASKA A M I
I've done some previous research on these forums, and I found that this entry is not as it should be [Edit: at least, I think so?]:I have, however, not touched my motherboard at all, aside from plugging in the SSD. Do I need to connect my SSD to the motherboard using the SATA port my old HDD was connected to (and still is)?Code:BIOS valid for OA 2.0: yes, but no SLIC table
Any other ideas on what I could do? Thank you in advance.
Last edited by Maroon; 21 Jul 2016 at 09:01.