none
(SOLVED) WINDOWS 7 SP1 ACTIVATION ERROR 0X8007007B

    Question

  • 022611 I downloaded and successfully installed Windows 7 SP1 for my 32bit Windows 7 Professional, installed on a HP 2710p 1.2 Core 2 Duo Tablet Computer with 3GB RAM and 80GB HD.  030111 the system attempted a Windows Activation which failed with a 0x8007007B error "the filename, directory name or volume label syntax is incorrect."  I have 25 days before Windows makes my life really miserable.

      I have tried creating a new administrative permissions user and ran the activation with the same error.  I have looked through the forums on Microsoft Support, here and googled this as well.  The closest thing I found is here for installing SP1.  I got it installed, but it reset my activation and I am stuck.  Most articles for the error code are for backup or restore operation.  I suppose that could be involved as the system creates a restore point and does backup files during install of the SP.  Somehow I wonder how this is related to activation.  I also downloaded MGA tool and from what I can tell the license indicates it was legit awaiting activation.  So no errors there from what I can tell.  SFC /scannow did not find any integrity violations.

        What do I need to do to clear this error and reactivate windows after SP1 install?  I really appreciate your time and effort to assist me to solve my issue here.  Thank you.

    Respectfully,

    Dave

    • Edited by DaveRTech Wednesday, March 02, 2011 8:39 PM Spelling
    Wednesday, March 02, 2011 8:34 PM

Answers

  • OK Sportsfans!!!  I figured it out...I remembered something I read somewhere in Googleland that entering Product Keys and Activations need to match the software installed.  This is mostly important when for some reason you need to reinstall Windows from the git go.  You need to use a Product Key that matches the software you are going to put on the computer new.

    In this case I did not realize the used computer I bought was not activated.  In the course of getting it up to speed with applications and updates I put SP1 on it from Windows Update.  Three days later, caused by some process, SP1 and/or KB 971033 (MS anti-pirating spyware) the system attempted an automatic activation.  It failed as noted above with error code 0x8007007B.  I further narrowed the issue to File Mismatches as detailed above with the MGA Tool.  I tried to use Add/Remove programs to remove the KB971033 update and reinstall it.  That did not work either (took me 2 times to do this for some reason) the activation still failed with the same error code.  There were no file issues SFC /SCANNOW and chkdsk did not find anything to fix.  Sorry Andre I did not try to replace the files as above with expand.exe as it nagged at me that there was something else wrong with the files and they were not corrupt.

    The issue?  The computer was loaded with Windows 7 Professional 32bit.  Since I loaded SP1 on it, not knowing the OS was not yet activated.  The system tried to activate Windows 7 Professional 32bit SP1 with a Windows 7 Professional 32bit Product Key.  No WONDER I got the file mismatch errors...the OS install did not match the Product Key.  I unistalled SP1 and activated without issue, problem solved...

    I really appreciate your assistance Andre.  It was really nice to know you were there looking out for me.  Hopefully my trials and tribulatios over the past couple of days will save others from mighty struggles...make certain your OS is activated before installing Service Packs!

    • Marked as answer by DaveRTech Thursday, March 03, 2011 9:42 PM
    Thursday, March 03, 2011 9:41 PM

