Windows 7 not genuine, after change of hard drive.

All replies

• 

  

  0

  Sign in to vote

  The installed Windows 7 is counterfeit.

  The installed OEM_SLP Product Key is ONLY valid on machines which shipped with WIndows 7 installed - your machine shipped 6 months before Windows 7 launched.

  You need to reformat and reinstall with genuine media and Key.

  ---

  Noel Paton | Nil Carborundum Illegitemi

  CrashFixPC | The Three-toed Sloth

  No - I do not work for Microsoft, or any of its contractors.

  • Proposed as answer by Noel D PatonModerator Sunday, September 6, 2015 2:49 PM

  Tuesday, August 25, 2015 8:03 AM

  Moderator
• 

  

  0

  Sign in to vote

  Interesting, but I need some convincing.

  Could you explain what brings you to that conclusion from the data I sent, please? How do you know the shipping date?

  I, and the owner, have spent more than 40 minutes talking to 3 different people at Fujitsu support. They rang me back twice after considering the problem. I gave them the serial numbers of the laptop and the recovery DVD. They told me which disk should accompany the machine and we confirmed it is the correct one. Surely they would have told me what you have told me.

  If you are correct about the time differences, I remember buying a Sony machine around the same time, with XP installed but with the promise (fulfilled) that W7 would be installed later. Could that be the scenario?

  Why has it worked without problems for the past 6 years?

  Tuesday, August 25, 2015 11:21 AM
• 

  

  0

  Sign in to vote

  I don't know the exact shipping date - but the manufacturing date is soon after the creation of the BIOS, and before Fujitsu-Siemens changed the BIOS to be compliant with the SLIC 2.1 requirements of Windows 7.

  Your BIOS is dated 20090327 - Windows 7 was released to manufacturing on 22 July 2009, and any BIOS prior to that date cannot have a compliant SLIC table.

  The SLIC table here is also showing as being invalid - which may mean that there has been an attempt to modify it, or simply that it's cot corrupted.

  Finally - for what version and edition of Windows is the COA sticker on the case of the machine valid? If it's not Windows 7 Home Premium then the installed Product Key cannot be valid. I suspet that it will be Windows Vista Home Premium

    

  ---

  Noel Paton | Nil Carborundum Illegitemi

  CrashFixPC | The Three-toed Sloth

  No - I do not work for Microsoft, or any of its contractors.

  Tuesday, August 25, 2015 12:23 PM

  Moderator
• 

  

  0

  Sign in to vote

  I have spoken to the owner. The machine was purchased as a new machine in February 2010, from a supplier, not directly from Fujitsu. The Software Recovery Manual, supplied with the machine appears to be genuine Fujitsu, published in Sept 2009. It refers to Windows 7 being a trademark of Microsoft.

  At some time in the past, not sure when, but before this problem, he had written the Windows Key on the front of the user manual. It is the same key that was automatically supplied either by the mother board or the recovery disk, during this new installation onto the new disk. (To emphasise: the key was not entered by me, but automatically, so it is in the BIOS or the recovery disk somewhere.)

  The sticker on the rear of the laptop is unreadable. It has been used as a laptop and the printing rubbed off by the person's knee. However, the multi-coloured metal thread is still there and the Microsoft logo on the right side is still visible. The background colour is blue not green which says to me that it was for Windows 7 not Vista. The sticker on the front, at the side of the keyboard has a windows logo and says Windows 7.

  Are we not dealing here with a machine built at the end of Vista period, but delivered during the transition from Vista to W7 and now updated with a new hard disk, so the Microsoft checker can't sort out the mess?

  Tuesday, August 25, 2015 3:06 PM
• 

  

  0

  Sign in to vote

  No - the motherboard was built before Windows 7 was finalised, and before MS released the bits necessary to write to the BIOS.

  There is no possible way that this machine originally shipped with Windows 7 unless the motherboard has been replaced with an older one, or the BIOS has been backdated - neither of which are at all likely.

  It's more likely that a counterfeit was installed by the vendor to make the machine more saleable - they probably got it as an end-of-line bargain at a reduced price, and rather than pass that on to the customer, installed Windows 7 and jacked the price back to the then-current market price.

  As to why the machine is only now showing the problems...

  1) recent install of SP1 may have broken the hack

  2) something appears to have ripped the WAT update out by the roots - this could have triggered the alarms, or been part of the original hack and only now come to light, although it *should* have run alarm bells when first installed.

  3) malware may have broken the hack - or an AV

  4) something else either installed or uninstalled may have accidentally broken the hack

  etc. etc.

  ---

  Noel Paton | Nil Carborundum Illegitemi

  CrashFixPC | The Three-toed Sloth

  No - I do not work for Microsoft, or any of its contractors.

  Tuesday, August 25, 2015 4:44 PM

  Moderator
