Suddenly Windows 7 is not genuine

Let's try this another (more aggressive) way:

It is essential that you don't skip a step! :)

Backing Up Your Registry

1. The steps that I am about to suggest involve modifying the registry. Modifying the registry can be dangerous so we will make a backup of the registry first.
   Modification of the registry can be EXTREMELY dangerous if you do not know exactly what you are doing so follow the steps that are listed below EXACTLY. if you cannot perform some of these steps or if you have ANY questions please ask BEFORE proceeding.
   
2. Download ERUNT
   (ERUNT (Emergency Recovery Utility NT) is a free program that allows you to keep a complete backup of your registry and restore it when needed.)
3. Install ERUNT by following the prompts
   (use the default install settings but say no to the portion that asks you to add ERUNT to the start-up folder, if you like you can enable this option later)
4. Start ERUNT
   (either by double clicking on the desktop icon or choosing to start the program at the end of the setup)
5. Choose a location for the backup
   (the default location is C:\WINDOWS\ERDNT which is acceptable).
6. Make sure that at least the first two check boxes are ticked
7. Press OK
8. Press YES to create the folder.

Registry Modifications

1. Go to Start > Run to bring up the run box
2. In the box, type notepad.exe and press OK to open Notepad
3. Copy (Ctrl+C) all of the text in the following box and paste (Ctrl+V) it into Notepad
   
   
   Code:

   Windows Registry Editor Version 5.00
   
   [-HKEY_LOCAL_MACHINE\Software\Microsoft\EventSystem\{26c409cc-ae86-11d1-b616-00805fc79216}\Subscriptions]

4. Go to File > Save As... and save it to your Desktop named Fix.reg. Make sure you change the Save as type to All Files (*.*)
5. Locate Fix.reg on your Desktop and double-click on it to merge it with your registry
6. Answer Yes when prompted about merging with the registry

Batch File

1. Click on the Start button and in the search box, type Notepad and click on it
2. Copy (Ctrl+C) all of the text in the following box and paste (Ctrl+V) it into Notepad
   Code:

   net stop “System Event Notification Service”
    net stop “COM+ Event System”
    net stop “Microsoft Software Shadow Copy Provider”
    net stop “Volume Shadow Copy”
    cd /d %windir%\system32
    net stop vss
    net stop swprv
    regsvr32 /s ole32.dll
    regsvr32 /s oleaut32.dll
    regsvr32 /s vss_ps.dll
    vssvc /register
    regsvr32 /s /i swprv.dll
    regsvr32 /s /i eventcls.dll
    regsvr32 /s es.dll
    regsvr32 /s stdprov.dll
    regsvr32 /s vssui.dll
    regsvr32 /s msxml3.dll
    net start “System Event Notification Service”
    net start “COM+ Event System”
    net start “Microsoft Software Shadow Copy Provider”
    net start “Volume Shadow Copy”

3. Go to File > Save As... and save it to your Desktop named fix.bat. Make sure you change the Save as type to All Files (*.*)
4. Locate fix.bat on your Desktop and right click then select Run as administrator

REBOOT YOUR COMPUTER

Batch File

1. Click on the Start button and in the search box, type Notepad and click on it
2. Copy (Ctrl+C) all of the text in the following box and paste (Ctrl+V) it into Notepad
   Code:

   cd /d %windir%\system32
    net stop vss
    net stop swprv
    regsvr32 ole32.dll
    regsvr32 oleaut32.dll
    regsvr32 /i eventcls.dll
    regsvr32 vss_ps.dll
    vssvc /register
    regsvr32 /i swprv.dll
    regsvr32 es.dll
    regsvr32 stdprov.dll
    regsvr32 vssui.dll
    regsvr32 msxml.dll
    regsvr32 msxml3.dll
    regsvr32 msxml4.dll
   vssadmin list writers > 0 & start notepad 0

3. Go to File > Save As... and save it to your Desktop named fix.bat. Make sure you change the Save as type to All Files (*.*)
4. Locate fix.bat on your Desktop and right click then select Run as administrator

This will open a Notepad window. Copy and paste this text into your next post please!

Tom

I *think* ASR twriter is actually part of Windows much-forgotten Automated System Recovery - which is one reason I picked it (the other is that it was first on the list! )
WMI Writer should be a safe one -
The other 'Default' ones are
BITS Writer
SPP
System Writer
SystemRestore
VolSnap
and
MSSearchService Writer

NoelDP said:

I *think* ASR twriter is actually part of Windows much-forgotten Automated System Recovery - which is one reason I picked it (the other is that it was first on the list! )
WMI Writer should be a safe one -
The other 'Default' ones are
BITS Writer
SPP
System Writer
SystemRestore
VolSnap
and
MSSearchService Writer

Ooh, thanks. Never knew that :) It wasn't on my list so I (wrongly!) assumed it wasn't a Windows thing.

@elimak,

That's a lot of errors! Let's see if those DLL files are okay:

SFC Scan

1. Click on the Start button and in the search box, type Command Prompt
2. When you see Command Prompt on the list, right-click on it and select Run as administrator
3. When command prompt opens, copy and paste the following commands into it, press enter after each
   
   sfc /scannow
   
   Wait for this to finish before you continue
   
   copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
   
   
4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Tom

Those arrors are pretty much standard, AFAIK - try it on your own m/c :)
we already tried SFC ealrlier with no problems.

That seems to have done a fair amount of work!
Something must have tripped, somewhere?
- and there's no record of any earlier SFC scan

Please run another scan, and post the new log - it'll tell us if anything remains to be done.

Good.
.....

Code:

POQ 121 ends.
2012-11-02 13:12:24, Info                  CSI    000002e4 [SR] Verify complete
2012-11-02 13:12:24, Info                  CSI    000002e5 [SR] Repairing 0 components
2012-11-02 13:12:24, Info                  CSI    000002e6 [SR] Beginning Verify and Repair transaction
2012-11-02 13:12:24, Info                  CSI    000002e7 Repair results created:
POQ 122 starts:

POQ 122 ends.
2012-11-02 13:12:24, Info                  CSI    000002e8 [SR] Repair complete

It found nothing to repair this time.

Begs the question of what a CheckSUR may find (I don't think we ran one yet?)

Please run the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Method 2)

Then zip the CheckSUR.log and upload it to your public SkyDrive so I can take a look - post a link in your reply.

The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.