All replies

  • Andre!

          Greetings!  Thank you for your reply and I will do that, but first understand I already did install SP1 successfully with absolutely no issues at all...The issue here is the Windows activation will not run and gives the error you posted the details for.  I will wait for your reply to this clarification so as not to clutter up this thread and waste your time chasing something that is not the issue.  I hope that makes things clearer.

       Also after doing more investigating about the MGA Tool, I think Windows is doing an initial activation not a reactivation, if I read the tool results correctly as I initially thought.  I just purchased this computer used and I thought Windows was already activated as I did not have to go through the initial set up for a fresh install out of the box.  I downloaded SP1 though Windows Update as part of installing things and I associated that act as causing the reactivation as I read in several posts that SP1 was causing issues with activation due to MS working to stop pirated versions and forcing a reactivation.  I posted the MGA Tool results below if that helps.

    Respectfully,

    Dave

     

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

    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
    Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
    Windows Product ID: 00371-868-0000007-85818
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {0FE36D4E-78B8-4ABE-8779-6541EBCEF2A7}(1)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000000
    Build lab: 7601.win7sp1_rtm.101119-1850
    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: 100 Genuine
    Microsoft Office Professional Plus 2007 - 100 Genuine
    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_E2AD56EA-765-d003_E2AD56EA-766-0_E2AD56EA-134-80004005

    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[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\npwatweb.dll[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watux.exe[Hr = 0x80070003]
    File Mismatch: C:\Windows\system32\wat\watweb.dll[Hr = 0x80070003]

    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{0FE36D4E-78B8-4ABE-8779-6541EBCEF2A7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-GPDD4</PKey><PID>00371-868-0000007-85818</PID><PIDType>1</PIDType><SID>S-1-5-21-4137160747-2616734258-1423646734</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq 2710p</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68MOU Ver. F.12</Version><SMBIOSVersion major="2" minor="4"/><Date>20080618000000.000000+000</Date></BIOS><HWID>6C733F07018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Plus 2007</Name><Ver>12</Ver><Val>BA8F712C7F40586</Val><Hash>HIKomUf7tgzGuwKk7g8+R4oY9tE=</Hash><Pid>89409-707-1593755-65111</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"/></Applications></Office></Software></GenuineResults> 

    Spsys.log Content: 0x80070002

    Licensing Data-->
    Software licensing service version: 6.1.7601.17514

    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-1033-7600.0000-0522011
    Installation ID: 003992174465220882601551749404997171454752847932405611
    Partial Product Key: GPDD4
    License Status: Initial grace period
    Time remaining: 36480 minute(s) (25 day(s))
    Remaining Windows rearm count: 4
    Trusted time: 3/2/2011 2:37:16 PM
    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: Not Registered - 0x80040154
    Admin Service: Not Registered - 0x80040154
    HealthStatus Bitmask Output:


    HWID Data-->
    HWID Hash Current: MgAAAAEAAwABAAIAAAABAAAAAgABAAEAeqjQ2MuRLmL63EaDVsyG9hxqqLQkfj4fKoU=

    OEM Activation 1.0 Data-->
    N/A

    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x0
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   HP      30C8   
      FACP   HP      30C8   
      HPET   HP      30C8   
      MCFG   HP      30C8   
      SLIC   HPQOEM  SLIC-MPC
      TCPA   HP      30C8   
      SSDT   HP      HPQPAT
      SSDT   HP      HPQPAT
      SSDT   HP      HPQPAT
      SSDT   HP      HPQPAT

     

     

    Wednesday, March 02, 2011 11:05 PM
  • OK I focused on the File Mismatches in the MGA Tool log and found another group of threads that advised to go to
    http://www.microsoft.com/genuine/validate  I successfully went through the process and was welcomed to Windows with a genuine copy of the Windows 7 Pro OS.  I reran the MGA Tool and here is the resultant log below.  Hopefully this will mean something to someone to assist me solve this issue...It looks the same to me and the activation wizard still goves the same error code 0x8007007B...Oh well...
    Respectfully,
    Dave
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    Validation Code: 0
    Cached Online Validation Code: 0x0
    Windows Product Key: *****-*****-J8D7P-XQJJ2-GPDD4
    Windows Product Key Hash: xgsndMkYdJsYmUng0qIJ/thx+HI=
    Windows Product ID: 00371-868-0000007-85818
    Windows Product ID Type: 1
    Windows License Type: KMS Client
    Windows OS version: 6.1.7601.2.00010100.1.0.048
    ID: {0FE36D4E-78B8-4ABE-8779-6541EBCEF2A7}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Professional
    Architecture: 0x00000000
    Build lab: 7601.win7sp1_rtm.101119-1850
    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: 100 Genuine
    Microsoft Office Professional Plus 2007 - 100 Genuine
    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:\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-->
    Other data-->
    Office Details: <GenuineResults><MachineData><UGUID>{0FE36D4E-78B8-4ABE-8779-6541EBCEF2A7}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.048</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-GPDD4</PKey><PID>00371-868-0000007-85818</PID><PIDType>1</PIDType><SID>S-1-5-21-4137160747-2616734258-1423646734</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP Compaq 2710p</Model></SYSTEM><BIOS><Manufacturer>Hewlett-Packard</Manufacturer><Version>68MOU Ver. F.12</Version><SMBIOSVersion major="2" minor="4"/><Date>20080618000000.000000+000</Date></BIOS><HWID>6C733F07018400FA</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>Eastern Standard Time(GMT-05:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>HPQOEM</OEMID><OEMTableID>SLIC-MPC</OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0011-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Professional Plus 2007</Name><Ver>12</Ver><Val>BA8F712C7F40586</Val><Hash>HIKomUf7tgzGuwKk7g8+R4oY9tE=</Hash><Pid>89409-707-1593755-65111</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"/></Applications></Office></Software></GenuineResults> 
    Spsys.log Content: 0x80070002
    Licensing Data-->
    Software licensing service version: 6.1.7601.17514
    Name: Windows(R) 7, Professional edition
    Description: Windows Operating System - Windows(R) 7, VOLUME_KMSCLIENT channel
    Activation ID: b92e9980-b9d5-4821-9c94-140f632f6312
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00371-00170-868-000000-03-1033-7600.0000-0522011
    Installation ID: 003992174465220882601551749404997171454752847932405611
    Partial Product Key: GPDD4
    License Status: Initial grace period
    Time remaining: 36180 minute(s) (25 day(s))
    Remaining Windows rearm count: 4
    Trusted time: 3/2/2011 8:10:04 PM
    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: MgAAAAEAAwABAAIAAAABAAAAAgABAAEAeqjQ2MuRLmL63EaDVsyG9hxqqLQkfj4fKoU=
    OEM Activation 1.0 Data-->
    N/A
    OEM Activation 2.0 Data-->
    BIOS valid for OA 2.0: yes
    Windows marker version: 0x0
    OEMID and OEMTableID Consistent: yes
    BIOS Information:
      ACPI Table Name OEMID Value OEMTableID Value
      APIC   HP      30C8   
      FACP   HP      30C8   
      HPET   HP      30C8   
      MCFG   HP      30C8   
      SLIC   HPQOEM  SLIC-MPC
      TCPA   HP      30C8   
      SSDT   HP      HPQPAT
      SSDT   HP      HPQPAT
      SSDT   HP      HPQPAT
      SSDT   HP      HPQPAT

    Thursday, March 03, 2011 1:23 AM
  • Andre!

        Greetings!  On focusing in on the File Mismatch part of the MGA Tool Log I found this TechNet post by you back in mid-December 2010.  The issue is silghtly different as I do not have any non-genuine notifications, but I do have the same corrupt files as the pos as you can note above.

    http://social.technet.microsoft.com/Forums/en/w7itproinstall/thread/39dafe9c-86fc-40e6-836a-f9e16c31034d

    I tried to uninstall the kb971033 update and reinstall it from MS Downloads.  All it did is say the KB was already installed.  Yes, I did reboot in the middle of the process.  So if those 4 files are corrupt because of KB 971033 then how do I get the uncorrupt versions installed so I can activate Windows?  Thank you for your time and effort to assist me...

    Respectfully,

    Dave

    Thursday, March 03, 2011 1:57 AM
  • use expand [1] to extract the Update KB971033 and replace the damaged files with the good ones.

    André

    [1] http://technet.microsoft.com/en-us/library/dd744339(WS.10).aspx


    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    Thursday, March 03, 2011 1:41 PM
  • OK Sportsfans!!!  I figured it out...I remembered something I read somewhere in Googleland that entering Product Keys and Activations need to match the software installed.  This is mostly important when for some reason you need to reinstall Windows from the git go.  You need to use a Product Key that matches the software you are going to put on the computer new.

    In this case I did not realize the used computer I bought was not activated.  In the course of getting it up to speed with applications and updates I put SP1 on it from Windows Update.  Three days later, caused by some process, SP1 and/or KB 971033 (MS anti-pirating spyware) the system attempted an automatic activation.  It failed as noted above with error code 0x8007007B.  I further narrowed the issue to File Mismatches as detailed above with the MGA Tool.  I tried to use Add/Remove programs to remove the KB971033 update and reinstall it.  That did not work either (took me 2 times to do this for some reason) the activation still failed with the same error code.  There were no file issues SFC /SCANNOW and chkdsk did not find anything to fix.  Sorry Andre I did not try to replace the files as above with expand.exe as it nagged at me that there was something else wrong with the files and they were not corrupt.

    The issue?  The computer was loaded with Windows 7 Professional 32bit.  Since I loaded SP1 on it, not knowing the OS was not yet activated.  The system tried to activate Windows 7 Professional 32bit SP1 with a Windows 7 Professional 32bit Product Key.  No WONDER I got the file mismatch errors...the OS install did not match the Product Key.  I unistalled SP1 and activated without issue, problem solved...

    I really appreciate your assistance Andre.  It was really nice to know you were there looking out for me.  Hopefully my trials and tribulatios over the past couple of days will save others from mighty struggles...make certain your OS is activated before installing Service Packs!

    • Marked as answer by DaveRTech Thursday, March 03, 2011 9:42 PM
    Thursday, March 03, 2011 9:41 PM
  • the key is not different for Sp1 or RTM. And not activating Windows should not cause the issues.

    "A programmer is just a tool which converts caffeine into code"

    Want to install RSAT on Windows 7 Sp1? Check my HowTo: http://www.msfn.org/board/index.php?showtopic=150221
    Thursday, March 03, 2011 9:52 PM
  • Andre!

       Greetings!  I certainly have no basis to disagree with you on the difference in keys, but you certainly can't argue with results...The OS activated immediately without issues after I uninstalled SP1...I can't think of any other logic than a mismatch between the key and the installed OS...I have run into this in reinstalling different Windows computers in the past.  The disk has to match the key.  If you try to load Windows XP Pro with a Windows XP Pro SP3 disk using the Product Key from the computer COA sticker it will fail, or it has failed for me.  If you use the original disk that matches the COA Sticker Product Key on the computer it will work, ie Windows XP Pro SP1 COA Sticker Product Key with a Windows XP Pro SP1 disk.  At least that has been my experience YMMV...

    Respectfully,

    Dave

    • Edited by DaveRTech Thursday, March 03, 2011 10:03 PM Added content
    Thursday, March 03, 2011 9:57 PM
  • Not sure I would consider this issue solved.

    I downloaded the Windows 7 w/SP1 VolumeKMSClient ISO through my volume license site. After installing the OS I discovered I cannot activate Windows through KMS. I get error code: 0x8007007B, The filename, directory name, or volume label syntax is incorrect. This seems to be a bug. The only way I can activate the OS is if I enter a MAK key through Windows Activation "Change product key" link.

    Does anyone have any insight on this issue.

    Thanks!

    Tony...

    • Proposed as answer by Pankaj S. Rai Saturday, October 27, 2012 1:18 AM
    Friday, April 08, 2011 3:22 PM
  • I agree with Tony - had the exact same situation, used the exact same solution to work around it. My opinion: something is broken in activation for Windows 7 SP1. If I knew what, I might have a vague clue how to fix it. I don't.

     

    Thanks Tony for showing me the way.

    Wednesday, May 25, 2011 11:53 AM
  • Hi All,

    Wanted to give you an update on this issue as I think I have it fixed. To summarize my environment and issue:

    Running Active Directory Server 2008 R2

    DNS and DHCP services running on Server 2008 R2

    Single Domain

    Multiple Forward Lookup Zones Configured in DNS

    Running KMS Services on Server 2003. (Handles activations of Win7, Server 2008, Ofice 2010) KMS srv record configured in DNS to point all clients to KMS host. This was setup by adding a service record at the root of DNS under _tcp. I added the forward lookup zone _tcp at the root of our DNS for the vlmcs srv record manually.

    Prior to Win7 SP1 being released, all clients activated without any issues. Activation issues started when Win 7 and Server 3008 ISO's were released with SP1 slipstreamed. The error code mentioned in this thread would occur when the activation was attempted from the client. Seemingly the only way to activate the client was to use the MAK code.

    After many days pounding on this issue I found a work around that would allow client machines that were built with the SP1 ISO's to activate through KMS. While not an acceptable solution it does work. The trick was to manually point the client to your local KMS host server. The command to accomplish this is as follows:

    From an elivated command prompt on the client machine, type: slmgr -skms "KMS Server IP Address" (without quotations) After entering the command, client machines would activate normally.

    At first I thought I discovered the miracle cure for activation issues, but soon decided there has to more to this since I didn't have the problem before SP1 was released. Plus, running around typing in the above command was not going to be fun given the number of machines affected by this issue.

    Many days went by trying to figure this out I came to the conclusion that is must be a DNS issue. SP1 probably fixed some holes in Activation or who knows what. Anyway, to make a long story short, here is what I did to fix the problem.

    The main problem was I had to _tcp forward lookup zones in my DNS configuration. One at the root and one in the DomainName forward lookup zone. To fix it, I deleted the _tcp lookup zone from the root of DNS. Next, I added the _vlmcs service record within the domain name _tcp records. This solved activation problems for computers joined to the domain, but not for machines that belonged to workgroups (non-domain computers). To fix activation for non-domain computers, I added option 135 (domain suffix search order) to the DHCP server options. See instructions below.

    1. Open up the DHCP MMC.
    2. Navigate DHCP and choose the DHCP server name.
    3. Right Click on the IPv4
    4. Choose "Set Predefined Options"
    5. Click on Add.
    6. Name: "Domain suffix search order"

    Data Type: String
    Code: "135" (without the quotation marks)
    Description: "List of domain suffixes in order" (without the quotation marks)
    String: Enter "avhsd.org" (without the quotation marks)

    7. Click OK to save changes.
    8. Exit the DHCP MMC and restart the DHCP Server Service.
    9. Open the DHCP MMC again and add the new scope option 135 to your server options/scope.
    10. Windows 7 w/sp1 and Office 2010 will activate without issue.

    Once these steps were taken, the activations worked as expected.

    I hope this helps fellow IS people to fix activation problems.

     

    Cheers!

     

    Tony

    Wednesday, May 25, 2011 5:07 PM
  • I had the same problem. Solution was in activation window - to change the key and re-enter the correct. Greetings Andre.

    Wednesday, June 08, 2011 6:18 PM
  • Tony's "Domain suffix search order" worked for my system - Windows 7 Enterprise, off domain, updated to SP1.  I manually added my AD domain under Control Panel\Network and Internet\Network Connections, Properties of my Wi-Fi connection, Properties of Internet Protocol Version 4, Advanced button, DNS tab, select "Append these DNS suffixes, Add button, enter you fully qualified AD domain.

    Thanks!

    -Joe

    Tuesday, June 28, 2011 1:27 AM
  • manually adding dns suffixes for the AD domain worked for me as well. My Win7 computer was not a member of the domain, and was set to a static IP, so the dns suffix didn't automatically get set.
    Monday, July 11, 2011 11:17 PM
  • If you set a static ip on the machine, do the following: Properties of Computer, click advanced system settings, click the computer name tab, click change, click the more button. Add your primary domain name (ie fqdn: company.org) in the box that says Primary DNS suffix when domain membership changes. Click ok twice and reboot. Activation should work as designed.

     

    Cheers!

     

    Tony...

    Tuesday, July 12, 2011 1:10 AM
  • I was getting this same error and it turned out to be DNS based. The problem in my case was that when I cloned the VM from vCenter, it did not rejoin the clone to the domain. Because of this, the DNS suffix did not exist and therefore activation could not find the server to activate. In this instance 0x8007007B appears to be incorrectly used by Microsoft and refers to DNS. Joining the system back to the domain and then trying after a reboot, activation worked against our KMS server without an issue.

    Since I was recieving the same error I thought I would share my solution. To confirm some of the other responses, if you are not on a domain, I would suggest adding the DNS prefix for your DNS domain containing the KMS records. If you do not have a KMS server or do not know what one is, then your issue is that you need a MAK key (or Retail, OEM, etc...) or activation will not work.

    Thursday, October 06, 2011 2:00 PM
  • I got the same error. I have Windows 7 Enterprise running but got no domain or KMS servers running. I use the msdn key. Where pre SP1 i didnt have to go through trouble I couldnt install on WIndows 7 SP1.

    I fixed it by the following (netstat showed activate (127.0.0.1) as kms server):

    slmgr.vbs /ipk <product key from MSDN (MAK)>

    This installed the product key, then I ran slmgr.vbs /ato which activated my computer as can be seen in slmgr.vbs /dlv

    Hope this helps.

    • Proposed as answer by goodbyelenin Thursday, March 01, 2012 7:23 PM
    Sunday, November 06, 2011 8:19 PM
  • It was just what I needed. Thanks.


    Louis T Klauder
    Monday, November 21, 2011 5:01 AM
  • thanks! works perfectly!
    Thursday, March 01, 2012 7:23 PM
  • Ok, for ALL you people that have received this error.......DO NOT follow DaveRTechs' instructions unless mine doesn't work...NO disrespect Dave, but your solution is long, time consuming and will not work for everybody.  I am honestly suprised that it has worked for some....

    I belive this is this fix for this error regardless if you have installed SP1 or not....  When windows throws up this error 0x8007007B it is because it is trying to activate a randomly generated key.  Where did this key come from?  I DO NOT KNOW.... However, follow these instructions:

    Click start

    right click on computer

    Scroll down to the bottom under "windows activation" and select, change product key

    enter in your CORRECT PRODUCT KEY and let Windows do its thing....if this doesn't work or you receive another error, DOUBLE CHECK YOUR PRODUCT KEY AND ENTER IT AGAIN...MAKE SURE YOU ENTERED IT CORRECT.

    After Windows is succesfully activated....run windows update again, you may not have all the security updates/patches that are critical

    Please respond to this post and let me know what happened...THANKS :)

    Saturday, June 23, 2012 2:03 AM
  • Noel's fix worked immediately - symptoms were just as described and cure was instant!

    Thanks. (that should get moved to the top of the thread!!)

    Monday, June 25, 2012 7:56 PM
  • Noel's fix also worked for me immediately. Today was my last day to activate. I followed the simple instructions and activation was successful which pleased me immensely.  I agree with the previous post, this should be at the top of the page. Thanx Noel. 
    Tuesday, June 26, 2012 12:02 AM
  • Big, big thank you Noel!!! As mentioned below, this should definitely get kicked on up this thread.

    Friday, September 21, 2012 4:01 AM
  • Mr. Patrick, your solution fixed my issue perfectly. Thanks a million.
    Friday, October 12, 2012 7:55 PM
  •  downloaded and successfully installed Windows 7 SP1 for my 32bit Windows 7 Professional, installed on a Dell Latitude E5510  Core 2 Duo  Computer with 4GB RAM and 500GB HD.   system attempted a Windows Activation which failed with a 0x8007007B error "the file name, directory name or volume label syntax is incorrect.

       So no errors there from what I can tell. 

        What do I need to do to clear this error and reactivate windows ?  I really appreciate your time and effort to assist me to solve my issue here.  Thank you.

    Respectfully

    Mohammad


    Tuesday, March 12, 2013 6:45 AM
  • Do you have your own KMS server?  If not, just follow WalkInTheFallen55's post by changing Product Key (provide KMS or MAK key)

    I have my own KMS server, and I saw that error (Long time ago) when I tried to activate a non-domain workstations.  To fix that, just follow Tony Inglima's post about Primary DNS thingy (whether your using DHCP or Static).

    Wednesday, May 29, 2013 7:49 PM
  • I SOLVED my issue, with issuing "slmgr /ipk <product key>" in administrator console, and than running the "Activate Windows" from the windows globe search pick.

    I had the same issue after installing a fresh WIN 7 DVD, it never asked me for product key but later on it asked to be activated, and the activation failed with 0x8007007B  code.


    • Edited by AtlantaKid Wednesday, August 07, 2013 1:45 PM
    Wednesday, August 07, 2013 1:45 PM
  • I installed a fresh Win7 with SP1 from the DVD, installed all the default options, next->next->finish. First step from a fresh install was to activate and I got this error. But weird on a fresh install since it had nothing on it at all (no patches, nothing). Not sure why but it seems that Windows is trying to activate before I type the key in. So under Control Panel->System, down the bottom is a Change Product Key, I typed in my key from the sticker on the back of the box and it activated.

    Tuesday, December 10, 2013 1:55 AM
  • Noel's suggestion got it done for me.  And it's an elegant simple solution to boot.
    Monday, February 10, 2014 3:01 PM