• 

  

  0

  Sign in to vote

  OK, well thank you for your time and patience on this. I am about to give up.

  I am not entirely convinced by your answers I still think this is a valid installation of Win7 on an end-of-line Vista machine. We have valid Fujitsu disks and documentation. However, it will be cheaper for me to buy a key from a discontinued machine for 30-quid than to spend time trapped between the two giants of Fujitsu and Microsoft. Probably their intention, because there is no money in it for them unless we buy something new. Fixing things is not the modern mentality.

  I have asked Fujitsu to confirm what was installed on the machine when shipped.

  Agreed, we know the motherboard was built before Win7 was released for OEM installation, but surely the manufacturers were working on integration before that.

  Agreed, We know something ripped it apart. The hard disk was destroyed beyond readability even with bit-level readers and repairers.

  I updated the Bios after I installed the OS on the new disk. After which it did 287 updates, over three days, and was working without problems for two weeks.

  Tuesday, August 25, 2015 5:25 PM
• 

  

  0

  Sign in to vote

  Fujitsu Technical Support have replied:

  "Dear Sir,

  I can confirm that when this unit left the Fujitsu factory it was shipped with Windows 7 Home Premium installed on it.

  Yours Sincerely, James H... Fujitsu (FTS) Limited... "

  So now can someone please provide HELP on what is going wrong and how to reinstall windows 7 onto a this new - and larger - hard disk and updated BIOS?

  Wednesday, August 26, 2015 11:57 AM
• 

  

  0

  Sign in to vote

  I find that very surprising - there is no way that should be the case.

  In that case all I can suggest is that you call MS and see if you can persuade them to part with a new Key.

  Attempt Telephone Activation, and speak to an operator - they will tell you that your current Key is blocked (they should then ask for confirmation of your Product Key). Explain
  to them your problem, that you need to change the Key to the one on your sticker, but that the sticker is unreadable (could they please supply a replacement Key?). Hopefully they will ask for documentary proof of the sticker, in the form of an email with a picture of the affected sticker - and you can proceed from there.

  Sometimes it takes two or three calls before you get an operator who actually knows and uses this procedure - but I know that it can and does happen (or at least used to happen - now that Win10 has been released they may be taking a harder line on these things)

  
  

  If you can't get to Telephone Activation the normal way, use your local number from this list... https://www.microsoft.com/en-us/licensing/existing-customer/activation-centers.aspx

  ---

  Noel Paton | Nil Carborundum Illegitemi

  CrashFixPC | The Three-toed Sloth

  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, August 26, 2015 12:35 PM

  Moderator
• 

  

  0

  Sign in to vote

  Thank you for the info.

  Since you said "...something ripped the WAT update out by the roots..." I am doing another complete installation, to return it to the state it was before I returned it to the owner last time. That should remove any changes/updates he made. Strangely, going back through the restore points doesn't remove them!

  Then I'll follow your suggestions.

  I'll let you know. That may take a while - it took more than three weeks to fail last time...

  Thanks for your time and patience.

  Wednesday, August 26, 2015 3:32 PM
• 

  

  0

  Sign in to vote

  Post a new MGADiag as soon as you've done the install - If the SLIC table is OK, in theory it should self-activate, but if the SLIC table is actually damaged, rather than just having a broken overlay on it, then it won't activate.

  ---

  Noel Paton | Nil Carborundum Illegitemi

  CrashFixPC | The Three-toed Sloth

  No - I do not work for Microsoft, or any of its contractors.

  Wednesday, August 26, 2015 3:47 PM

  Moderator
