Well, it still doesn't work. Here is the events:
Vino's Event Viewer v01c run on Windows 2008 in English
Report run at 30/12/2011 9:21:59 AM

Note: All dates below are in the format dd/mm/yyyy

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 23/06/2011 10:18:06 AM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Virtual PC 2007, from vendor Microsoft) was hard-blocked and raised the following: Virtual PC 2007 is not supported on this version of Windows. For more information, contact Microsoft.

Log: 'Application' Date/Time: 23/06/2011 10:17:40 AM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Virtual PC 2007, from vendor Microsoft) was hard-blocked and raised the following: Virtual PC 2007 is not supported on this version of Windows. For more information, contact Microsoft.

Log: 'Application' Date/Time: 23/06/2011 10:16:42 AM
Type: Critical Category: 0
Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
The application (Virtual PC 2007, from vendor Microsoft) was hard-blocked and raised the following: Virtual PC 2007 is not supported on this version of Windows. For more information, contact Microsoft.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'Application' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'Application' Date/Time: 30/12/2011 2:23:34 AM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 28/12/2011 11:39:23 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 28/12/2011 7:31:32 PM
Type: Error Category: 0
Event: 12293 Source: VSS
Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is snapshotted. [0x8000ffff] [hr = 0x8000ffff, Catastrophic failure ].

Log: 'Application' Date/Time: 28/12/2011 7:31:11 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Faulting module name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Exception code: 0xc0000005 Fault offset: 0x00001883 Faulting process id: 0xa78 Faulting application start time: 0x01ccc597255afff7 Faulting application path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Faulting module path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Report Id: 7f577c31-318a-11e1-a467-08002700ecd3

Log: 'Application' Date/Time: 28/12/2011 4:15:28 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Faulting module name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Exception code: 0xc0000005 Fault offset: 0x0000174c Faulting process id: 0x5d4 Faulting application start time: 0x01ccc57be8d2b9a0 Faulting application path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Faulting module path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Report Id: 27f334eb-316f-11e1-a467-08002700ecd3

Log: 'Application' Date/Time: 28/12/2011 2:19:20 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0x388 Faulting application start time: 0x01ccc56afd1d5092 Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: ee4b64bc-315e-11e1-a467-08002700ecd3

Log: 'Application' Date/Time: 28/12/2011 1:12:50 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xff8 Faulting application start time: 0x01ccc561b309fd43 Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: a41568d4-3155-11e1-b747-08002700ecd3

Log: 'Application' Date/Time: 28/12/2011 12:41:03 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xcb4 Faulting application start time: 0x01ccc55d3e94f67a Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 334aeec7-3151-11e1-98db-08002700ecd3

Log: 'Application' Date/Time: 24/12/2011 6:49:29 PM
Type: Error Category: 101
Event: 1002 Source: Application Hang
The program Explorer.EXE version 6.1.7601.17567 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: a8c Start Time: 01ccc1744e8197d4 Termination Time: 0 Application Path: C:\Windows\Explorer.EXE Report Id: f9f83951-2e5f-11e1-ad49-08002700ecd3

Log: 'Application' Date/Time: 23/12/2011 2:29:17 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 23/12/2011 1:16:59 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xdf4 Faulting application start time: 0x01ccc174730989ca Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 64c3fc8e-2d68-11e1-ad49-08002700ecd3

Log: 'Application' Date/Time: 21/12/2011 11:25:32 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 21/12/2011 12:36:54 AM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 19/12/2011 10:30:59 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 19/12/2011 7:09:50 PM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xd68 Faulting application start time: 0x01ccbe81144ff91e Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 05929130-2a75-11e1-a8bb-08002700ecd3

Log: 'Application' Date/Time: 19/12/2011 3:27:26 PM
Type: Error Category: 0
Event: 4003 Source: NovaBACKUP
My Backup 2012 [Completed with errors], Monday, December 19, 2011 Objects Selected : 31
Bytes Selected : 121.51 MB
Objects Completed : 2
Bytes Completed : 30.51 MB
Start Time : 12/19/2011, 5:25:19 PM
End Time : 12/19/2011, 5:27:26 PM
Elapsed Time : 00:02:07
3 Informational message(s), 1 warning(s), 1 error(s)
Log file: C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Logs\4eef575f.txt

