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
    2012-09-01T15:57:09+00:00

    I simply made a defrag run on my ssd and it worked ever since. Try that!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2012-08-31T17:30:04+00:00

    I had the same problem and it was fixed by deleting the the xml files and re-running.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2012-06-23T17:30:15+00:00

    Really! This won't work i even used the hotfix from microsoft

    http://support.microsoft.com/kb/2687862

    I get this when running Winsat Storage:

    Windows System Assessment Tool

    > Running: Feature Enumeration ''

    > Run Time 00:00:00.00

    > Running: Storage Assessment '-seq -read -n 0'

    > Run Time 00:00:02.95

    > Running: Storage Assessment '-ran -read -n 0'

    > Run Time 00:00:00.38

    > Running: Storage Assessment '-scen 2009 -drive C:'

    Error: Failed to properly assess the disk.

    The operation completed successfully.

    > Run Time 00:00:00.03

    > Disk  Sequential 64.0 Read                   249.23 MB/s          7.5

    > Disk  Random 16.0 Read                       214.32 MB/s          7.8

    > Total Run Time 00:00:04.11

    The log says:

    2663046 (3052) - winsat\logging.cpp:0815: --- START 2012\6\23 19:24:37 ---

    2663062 (3052) - winsat\main.cpp:4301: Command Line = winsat  diskformal

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

    2663062 (3052) - winsat\main.cpp:2490: > DWM Running.

    2663062 (3052) - winsat\main.cpp:2501: > leaving DWM on.

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

    2663187 (3052) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '777b0319-8bb4-4362-bc25-2259a21934dc'

    2663187 (3052) - winsat\main.cpp:2793: > power policy saved.

    2663218 (3052) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'

    2663218 (3052) - winsat\main.cpp:2814: > power policy set to maximum.

    2663531 (3052) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance

    2663531 (3052) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=FALSE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE

    2663531 (3052) - winsat\main.cpp:1775: > Run Assessment features

    2663781 (3052) - winsat\main.cpp:1775: > Run Assessment disk -seq -read -n 0

    2666734 (3052) - winsat\main.cpp:1775: > Run Assessment disk -ran -read -n 0

    2667109 (3052) - winsat\main.cpp:1775: > Run Assessment disk -scen 2009 -drive C:

    2667140 (3052) - storage\diskprof.cpp:2324: Unable to open temporary file.  Largest available contiguous space was: 11MB

    2667140 (3052) - storage\diskprof.cpp:0283: Error: Failed to properly assess the disk.

    The operation completed successfully.

    2667156 (3052) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 590

    2667156 (3052) - winsat\processresults.cpp:1498: > Wrote random read disk score to the registry 219463

    2667187 (3052) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 777b0319-8bb4-4362-bc25-2259a21934dc'

    2667187 (3052) - winsat\main.cpp:2855: > Power state restored.

    2667187 (3052) - winsat\main.cpp:2870: > Successfully reenabled EMD.

    2667203 (3052) - winsat\main.cpp:4909: > exit value = 0.

    it's something wrong with the Assessment disk -scen 2009 benchmark and im not alone.

    http://www.awesomes.net/?p=79

    I've made clean boots without 3rd party programs and removed the AV and all MS program to no avail.

    I use a Intel SSD G2 80gb but somehow WEI always return a score of 5.9 no matter what i do. It should be way higher than that.

    Was this answer helpful?

    0 comments