• 

  

  0

  Sign in to vote

  I think I have solved it. Hope you will confirm so.

  I spent an hour and a half on the phone with the MS help desk. Granted them remote access, but the end result was no progress and being told "Only the OEM can sort it out..." Email to Fujitsu was answered "Call our helpdesk..." Having already spent 45 Minutes on the phone with them at 64 pence per minute. Going round in circles was making me dizzy - and poorer.

  Firstly I re-installed the disk image that had been working when I returned it to its owner. (trying to avoid reinstalling all the drivers and 286 W7 updates etc. - I wish Microsoft would make a consolidated version of their OS's available after so many updates and patches.) However, that gave me the black screen immediately.

  So, I went back to the original Fujitsu DVD and did a custom install, stopped all updating, downloaded and ran MGA Diagnostic Tool. I noticed that it said:

  License Status: Initial grace period
  Time remaining: 43200 minute(s) (30 day(s))

  Then the Licence Status: Notification, in the previously posted output made more sense to me. This must have been what happened before (30 days, then black screen). If there had been some indication of that after the initial installation, I could have dealt with this earlier and saved a lot of time, money and credibility with the owner.

  So, that and your previous comments about the BIOS set me to checking it again. It seems I may have flashed it with a March 2009 instead of a August 2009 version!!??!!

  Re-flashing with that and installing again from the DVD gave me:

  License Status: Licensed - I'm hoping that means what it says.

  Do you think I could install from the disk image again, or must I go go through two days of updating drivers and 286 W7 updates?

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

  Validation Code: 0
  Cached Online Validation Code: N/A, hr = 0xc004f012
  Windows Product Key: *****-*****-74TDC-FHRMV-XB88W
  Windows Product Key Hash: oapGC3x6sND4JBSp2652COj8+UA=
  Windows Product ID: 00359-OEM-8992687-00009
  Windows Product ID Type: 2
  Windows License Type: OEM SLP
  Windows OS version: 6.1.7600.2.00010300.0.0.003
  ID: {559D6EC3-D1A0-4601-A592-847BC5ECD549}(1)
  Is Admin: Yes
  TestCab: 0x0
  LegitcheckControl ActiveX: N/A, hr = 0x80070002
  Signed By: N/A, hr = 0x80070002
  Product Name: Windows 7 Home Premium
  Architecture: 0x00000000
  Build lab: 7600.win7_rtm.090713-1255
  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:\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>{559D6EC3-D1A0-4601-A592-847BC5ECD549}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7600.2.00010300.0.0.003</OS><Architecture>x32</Architecture><PKey>*****-*****-*****-*****-XB88W</PKey><PID>00359-OEM-8992687-00009</PID><PIDType>2</PIDType><SID>S-1-5-21-3051086036-3728089923-2761325576</SID><SYSTEM><Manufacturer>FUJITSU SIEMENS</Manufacturer><Model>AMILO Li3710</Model></SYSTEM><BIOS><Manufacturer>Phoenix</Manufacturer><Version>1.10</Version><SMBIOSVersion major="2" minor="5"/><Date>20090821000000.000000+000</Date></BIOS><HWID>DEBA3607018400F8</HWID><UserLCID>0809</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>GMT Standard Time(GMT+00:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM><OEMID>FSC   </OEMID><OEMTableID>PC      </OEMTableID></OEM><GANotification/></MachineData><Software><Office><Result>109</Result><Products/><Applications/></Office></Software></GenuineResults> 

  Spsys.log Content: 0x80070002

  Licensing Data-->
  Software licensing service version: 6.1.7600.16385

  Name: Windows(R) 7, HomePremium edition
  Description: Windows Operating System - Windows(R) 7, OEM_SLP channel
  Activation ID: d2c04e90-c3dd-4260-b0f3-f845f5d27d64
  Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
  Extended PID: 00359-00178-926-800009-02-2057-7600.0000-2502015
  Installation ID: 017841783090853365468634638262541770343135844422294372
  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: XB88W
  License Status: Licensed
  Remaining Windows rearm count: 3
  Trusted time: 07/09/2015 16:05:57

  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: MAAAAAEAAgABAAIAAAABAAAAAgABAAEAeqgy5O5ben+SrFBTpKniHnB2nCqgO1a4

  OEM Activation 1.0 Data-->
  N/A

  OEM Activation 2.0 Data-->
  BIOS valid for OA 2.0: yes
  Windows marker version: 0x20001
  OEMID and OEMTableID Consistent: yes
  BIOS Information:
    ACPI Table Name OEMID Value OEMTableID Value
    APIC   QCI     EF7    
    FACP   QCI     EF7    
    HPET   QCI     EF7    
    BOOT   QCI     EF7    
    MCFG   QCI     EF7    
    TCPA   QCI     EF7    
    SLIC   FSC     PC     
    SSDT   PmRef  Cpu0Cst
    SSDT   PmRef  Cpu0Cst
    SSDT   PmRef  Cpu0Cst

  • Proposed as answer by Noel D PatonModerator Monday, September 7, 2015 8:00 PM
  • Marked as answer by Noel D PatonModerator Sunday, September 13, 2015 10:37 AM

  Monday, September 7, 2015 7:35 PM
• 

  

  0

  Sign in to vote

  As far as I can see, that install looks fine - Well done!

  The BIOS date is August - and the SLIC table now looks happy.

  It all goes to show that extreme care needs to be taken with all BIOS operations ;)

  Good luck!

  ---

  Noel Paton | Nil Carborundum Illegitemi

  CrashFixPC | The Three-toed Sloth

  No - I do not work for Microsoft, or any of its contractors.

  Monday, September 7, 2015 8:00 PM

  Moderator