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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2010-11-02T23:15:25+00:00

    I am getting the same issue. 

    I don't even get to the scan my WEI. I have all the latest drivers and I am using a ASUS G72GX

    6Gb or RAM

    Nvidia 260M Graphics Card

    Dual Intel 2.6 Core Processor

    Here is the log:

    926755 (3780) - winsat\logging.cpp:0815: --- START 2010\11\2 23:11:28 ---

    926770 (3780) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent 204d2d08-5052-415b-b0cc-638efe43f3ac

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

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

    927129 (3780) - winsat\main.cpp:4505: ERROR: no multi-media files, no MM support

    927129 (3780) - winsat\main.cpp:2861: > no need to restore power state (no saver object).

    927145 (3780) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache.

    927316 (3780) - winsat\main.cpp:4909: > exit value = 10.

    I have tried the cmd sfc /scannow comes back with the message "Windows Resource did not find any integrity violations"

    Please could someone help!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2010-10-27T06:44:13+00:00

    I suggest you download and install the latest ATI radeon graphics card drivers from Dell or ATI web sites...Also, I suggest you read the following article:http://www.windows7library.com/blog/util/directx-tool/

    Was this answer helpful?

    0 comments
  3. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more