Log: 'Application' Date/Time: 18/12/2011 10:30:47 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 17/12/2011 10:30:47 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 16/12/2011 10:30:47 PM
Type: Error Category: 0
Event: 72 Source: SideBySide
Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

Log: 'Application' Date/Time: 16/12/2011 10:16:10 AM
Type: Error Category: 100
Event: 1000 Source: Application Error
Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xe28 Faulting application start time: 0x01ccbbdb07a1a929 Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: f9704267-27ce-11e1-a472-08002700ecd3

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Critical Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 08/12/2011 1:45:15 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 15/08/2011 4:45:38 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 09/08/2011 12:48:24 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 05/08/2011 1:32:10 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 02/08/2011 10:04:28 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 16/07/2011 11:35:32 AM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 03/07/2011 1:59:49 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Log: 'System' Date/Time: 18/06/2011 7:22:26 PM
Type: Critical Category: 63
Event: 41 Source: Microsoft-Windows-Kernel-Power
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'System' Log - Error Type
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Log: 'System' Date/Time: 28/12/2011 2:14:18 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 28/12/2011 2:13:00 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Diagnostic Policy Service service terminated with the following error: Access is denied.

Log: 'System' Date/Time: 28/12/2011 2:12:46 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 28/12/2011 1:44:23 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 28/12/2011 1:43:47 PM
Type: Error Category: 2
Event: 55 Source: Ntfs
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7.

Log: 'System' Date/Time: 28/12/2011 1:43:45 PM
Type: Error Category: 2
Event: 55 Source: Ntfs
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7.

Log: 'System' Date/Time: 28/12/2011 1:43:44 PM
Type: Error Category: 2
Event: 55 Source: Ntfs
The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7.

Log: 'System' Date/Time: 28/12/2011 1:07:48 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 28/12/2011 1:06:54 PM
Type: Error Category: 0
Event: 3002 Source: Microsoft Antimalware
Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

Log: 'System' Date/Time: 28/12/2011 1:06:37 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Diagnostic Policy Service service terminated with the following error: Access is denied.

Log: 'System' Date/Time: 28/12/2011 1:06:23 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 28/12/2011 1:06:16 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 28/12/2011 12:35:50 PM
Type: Error Category: 0
Event: 10016 Source: Microsoft-Windows-DistributedCOM
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

Log: 'System' Date/Time: 28/12/2011 12:35:49 PM
Type: Error Category: 0
Event: 7022 Source: Service Control Manager
The NovaStor NovaBACKUP Backup/Copy Engine service hung on starting.

Log: 'System' Date/Time: 28/12/2011 12:34:21 PM
Type: Error Category: 0
Event: 7023 Source: Service Control Manager
The Diagnostic Policy Service service terminated with the following error: Access is denied.

Log: 'System' Date/Time: 28/12/2011 12:34:10 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 28/12/2011 12:34:05 PM
Type: Error Category: 0
Event: 46 Source: volmgr
Crash dump initialization failed!

Log: 'System' Date/Time: 24/12/2011 6:49:42 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk3\DR8.

Log: 'System' Date/Time: 24/12/2011 6:49:42 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk3\DR8.

Log: 'System' Date/Time: 24/12/2011 6:49:41 PM
Type: Error Category: 0
Event: 11 Source: Disk
The driver detected a controller error on \Device\Harddisk3\DR8.

the hard drive errors are probably because my external hdd isn't working very well.

Thanks for all the help

The Event viewer logs don't seem to show anything helpful

I also tried looking further into MTP/WPD drivers, their installs, dependencies, etc. but frankly the more I try to look and read, the more it makes my head spin! :dead: I'm sorry to say i don't think i can help fix your MTP driver problems

Since it looks like your disk is also having errors, a clean reinstall on a new disk may be the best advice
> An easy tool to look at your disk health status HERE
> Also, before doing a fresh reinstall, make sure you know any activation IDs needed to reactivate any paid software you may need to reinstall that will need reactivating

For future (to avoid reinstalls) you might periodically create disk image backups (so you can then restore a disk image of a working system). In general, I create a disk image backup every 3 months. I do data backups more frequently. Then it's a matter of you restoring the disk image followed by restoring your most recent data backup on top of the disk image restore
I use Acronis True Image but EASUS ToDo Backup is a good freeware tool as well

