WEI - The Windows Experience Index for your system could not be computed.

Anonymous
2009-10-23T22:29:38+00:00

Hi,

Ive installed a clean copy of Windows7 64bit, on a formatted HD. I am unable to run WEI.

I updated the BIOS for my M3A79-T DELUXE to the latest (1303 rev). Installed all latest drivers for the hardware and latest Windows update.

I have ran c: CHKDSK /F /R /X (Ive seen on a website this has resolve the issue for one person) 

checked all hardware is installed ok and there are no conflicts in device manager.

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments
Answer accepted by question author
Anonymous
2009-10-24T11:13:49+00:00

Windows Experience Index has a log file "%SystemRoot%\Performance\WinSAT\winsat.log". That may give some relevant details.

I had the same error message and, in my case, the log file reported "Unable to save". It appears to have been Kaspersky Internet Security 2010 which was blocking WEI from saving the results. The complete WEI test ran OK and even flashed-up the 'completed' message but this was then immediately replaced with the "assessment could not be completed" message ... because it could not *save* the results.

Can I suggest you try another AV package? If you disconnect the network cable you could safely uninstall your existing AV package and see if WEI works again. If that resolves it, perhaps you need a different AV package from now on.

Personally, I found that Microsoft Security Essentials appears to not have this issue and I can now get my rating again. But I may try some other (try before you buy) packages to see what's best.

Worth a try?

Keith.

Was this answer helpful?

30+ people found this answer helpful.
0 comments
Answer accepted by question author
Anonymous
2009-11-05T17:14:05+00:00

Hello Everyone,

For those with Kaspersky and this issue, an article was recently released by Kaspersky with their fix for the issue:

http://support.kaspersky.com/faq/?qid=208280937

Thanks!

If you find that my answer was what you were looking for, please remember to click the "mark as answer" box below!

Was this answer helpful?

2 people found this answer helpful.
0 comments

66 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. Anonymous
    2012-06-07T03:12:27+00:00

    A very easy step,

    in the action center disable Windows firewall and try again, it works for me.

    thank you

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-03-29T11:53:59+00:00

    Hello, This is my error log, can anyone help

    488548 (2632) - winsat\logging.cpp:0815: --- START 2012\3\29 16:46:27 PM ---

    488548 (2632) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent c048464e-5c52-4e40-a929-c50193e551aa

    488548 (2632) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured

    488797 (2632) - winsat\main.cpp:4474: > IsFormal=TRUE  IsMoobe=FALSE.

    488844 (2632) - winsat\main.cpp:4585: Watch dog system enabled

    488844 (2632) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds

    489000 (2632) - winsat\main.cpp:2490: > DWM Running.

    489219 (2632) - winsat\main.cpp:2497: > turning off DWM.

    489219 (2632) - winsat\main.cpp:2470: > EMD service will be restored on exit.

    489609 (2632) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'

    489609 (2632) - winsat\main.cpp:2793: > power policy saved.

    489858 (2632) - winsat\syspowertools.cpp:1018: ERROR: Cannot set the current power scheme to '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c': The instance name passed was not recognized as valid by a WMI data provider.

    489858 (2632) - winsat\main.cpp:2810: ERROR: Can't set high power state.

    489889 (2632) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'

    489889 (2632) - winsat\main.cpp:2855: > Power state restored.

    489889 (2632) - winsat\main.cpp:2870: > Successfully reenabled EMD.

    490123 (2632) - winsat\watchdog.cpp:0311: Watch dog system shutdown

    490139 (2632) - winsat\main.cpp:4909: > exit value = 1.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-03-10T18:40:15+00:00

    Nope.  That's not it.  NVidia driver up to date.

    Was this answer helpful?

    0 comments