W7 Ultimate x64 - Pre-Validation Query

Page 1 of 2 12 LastLast

  1. Posts : 8
    Windows 7 Ultimate x64
       #1

    W7 Ultimate x64 - Pre-Validation Query


    I've been given a nice HP laptop and run through the main checks to correct anything that was potentially 'sketchy' via SpyHunter / RegHunter. Everything works perfectly now with no issues (rare!) but Windows has never been validated on this laptop. I've run SLMGR -REARM run a couple of times and there's 29 days left yet, but I think, from what I can see so far (see file mismatches extract from the initial MGAdiag), that if I attempt to validate this as it is currently, it will probably result in a "not genuine" type MS message...

    Code:
    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]
    The latest MGADiag report is below and that obviously still has the mismatches showing. I did read another thread so this report was run AFTER running CHKDSK C: /R and then SFC /SCANNOW and a compressed copy of the cbs.log from that exercise is attached.

    I'd appreciate guidance! e.g. if the validation fails, does that result in the installed W7 Ultimate x64 version locking and then becoming unusable? Plus the error corrective options / paths for those file mismatches etc. I only have the laptop itself, no disk copy of Windows7 Ultimate x64 etc ssssoooooo.....

    I don't actually know, so I'd prefer to ask those that do know, first

    Post CHKDSK C: /R and SFC /SCANNOW MGADiag report:

    Code:
    Diagnostic Report (1.9.0027.0):
    -----------------------------------------
    Windows Validation Data-->
    
    Validation Code: 0
    Cached Online Validation Code: N/A, hr = 0xc004f012
    Windows Product Key: *****-*****-TMVMJ-BBMRX-3MBMV
    Windows Product Key Hash: 55n8g6xdzhe4AOWhmTzdzQoLfa4=
    Windows Product ID: 00426-292-0000007-85824
    Windows Product ID Type: 5
    Windows License Type: Retail
    Windows OS version: 6.1.7600.2.00010100.0.0.001
    ID: {BB05C5B8-6B83-4BEC-895E-B9367EF02E20}(3)
    Is Admin: Yes
    TestCab: 0x0
    LegitcheckControl ActiveX: N/A, hr = 0x80070002
    Signed By: N/A, hr = 0x80070002
    Product Name: Windows 7 Ultimate
    Architecture: 0x00000009
    Build lab: 7600.win7_gdr.150318-1623
    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 Enterprise 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_E2AD56EA-765-b01a_E2AD56EA-766-0_E2AD56EA-148-80004005_16E0B333-89-80004005_B4D0AA8B-1029-80004005
    
    Browser Data-->
    Proxy settings: N/A
    User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
    Default Browser: C:\Program Files (x86)\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-->
    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>{BB05C5B8-6B83-4BEC-895E-B9367EF02E20}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010100.0.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-3MBMV</PKey><PID>00426-292-0000007-85824</PID><PIDType>5</PIDType><SID>S-1-5-21-2832956965-1999899848-3240542479</SID><SYSTEM><Manufacturer>Hewlett-Packard</Manufacturer><Model>HP 14 Notebook PC</Model></SYSTEM><BIOS><Manufacturer>Insyde</Manufacturer><Version>F.18</Version><SMBIOSVersion major="2" minor="7"/><Date>20140521000000.000000+000</Date></BIOS><HWID>B7B83607018400FC</HWID><UserLCID>0409</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>SE Asia Standard Time(GMT+07:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><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>7480B9502DF0D86</Val><Hash>oYWOW5ayFE3pZ+jvTpuXYsY64JE=</Hash><Pid>89388-707-8722531-65387</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, Ultimate edition
    Description: Windows Operating System - Windows(R) 7, RETAIL channel
    Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
    Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
    Extended PID: 00426-00170-292-000000-00-1033-7600.0000-2972011
    Installation ID: 003966978714824852109623968103912524479455728556269553
    Processor Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88338
    Machine Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88339
    Use License URL: http://go.microsoft.com/fwlink/?LinkID=88341
    Product Key Certificate URL: http://go.microsoft.com/fwlink/?LinkID=88340
    Partial Product Key: 3MBMV
    License Status: Initial grace period
    Time remaining: 41760 minute(s) (29 day(s))
    Remaining Windows rearm count: 0
    Trusted time: 2/27/2016 1:08:19 PM
    
    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: LgAAAAEAAQABAAEAAAABAAAAAwABAAEA6GHgiVKgsvc2xRqprBo/Rca53l26eg==
    
    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			HPQOEM		SLIC-MPC
      FACP			HPQOEM		SLIC-MPC
      DBGP			HPQOEM		INSYDE  
      HPET			HPQOEM		INSYDE  
      BOOT			HPQOEM		INSYDE  
      MCFG			HPQOEM		INSYDE  
      UEFI			HPQOEM		INSYDE  
      FPDT			HPQOEM		SLIC-MPC
      ASF!			HPQOEM		INSYDE  
      SSDT			HPQOEM		INSYDE  
      ASPT			HPQOEM		INSYDE  
      LPIT			HPQOEM		INSYDE  
      SSDT			HPQOEM		INSYDE  
      SSDT			HPQOEM		INSYDE  
      SSDT			HPQOEM		INSYDE  
      SSDT			HPQOEM		INSYDE  
      DMAR			HPQOEM		INSYDE
    Last edited by nhungw7; 27 Feb 2016 at 21:51.
      My Computer


  2. Posts : 17,322
    Win 10 Pro x64
       #2

    That is the default key, you need to get the product key off the COA sticker and that should fix that.

    W7 Ultimate x64 - Pre-Validation Query-coa-stickers.gif

    That should be on the bottom or in the battery compartment.

    The default key will never activate.

    Once you get that key in there you can fix the file mismatches with the WAT update.

    https://support.microsoft.com/en-us/kb/971033
      My Computer


  3. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #3

    Thanks derekimo for your speedy reply, but I can feel things crashing down now ((
    There is no COA sticker anywhere on the laptop, either externally or inside the battery area. It's super clean - literally...
    The WAT update you have posted, I am guessing, will not work at all without that product key?
    I have downloaded it but not run it yet Hmmmmm
      My Computer


  4. Posts : 17,322
    Win 10 Pro x64
       #4

    That's interesting that it doesn't have the COA, I know when they came out with windows 8 they did away with those, is there a sticker anywhere referring to W8?

    That update I posted will only get rid of the file mismatches, you still need a product key within the next 29 days, or you will have to reinstall, that will just start it over and wont solve your problem.

    Either way, you need to get a product key, sounds like you are going to have to buy one.
      My Computer


  5. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #5

    Nope. No stickers anywhere!

    All the HP stuff itself is clearly visible on their super strong metallic type stickers / labels but nothing else, anywhere at all.

    Buy one. Yep... that's what I thought

    What's the expert view of "Loaders" like this one: [REMOVED] fake nonsense that will never work.... or a cash saving option albeit surely technically illegal?
      My Computer


  6. Posts : 17,322
    Win 10 Pro x64
       #6

    Those are illegal so I removed it. We don't support piracy or talk about it.

    There's really not much you can do but get a product key if there is nothing that you can see to show there is a legal install.
      My Computer


  7. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #7

    Okay, if I understand this clearly then derekimo, it's this specific order of events:

    1) Purchase a legal product key

    2) Enter the new product key

    3) Run the Wat update

    4) Run a new MGADiag report to confirm that 1) - 3) are okay and all is well

    5) Then and only then, go and validate the licence (new product key)

    6) Finish with no other issues
      My Computer


  8. Posts : 17,322
    Win 10 Pro x64
       #8

    Yeah, that looks about right. I don't see any reason you can't install the WAT update now though.

    It will only get rid of the file mismatches anyway.
      My Computer


  9. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #9

    I have run the WAT update and yes, those errors have all vanished, regardless of it's current validation-free state

    Thanks for this guidance! Off to secure a product key at a super sharp price somewhere next then.... :)
      My Computer


  10. Posts : 8
    Windows 7 Ultimate x64
    Thread Starter
       #10

    Finish! New official Windows product key purchased (at a super-price!) number entered and validated. NO errors. Excellent!
      My Computer


 
Page 1 of 2 12 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:27.
Find Us