/* EDIT */
We can still try to uninstall old MTP stuff still not yet removed if you;d like, but to repeat, it's best to only try that if you have everything backed up. I would GUESS that wouldn't make things any worse but can't guarantee as there's still much about MTP i don't understand. If you should want to try, run another DevManView for me so i can see what's still there and i can give you instruction

Well, I don't have a backup, because I couldn't get it to backup all files and then update them each time, not overwrite or create a new backup. I should select "Differential" instead of "Incremental", right?
Another question: Do I need to back up all my files or just drive C:?

I don't think I am ready to do a clean install, I think I should reinstall or clone drive c: when I get another HDD (500GB just isn't enough). I can't get a new one untill the prices go down; Samsung 1TB currently costs 2.5x the original price!

I still think we should try again and if I still have this problem when I get a new HDD, I will do a clean install.
I think that we should remove the Microsoft VirtualPC drivers, because I use VirtualBox now instead.

1) Please re-run DevManView. (see See [post=939115]How To Report Your Computer's Device Manager Data[/post])
I need its output saved as either "tabular text" or "comma delimited text". I can import those formats into Excel which makes it easy for me to manipulate and sort as columnar data (such as by Device Type).

2. Hmm... Looks like EASUS released a new version of their backup tool since the last time i used it. I just did a quick look at their new version
> Incremental vs. Differential will both create subsequent backups. (The difference is how they do it) Go ahead and use Incremental (Incrementals will use less space)
> So do a full backup of your data. Then try incremental backups of your data
> I notice EASUS will create a .PDB backup file for each backup. If you double click a backup file you can "explore" the backup and it should reflect the files at the time of the backup.

If you also have the space to save a single backup of your C: drive, it helps assure you have everything as of "today" and can restore the full partition if needed. But whether you want to do it as well is up to you. I do things like that just to be extra cautious if the hard drive should unexpectedly fail.. then you have something you can also restore if need be

/* EDIT */
Oh. on that note, also click their Tools->Create rescue CD (or some similar name, i forget). This creates a rescue CD you can boot from the rescue CD if the hard drive should ever unexpectedly fail so you can restore to a new, empty disk if ever needed

I attached the new DevManView file.

About backing up: My external HDD isn't working well. If Windows starts up with the drive connected, it doesn't work, and reconnecting doesn't help. If I disconnect it and reboot, it works well, unless I reconnect it. I think this is because it is a 3.5" HDD with a USB to IDE/SATA adapter, and this adapter probably doesn't work properly.
Another thing: I have some files on my external HDD because I don't have enough internal HDD space. Does EASEUS support compression? If not, I will try to come up with a solution for this.

Pretty sure EASUS supports compression. Look under Backup Options

Here's my approach for what we try next (this is pretty much it before i think best giving up). More detail on these steps below
1. We'll first uninstall any programs you might have from Nokia (e.g. you still have Nokia Ovi installed?)
2, Then we’ll uninstall devices (and their drivers) still found in Device Manager for: all the WPD (Windows Portable) devices and anything else from Nokia
3. Then you download, reinstall the latest Nokia Ovi and finally try connecting your Nokia again

Again, I THINK is OK to uninstall all these devices. But I can’t guarantee. So choose to proceed at your own risk

First, Check Ctl Panel->Programs and Features Do you have any Nokia software installed? Also check if more then one Nokia item (just as we found Samsung Kies also had multiple items under Programs/features)

Now to Device Manager. First, some notes on using DevManView to help uninstall. DevManView can uninstall one or more selected devices at a time
> You simply select the device(s) you want to uninstall then File->Uninstall Selected Devices
> To select more then one entry use Ctrl-Left Click to select or de-select a device

Open DevManView. Click on the column header DeviceTypeCode to sort by Type. Scroll to select and uninstall (you can select one or more at a time as convenient for you. just uninstall them all by the time you;re done)
> All devices with DeviceTypeCode = WPD
> All devices with DeviceTypeCode = Wireless Communication. (these are also all Nokia devices. Not to worry. Your other wireless devices don’t use this same type code)
> Also look for typecode = either Ports or Modem. Look for any device name with Nokia in its name. Uninstall it

That should clean up all left behind. Try installing latest version of Ovi and try your Nokia phone again. g;luck

Well, it still doesn't work. Yes, I am giving up now but I have one more question:
Can I repair my windows installation instead of doing a clean install? I read that you can do that in the PCWorld magazine.

Try the repair install. Post back to let us know if it helped