Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Window 7 Enterpise Activation Error RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    We have an issue with a single Acer Extensa 5620Z laptop which we've imaged with Windows 7 Enterprise (fully licensed VLK). When attempting to activate it gives an error message (code 0xc004f035) "The software Licensing Service reported that the computer could not be activated with a Volume license product key. Volume licensed systems require upgrading from a qualified operating system. Please contact your system administrator or use a different type of key." The laptop was originally supplied with Vista Business on it (also have a Vista Business COA on it). We're tried updating the BIOS but had no luck, and have checked for updates and all are installed. Log from mgatool:

    Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->

Validation Code: 50
Cached Online Validation Code: N/A, hr = 0xc004f012
Windows Product Key: *****-*****-2VJC9-XBBR8-HVTHH
Windows Product Key Hash: k/l/EMDQdwK9OvdCkPtHG1YdosE=
Windows Product ID: 00392-918-5000002-85442
Windows Product ID Type: 1
Windows License Type: KMS Client
Windows OS version: 6.1.7600.2.00010100.0.0.004
ID: {8299A0E2-F3C3-44F1-B471-E2E4EBFF7979}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: N/A, hr = 0x80070002
Signed By: N/A, hr = 0x80070002
Product Name: Windows 7 Enterprise
Architecture: 0x00000000
Build lab: 7600.win7_gdr.100618-1621
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: 2.0.48.0
OGAExec.exe Signed By: N/A, hr = 0x800b010e
OGAAddin.dll Signed By: N/A, hr = 0x800b010e

OGA Data-->
Office Status: 100 Genuine
Microsoft Office Enterprise 2007 - 100 Genuine
OGA Version: Registered, 2.0.48.0
Signed By: N/A, hr = 0x800b010e
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:\Program Files\Internet Explorer\iexplore.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-->
File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\wat\npwatweb.dll[7.1.7600.16395], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\wat\watweb.dll[7.1.7600.16395], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b010e
File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b010e

Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{8299A0E2-F3C3-44F1-B471-E2E4EBFF7979}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.004</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-HVTHH</PKey><PID>00392-918-5000002-85442</PID><PIDType>1</PIDType><SID>S-1-5-21-2682788629-3514282767-2443464472</SID><SYSTEM><Manufacturer>Acer      </Manufacturer><Model>Extensa 5620          </Model></SYSTEM><BIOS><Manufacturer>Phoenix Technologies LTD</Manufacturer><Version>V1.35     </Version><SMBIOSVersion major="2" minor="4"/><Date>20080703000000.000000+000</Date></BIOS><HWID>13BB3607018400FA</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>1</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>ACRSYS</OEMID><OEMTableID>ACRPRDCT</OEMTableID></OEM><GANotification><File Name="OGAAddin.dll" Version="2.0.48.0"/></GANotification></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>A02AAB743F7D8A</Val><Hash>M3gerk9vMjJTFXEpFr5wmREv1yc=</Hash><Pid>89388-709-5015872-65791</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults> 

Spsys.log Content: 0x80070002

Licensing Data-->
Software licensing service version: 6.1.7600.16385

Name: Windows(R) 7, Enterprise edition
Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
Activation ID: ae2ee509-1b34-41c0-acb7-6d4650168915
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00392-00170-918-500000-03-2057-7600.0000-0492010
Installation ID: 014411074464169610734612971532042244110372723380025152
Partial Product Key: HVTHH
License Status: Notification
Notification Reason: 0xC004F035.
Remaining Windows rearm count: 0
Trusted time: 07/02/2011 13:01:19
Please use slmgr.vbs /ato to activate and update KMS client information in order to update values.

Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: N/A
HealthStatus: 0x0000000000000000
Event Time Stamp: N/A
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:


HWID Data-->
HWID Hash Current: OAAAAAEABAABAAMAAAABAAAAAwABAAEAJJT0jm5sRoP8kFQ5Rrc8YSxRUp3igkCZasTYRTQ9KoU=

OEM Activation 1.0 Data-->
N/A

OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no Windows marker
Windows marker version: N/A
OEMID and OEMTableID Consistent: yes
BIOS Information: 
 ACPI Table Name	OEMID Value	OEMTableID Value
 APIC			PTLTD 			 APIC 
 FACP			INTEL 		CRESTLNE
 HPET			INTEL 		CRESTLNE
 BOOT			PTLTD 		$SBFTBL$
 MCFG			INTEL 		CRESTLNE
 TCPA			Intel 		 CRESTLN
 TMOR			PTLTD 		    
 SLIC			ACRSYS		ACRPRDCT
 ASF!			OEMID 		OEMTBL 
 SSDT			SataRe		SataPri
 SSDT			SataRe		SataPri
 SSDT			SataRe		SataPri
 SSDT			SataRe		SataPri
 SSDT			SataRe		SataPri
 SSDT			SataRe		SataPri

    Considering the bits from the above - I've run sfc /scannow to try to resolve the file mismatch issues - it finds no issues in verification, I've also chkdsk'd the drive. We've put contact into Acer (and are waiting to hear back). But if anyone has any ideas, that would be great.

    Will

    PS To clarify we are fully licensed with a Microsoft VL agreement (with SA) for Windows 7 Enterprise, all our laptops (we have about 40 more of the same model) were purchased with OEM licenses on them and we already have a significant number which have successfully activated through the route we are trying.

    Monday, February 7, 2011 1:56 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Willottctk,

     

      There appears to be two issues at play here.

    1) OEM Bios Flag: PCs that are built by a Large Manufacturer that come with Windows Pre-installed use an activation process that involves checking for a OEM Bios Flag. Volume License use the same OEM Bios Flag to determine if it is being installed on a PC that originally came with a "qualified operating system".

     Now even though your laptop was originally supplied with Vista Business (i.e. a qualified operating system) and would have had a Bios that contains an OEM Bios Flag,but for unknown reasons, that Bios Flag is not present. As you can see from the Diagnostic Report line: "BIOS valid for OA 2.0: yes, but no Windows marker "

    Resolution:

      a) Re-flashing the Bios was the right thing to do, however, you need to ensure the Bios is specifically for that model PC. That should ensure that it contains a Bios Flag.  (May also contact the PC's manufacturer and they should be able to direct you to the proper BIOS update)

      b) I am not 100% positive (I don't handle VLK issue very much) but I seem to me that a Volume MAK key does not have the Bios Flag requirement. I would recommend double checking that information in either the MSDN or Technet forums:

    Technet: http://social.technet.microsoft.com/Forums/en-us/categories

    MSDN: http://social.msdn.microsoft.com/Forums/en-US/categories/

     

    2) File Mismatch:

    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\wat\watweb.dll[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b010e

      First off, the files I have Highlighted can be ignored, they are not causing an issue.  Those are Optional files that are only installed if you decide to Validate your Windows as Genuine at http://microsoft.com/genuine/validate .  I do recommend that you do go to that link and Validate as it may help the current issue.  And even if it doesn't, it will at least be convenient to not have those file muddying up the File Mismatch list.

     The reason those other files are listed as Mismatch is that the Hashs for those files do not match the Hashs listed in System Catalog for those files.

     You mentioned that you already tried the sfc /scannow command. With this type of issue, normal it would have either told you it found bad files and repaired them or that it found bad files but was unable to repair them.  But, if I understood your post, it said it found no bad files at all.  This is unusual and am not sure what to make of it.

     

    Possible Resolution:

      a) First try a System Restore to a point before the issue was first seen

      b) Next, if you haven't done so already, go to the URL I listed above and run Validation. Once done, try the sfc /scannow command once again. 

      c) If you have another PC with a known-good install of Windows 7 Enterprise, then find the files, on the Mismatch file list, and copy them over to replace the bad ones.

      There is also a way to extract the files from a Windows install disk but I don't have the exact instructions on how to do that but if you know how, that may also be an option for you.

      d) As the last resort, Reinstall Windows.

     

    I hope this was helpful,

     

    Darin MS
    • Proposed as answer by Darin Smith MS Wednesday, February 9, 2011 12:54 AM
    • Marked as answer by Darin Smith MS Friday, February 11, 2011 10:04 PM
    Wednesday, February 9, 2011 12:52 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello Willottctk,

     

      There appears to be two issues at play here.

    1) OEM Bios Flag: PCs that are built by a Large Manufacturer that come with Windows Pre-installed use an activation process that involves checking for a OEM Bios Flag. Volume License use the same OEM Bios Flag to determine if it is being installed on a PC that originally came with a "qualified operating system".

     Now even though your laptop was originally supplied with Vista Business (i.e. a qualified operating system) and would have had a Bios that contains an OEM Bios Flag,but for unknown reasons, that Bios Flag is not present. As you can see from the Diagnostic Report line: "BIOS valid for OA 2.0: yes, but no Windows marker "

    Resolution:

      a) Re-flashing the Bios was the right thing to do, however, you need to ensure the Bios is specifically for that model PC. That should ensure that it contains a Bios Flag.  (May also contact the PC's manufacturer and they should be able to direct you to the proper BIOS update)

      b) I am not 100% positive (I don't handle VLK issue very much) but I seem to me that a Volume MAK key does not have the Bios Flag requirement. I would recommend double checking that information in either the MSDN or Technet forums:

    Technet: http://social.technet.microsoft.com/Forums/en-us/categories

    MSDN: http://social.msdn.microsoft.com/Forums/en-US/categories/

     

    2) File Mismatch:

    File Mismatch: C:\Windows\system32\wat\watadminsvc.exe[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\wat\watux.exe[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\wat\watweb.dll[7.1.7600.16395], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppobjs.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppc.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppcext.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppwinob.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\slc.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\slcext.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppuinotify.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\slui.exe[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppcomapi.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppcommdlg.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\sppsvc.exe[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\drivers\spsys.sys[6.1.7127.0], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\drivers\spldr.sys[6.1.7127.0], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\systemcpl.dll[6.1.7600.16385], Hr = 0x800b010e
    File Mismatch: C:\Windows\system32\user32.dll[6.1.7600.16385], Hr = 0x800b010e

      First off, the files I have Highlighted can be ignored, they are not causing an issue.  Those are Optional files that are only installed if you decide to Validate your Windows as Genuine at http://microsoft.com/genuine/validate .  I do recommend that you do go to that link and Validate as it may help the current issue.  And even if it doesn't, it will at least be convenient to not have those file muddying up the File Mismatch list.

     The reason those other files are listed as Mismatch is that the Hashs for those files do not match the Hashs listed in System Catalog for those files.

     You mentioned that you already tried the sfc /scannow command. With this type of issue, normal it would have either told you it found bad files and repaired them or that it found bad files but was unable to repair them.  But, if I understood your post, it said it found no bad files at all.  This is unusual and am not sure what to make of it.

     

    Possible Resolution:

      a) First try a System Restore to a point before the issue was first seen

      b) Next, if you haven't done so already, go to the URL I listed above and run Validation. Once done, try the sfc /scannow command once again. 

      c) If you have another PC with a known-good install of Windows 7 Enterprise, then find the files, on the Mismatch file list, and copy them over to replace the bad ones.

      There is also a way to extract the files from a Windows install disk but I don't have the exact instructions on how to do that but if you know how, that may also be an option for you.

      d) As the last resort, Reinstall Windows.

     

    I hope this was helpful,

     

    Darin MS
    • Proposed as answer by Darin Smith MS Wednesday, February 9, 2011 12:54 AM
    • Marked as answer by Darin Smith MS Friday, February 11, 2011 10:04 PM
    Wednesday, February 9, 2011 12:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Darin,

    Thanks for the response. We'll try the MAK today (I had a feeling that would work, just wanted to see if there were avenues to get KMS working). I've just confirmed the bios version used to reflash, and we're still awaiting a response from Acer support.

    If that works, I'm probably not going to worry too much about the file mismatches - too many other jobs on presently!

    Cheers

    Will

    Wednesday, February 9, 2011 8:46 AM