WINDOWS NOT GENUINE!?!??!?!

#1
I have searched forums for weeks.
Windows is telling me that I am running a non-genuine copy of windows 7. This is NOT true. This is a real copy of the OS. So I don't know what is going on.
I finally decided to do a system restore, rolled it back to June and everything was okay for a couple of days.
But Then

bsod.png
so I click on the link and it takes me here:

Genuine Microsoft Software

and then I download the file... and I get this:
bsod2.png

I don't know what to do anymore! It is driving me crazy. Please HELP!
 


Elmer

Extraordinary Member
#2
Hi zomgfixitnow and Welcome to The Forum.

Just to check that no system files have been corrupted, run sfc /scannow in an elevated command prompt.
 


#3
problems.png

Trying to find the log.
 


Elmer

Extraordinary Member
#4
May well be a hidden folder. Did it find any errors?

Sorry, Yes it did. Should learn to read!!
 


#5
Haha, I should have typed it up instead of just putting the image! Sorry!

It wont let me open up the file.
 


#7
I called Microsoft Validation put in all the numbers and it is still telling me that this software is not genuine. It came on the computer which came directly from hp! What the heck!

I am uploading the log to google now so I can share it with you.

Thanks
 


#8
CBS Failed to get session package state for package: Package_2_for_KB2552343~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]

CBS Failed to get session package state for package: Package_2_for_KB2552343~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
CBS Failed to get session package state for package: Package_3_for_KB2552343~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
CBS Failed to get session package state for package: Package_2_for_KB2552343~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
CBS Failed to get session package state for package: Package_2_for_KB2552343~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
CBS Failed to get session package state for package: Package_3_for_KB2552343~31bf3856ad364e35~amd64~~6.1.1.0 [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
 


#9
activated.png
According to this... it is already activated!
 


Elmer

Extraordinary Member
#10
How long have you had the laptop?

How long has it been telling you Windows is not genuine?

Do you have the RC version of SP1 installed?
Warnings of the imminent expiration of SP1 RC began around the end of August. Computers with Windows 7 SP1 RC installed will be treated as if it is non-genuine software even if the original system of Windows 7 is genuine.
 


#11
How long have you had the laptop?

How long has it been telling you Windows is not genuine?

Do you have the RC version of SP1 installed?
Warnings of the imminent expiration of SP1 RC began around the end of August. Computers with Windows 7 SP1 RC installed will be treated as if it is non-genuine software even if the original system of Windows 7 is genuine.

The computer will be two years old in December. How do I check what version of SP1 is installed? Should I just uninstall SP1? Looks like I am running this version: Help and Supporthe pop up has been happening since the middle of August.

Thanks
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#12
It seems KB2552343 is a critical update, and it has not been installed. It came out around July 11, so if your system was installed then, it should have loaded. Many times they show errors, but install eventually so you could check to see if it is actually installed. You might check this Microsoft site to see if anything there might help.

In windows Update, you need to look in the installed updates, not just the update history. If you need to remove an update, you could do it there.

I do not believe the errors you show from the CBS.log are the problems discovered when you used the SFC, but not sure. Did you run the command line indicated on this Microsoft site to help dig out the SFC information.? These files can be quite large, so looking close to the bottom of the listing is a good idea. You could just search the file for the language indicated ([SR] Cannot repair member file).
 


#13
Went to the Genuine Check download, got the code, validated it, got access to KB2552343 and then this again: moprobls.png

Looked at the log again....

searched for SR -->

2011-09-13 18:20:40, Info CSI 00000009 [SR] Verifying 1 components
2011-09-13 18:20:40, Info CSI 0000000a [SR] Beginning Verify and Repair transaction
2011-09-13 18:20:41, Info CSI 0000000b Repair results created:
POQ 0 starts:
0: Move File: Source = [l:192{96}]"\SystemRoot\WinSxS\Temp\PendingRenames\9d8a72847c72cc0103000000c402400f._0000000000000000.cdf-ms", Destination = [l:104{52}]"\SystemRoot\WinSxS\FileMaps\_0000000000000000.cdf-ms"
1: Move File: Source = [l:162{81}]"\SystemRoot\WinSxS\Temp\PendingRenames\bed872847c72cc0104000000c402400f.$$.cdf-ms", Destination = [l:74{37}]"\SystemRoot\WinSxS\FileMaps\$$.cdf-ms"
2: Move File: Source = [l:214{107}]"\SystemRoot\WinSxS\Temp\PendingRenames\2eaa7f847c72cc0105000000c402400f.$$_system32_21f9a9c4a2f8b514.cdf-ms", Destination = [l:126{63}]"\SystemRoot\WinSxS\FileMaps\$$_system32_21f9a9c4a2f8b514.cdf-ms"
3: Move File: Source = [l:270{135}]"\SystemRoot\WinSxS\Temp\PendingRenames\28af86847c72cc0106000000c402400f.$$_system32_spp_plugin-manifests-signed_d1e9d31c180bebd2.cdf-ms", Destination = [l:182{91}]"\SystemRoot\WinSxS\FileMaps\$$_system32_spp_plugin-manifests-signed_d1e9d31c180bebd2.cdf-ms"

POQ 0 ends.
2011-09-13 18:20:41, Info CSI 0000000c [SR] Verify complete
2011-09-13 18:20:41, Info CSI 0000000d [SR] Verifying 1 components
2011-09-13 18:20:41, Info CSI 0000000e [SR] Beginning Verify and Repair transaction
2011-09-13 18:20:41, Info CSI 0000000f Repair results created:
POQ 1 starts:

POQ 1 ends.
2011-09-13 18:20:41, Info CSI 00000010 [SR] Verify complete
2011-09-13 18:20:41, Info CSI 00000011 [SR] Verifying 1 components
2011-09-13 18:20:41, Info CSI 00000012 [SR] Beginning Verify and Repair transaction
2011-09-13 18:20:41, Info CSI 00000013 Repair results created:
POQ 2 starts:
..................................





Also searched "failed" and this came up for several pages:
2011-09-09 16:46:05, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_std.sqm, flags: 0x2 [HRESULT = 0x80004005 - E_FAIL]
2011-09-09 16:46:05, Info CBS SQM: Failed to start standard sample upload. [HRESULT = 0x80004005 - E_FAIL]
2011-09-09 16:46:05, Info CBS SQM: Failed to start upload with file pattern: C:\Windows\servicing\sqm\*_all.sqm, flags: 0x6 [HRESULT = 0x80004005 - E_FAIL]
2011-09-09 16:46:05, Info CBS SQM: Failed to start always sample upload. [HRESULT = 0x80004005 - E_FAIL]
2011-09-09 16:46:05, Info CBS SQM: Warning: Failed to upload all unsent reports. [HRESULT = 0x80004005 - E_FAIL]
 


Saltgrass

Excellent Member
Microsoft Community Contributor
#14
The CBS log will give many messages that are not relevant. If the SFC said it could not repair some files, you should have the exact working indicated earlier. If something does not at least say FATAL, it might have been corrected. The CBS.log contains items from at least Windows Update and the SFC scans. Probably other inputs also, but not sure. If you want to send me the file, I will check. If you decide to attach it, just copy the last couple of days into a text file and attach.

You might try the SFC again to see if anything changed?

Is your Windows Update working normally?

There is also a WindowsUpdate.log in the Windows folder you might send me, or attach the last couple of days. It will also have to be copied to the desktop.
 


This website is not affiliated, owned, or endorsed by Microsoft Corporation. It is a member of the Microsoft Partner Program.