locked
Windows Experience Index not working RRS feed

  • Question

  • Hello,

    I have been searching everywhere but with no success.

    I am currently having problems refreshing my WinSAT index score. Everytime I click the refresh button, it goes through the motions and then when it is about to finish it gives me an error stating,"Cannot complete because of error reported from the operating system, drivers or other component".

    I checked the error log and this is what it says,

    "785075 (1708) - winsat\main.cpp:2295: --- START 2008\11\4 13:43:35 PM ---
    785090 (1708) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    785090 (1708) - winsat\main.cpp:1974: > DWM Running.
    785340 (1708) - winsat\main.cpp:1987: > turning off DWM.
    785355 (1708) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    785355 (1708) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    785402 (1708) - winsat\main.cpp:2108: > power policy saved.
    785511 (1708) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    785527 (1708) - winsat\main.cpp:2120: > power policy set to maximum.
    786369 (1708) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    786369 (1708) - winsat\main.cpp:1161: > Running Assessment: features ''
    787212 (1708) - winsat\main.cpp:1436: > Assessment completed
    787212 (1708) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    913105 (1708) - winsat\main.cpp:1390: > DWM Assessment completed
    913120 (1708) - winsat\processresults.cpp:2109: > Wrote video memory bandwidth to the registry 4398880
    913120 (1708) - winsat\main.cpp:1408: > DWM Assessment results processing SUCCESS
    913120 (1708) - winsat\main.cpp:1436: > Assessment completed
    913136 (1708) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    925475 (1708) - winsat\main.cpp:1436: > Assessment completed
    925475 (1708) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    925475 (1708) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    929017 (1708) - winsat\main.cpp:1436: > Assessment completed
    929017 (1708) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    939266 (1708) - winsat\main.cpp:1436: > Assessment completed
    939266 (1708) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    949500 (1708) - winsat\main.cpp:1436: > Assessment completed
    949500 (1708) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    959671 (1708) - winsat\main.cpp:1436: > Assessment completed
    959671 (1708) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    969842 (1708) - winsat\main.cpp:1436: > Assessment completed
    969842 (1708) - winsat\main.cpp:1161: > Running Assessment: mem ''
    974975 (1708) - winsat\main.cpp:1436: > Assessment completed
    975021 (1708) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 0'
    975037 (1708) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    975037 (1708) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    975037 (1708) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    975053 (1708) - winsat\processresults.cpp:2606: Can't find assessed disk number in XML output
    975131 (1708) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    975146 (1708) - winsat\main.cpp:2155: > Power state restored.
    975146 (1708) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    975146 (1708) - winsat\main.cpp:2193: > Composition restarted
    975146 (1708) - winsat\main.cpp:3216: > exit value = 1.

    I do not know what that means or where to find a solution. I hope anyone can help with this problem. Thank You.

    Tuesday, November 4, 2008 1:08 PM

All replies

  • Have you checked the device manager to see if you are having some driver issues?  Make sure all your drivers are updated and try it again.  Let me know.
    Wednesday, November 5, 2008 1:09 PM
  • Have you checked your device manager for any driver conflicts.  I would do that and make sure all your drivers for your computer are up to date.  Then run it again.  Let me know how it works out.
    Wednesday, November 5, 2008 1:10 PM
  •   I am having the same issue but I am haveing a different failure ( DWM Assessment results processing FAILED) can anyone shed some light on this I did just install a vid card ATI HD 3850 and I have already installed drivers again and again also tried deleting the old winsat files and datastore files with no luck.

     HHHEeeeellpppp!!!!

    Wednesday, November 5, 2008 11:23 PM
  • Hi,

     

    The Indexing related issue occurs if one of the device driver is corrupt or not updated. Did the issue occur right after you installed the system, or it started to occur recently? If it occurred originally, the hard disk may not support Win SAT. You may need to contact the manufacturer of the hard disk to confirm this situation.

     

    If it started to occur recently, Kingv84, please let us know if you have installed any disc maintenance related programs. If so, please remove it and check the result. If the issue still occurs, I suggest that you boot in Clean Boot Mode.

     

    Clean boot

    =================

    Let’s disable all startup items and third party services when booting. This method will help us determine if this issue is caused by a loading program or service. Please perform the following steps:

     

    1. Click the Start Button type "msconfig" (without quotation marks) in the Start Search box, and then press Enter.

     

    Note: If prompted, please click Continue on the User Account Control (UAC) window.

     

    2. Click the "Services" tab, check the "Hide All Microsoft Services" box and click "Disable All" (if it is not gray).

    3. Click the "Startup" tab, click "Disable All" and click "OK".

     

    Then, restart the computer. When the "System Configuration Utility" window appears, please check the "Don't show this message or launch the System Configuration Utility when Windows starts" box and click OK.

     

    Please test this issue in the Clean Boot environment, if the issue disappears in the Clean Boot environment, we can use a 50/50 approach to quickly narrow down which entry is causing the issue.

     

    For more information about this step, please refer to the following KB article:

     

    How to troubleshoot a problem by performing a clean boot in Windows Vista

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

     

    If the issue still occurs in Clean Boot Mode, please let us know if the computer is from computer manufacturer.

     

    Mojoe, you may also check the log and try to find some clues. Kingv, could you let us know how exactly you launch the log?

    Thursday, November 6, 2008 6:47 AM
    Moderator
  • Yes acually I did install seagate disc wizard but I did uninstall since you sugested and restarted with no luck still I am trying your other steps now, thanks for any and all help.

     

    1637312 (3856) - winsat\main.cpp:2295: --- START 2008\11\6 9:24:21 AM ---
    1637359 (3856) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    1637359 (3856) - winsat\main.cpp:1974: > DWM Running.
    1637468 (3856) - winsat\main.cpp:1987: > turning off DWM.
    1637468 (3856) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    1637468 (3856) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '03a98a08-49ee-4ac8-92a6-f3abc67dcdf5'
    1637484 (3856) - winsat\main.cpp:2108: > power policy saved.
    1637562 (3856) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    1637578 (3856) - winsat\main.cpp:2120: > power policy set to maximum.
    1638359 (3856) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    1638359 (3856) - winsat\main.cpp:1161: > Running Assessment: features ''
    1639109 (3856) - winsat\main.cpp:1436: > Assessment completed
    1639156 (3856) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    1639687 (3856) - winsat\main.cpp:1390: > DWM Assessment completed
    1639703 (3856) - winsat\main.cpp:1406: > DWM Assessment results processing FAILED
    1639703 (3856) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    1639703 (3856) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    1648546 (3856) - winsat\main.cpp:1436: > Assessment completed
    1648546 (3856) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    1648546 (3856) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    1651062 (3856) - winsat\main.cpp:1436: > Assessment completed
    1651078 (3856) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    1661468 (3856) - winsat\main.cpp:1436: > Assessment completed
    1661468 (3856) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    1671609 (3856) - winsat\main.cpp:1436: > Assessment completed
    1671609 (3856) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    1681796 (3856) - winsat\main.cpp:1436: > Assessment completed
    1681796 (3856) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    1691921 (3856) - winsat\main.cpp:1436: > Assessment completed
    1691921 (3856) - winsat\main.cpp:1161: > Running Assessment: mem ''
    1697062 (3856) - winsat\main.cpp:1436: > Assessment completed
    1697109 (3856) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 1'
    1710296 (3856) - winsat\main.cpp:1436: > Assessment completed
    1710296 (3856) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 1'
    1714562 (3856) - winsat\main.cpp:1436: > Assessment completed
    1714562 (3856) - winsat\processresults.cpp:0672: Total physical mem available to the OS : 2.99 GB (3,217,928,192 bytes)
    1714562 (3856) - winsat\processresults.cpp:0965: No D3D results - limiting D3D Score to 1.0
    1714750 (3856) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 03a98a08-49ee-4ac8-92a6-f3abc67dcdf5'
    1714750 (3856) - winsat\main.cpp:2155: > Power state restored.
    1714750 (3856) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    1714765 (3856) - winsat\main.cpp:2193: > Composition restarted
    1714765 (3856) - winsat\main.cpp:3216: > exit value = 1.

    Thursday, November 6, 2008 5:38 PM
  •   I am still haveing this issue I actuall uninstalled my new videocard and put my old one back in and it still comes up with the same error. I also had forgoten about 1 more detail that could acually be very important about 3 months ago I had cloned my HD to a bigger drive and so this is actually probable ther cause but this is a drive that was already in the machine so I am not sure what I can do to check this.

     

    Monday, November 10, 2008 5:03 PM
  • Hi,

     

    It could be a reason that information of hard drive cannot be collected. However, the failure of collecting the video card information should not be caused by it. Maybe Desktop Window Manager is blocked when it collect information from hardware. I suggest that you temporary uninstall the anti-virus and firewall. After that, please try to refresh the Index information again.

    Tuesday, November 11, 2008 9:46 AM
    Moderator
  • Hi Arthur,

    I did exactly what you recommended, I still got the same error in the clean boot. The computer is an HP Desktop running Windows Vista Home Premium 64 Bit. It is a purchased copy from MS not the OEM copy that was installed before.

    To get to the log just go to C:\Windows\Performance\WinSAT\winsat.log


    This is what I got in the log after the clean boot you recommended.

    277853 (3352) - winsat\main.cpp:2295: --- START 2008\11\11 17:20:51 PM ---
    278399 (3352) - winsat\main.cpp:2567: > IsFormal=TRUE  IsMoobe=FALSE.
    278399 (3352) - winsat\main.cpp:1974: > DWM Running.
    278664 (3352) - winsat\main.cpp:1987: > turning off DWM.
    278664 (3352) - winsat\main.cpp:2051: > EMD device detected to be on.  EMD will be restored on exit.
    278664 (3352) - mlib\syspowertools.cpp:0872: > Read the active power scheme as '8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    278758 (3352) - winsat\main.cpp:2108: > power policy saved.
    278836 (3352) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    278960 (3352) - winsat\main.cpp:2120: > power policy set to maximum.
    279787 (3352) - winsat\main.cpp:2756: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=FALSE  RanOverTs=FALSE  RanOnbatteries=FALSE
    279818 (3352) - winsat\main.cpp:1161: > Running Assessment: features ''
    280536 (3352) - winsat\main.cpp:1436: > Assessment completed
    280552 (3352) - winsat\main.cpp:1161: > Running Assessment: graphicsformal ' -wddm'
    319521 (3352) - winsat\main.cpp:1390: > DWM Assessment completed
    319536 (3352) - winsat\processresults.cpp:2109: > Wrote video memory bandwidth to the registry 4492130
    319552 (3352) - winsat\main.cpp:1408: > DWM Assessment results processing SUCCESS
    319552 (3352) - winsat\main.cpp:1436: > Assessment completed
    319552 (3352) - winsat\main.cpp:1161: > Running Assessment: media '-input {winsatencode.wmv} -encode {winsat.prx}'
    331751 (3352) - winsat\main.cpp:1436: > Assessment completed
    331751 (3352) - winsat\main.cpp:1161: > Running Assessment: moobego ''
    331751 (3352) - winsat\main.cpp:1161: > Running Assessment: mfmedia '-input {winsat.wmv} -nopmp'
    336837 (3352) - winsat\main.cpp:1436: > Assessment completed
    336837 (3352) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption'
    347461 (3352) - winsat\main.cpp:1436: > Assessment completed
    347476 (3352) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression'
    357694 (3352) - winsat\main.cpp:1436: > Assessment completed
    357694 (3352) - winsat\main.cpp:1161: > Running Assessment: cpu '-encryption2'
    367819 (3352) - winsat\main.cpp:1436: > Assessment completed
    367819 (3352) - winsat\main.cpp:1161: > Running Assessment: cpu '-compression2'
    377974 (3352) - winsat\main.cpp:1436: > Assessment completed
    377974 (3352) - winsat\main.cpp:1161: > Running Assessment: mem ''
    383060 (3352) - winsat\main.cpp:1436: > Assessment completed
    383122 (3352) - winsat\main.cpp:1161: > Running Assessment: disk '-seq -read -n 0'
    383122 (3352) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    383122 (3352) - winsat\main.cpp:1161: > Running Assessment: disk '-flush -n 0'
    383122 (3352) - winsat\main.cpp:1430: > Assessment FAILED due to an error
    383122 (3352) - winsat\processresults.cpp:2606: Can't find assessed disk number in XML output
    383200 (3352) - mlib\syspowertools.cpp:0904: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    383200 (3352) - winsat\main.cpp:2155: > Power state restored.
    383200 (3352) - winsat\main.cpp:2171: > Successfully reenabled EMD.
    383200 (3352) - winsat\main.cpp:2193: > Composition restarted
    383200 (3352) - winsat\main.cpp:3216: > exit value = 1.

    Am totally lost, I checked all my drivers and I have all of it updated according to Vista. This error just started recently. I have not installed any new hardware or software since I started getting this problem. The system was a clean install and worked great till recently the WinSat could not refresh because of the Disk Assessment error. If you read the last red line, it says something about not being able to find the assessed disk number in XML output. I hope MS finds a solution or maybe when I install Windows 7 in the future it will disappear.

    I keep trying to find a solution and try to post back here. Thanks guys for all your solutions.


    Tuesday, November 11, 2008 4:31 PM
  •   I also did what you sugested with no luck I am doing a CHKDSK on my drives now to see if this will fix any issues I will let ya know what happens thanks.

    Tuesday, November 11, 2008 7:52 PM
  •  Mojoe2 wrote:

      I also did what you sugested with no luck I am doing a CHKDSK on my drives now to see if this will fix any issues I will let ya know what happens thanks.



    Did you have any luck with CHKDSK Mojoe2? I have not tried CHKDSK myself yet but I will give it a shot too. Am still in the same loop with the assessment errors. I really do not want to erase vista and reinstall. I rather live with the problem till Windows 7 comes out and i install that over my Windows Vista copy.


    I let you guys know if I have any luck.


    Friday, November 14, 2008 3:29 PM
  •   No Kingv it did not I did all 3 drives and it took like 3 hours but it did not work sorry for not posting that info.

    Friday, November 14, 2008 4:34 PM
  • Mine was failing with that error as well and no where could I find what was causing it.
    Then I tried to use Acronis to make a backup.... but it wouldn't run... it looked at the partitions on my hard drives and it would report sector errors on my C: drive and fail. 

    After moving my system to another drive I tested the bad one to find that I couldn't format the drive.  I could repartition it or remove and add partitions but never could format the bottom partition. After removing the drive competely from my system th Windows Experience index worked again and my backup software also worked.  
    Thursday, May 14, 2009 4:05 PM
  • The answer to your question is few steps away.  Windows 7 N and Windows 7 KN editions include the same functionality as Windows 7, except that these versions of Windows do not include Windows Media Player, and related technologies.

    End-user customers can enable the media functionality to work properly by installing the Windows Media Feature Pack for Windows 7 N and Windows 7 KN (KB968211).
    Simply download and install Windows Media Player for Windows 7.  After the installation is complete, run the Windows Experience Index again.  The file name is :

    Media Feature Pack for Windows 7 N and Windows 7 KN (KB968211)

    http://www.microsoft.com/downloads/details.aspx?FamilyID=31017ed3-166a-4c75-b90c-a6cef9b414c4&displaylang=en&Hash=ZqjbrOmpRL8pmDZD3ivprfUO9WHNf0F0lPqNctQEm0%2fX2yID620MsO83e2PlyWbL5AJfWwNOcNdai3GlhCNImg%3d%3d

     

    Monday, August 16, 2010 5:24 AM
  • The answer to your question is few steps away.  Windows 7 N and Windows 7 KN editions include the same functionality as Windows 7, except that these versions of Windows do not include Windows Media Player, and related technologies.

    End-user customers can enable the media functionality to work properly by installing the Windows Media Feature Pack for Windows 7 N and Windows 7 KN (KB968211).
    Simply download and install Windows Media Player for Windows 7.  After the installation is complete, run the Windows Experience Index again.  The file name is :

    Media Feature Pack for Windows 7 N and Windows 7 KN (KB968211)

    http://www.microsoft.com/downloads/details.aspx?FamilyID=31017ed3-166a-4c75-b90c-a6cef9b414c4&displaylang=en&Hash=ZqjbrOmpRL8pmDZD3ivprfUO9WHNf0F0lPqNctQEm0%2fX2yID620MsO83e2PlyWbL5AJfWwNOcNdai3GlhCNImg%3d%3d
    Monday, August 16, 2010 5:34 AM
  • Hi, Authur,

    I have a Windows Experience Index rating problem too.  I checked the winsat.log  ----

    4897486 (6012) - winsat\logging.cpp:0815: --- START 2010\12\9 18:45:16 PM ---
    34897486 (6012) - winsat\main.cpp:4301: Command Line = winsat  formal -v
    34897486 (6012) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
    34897501 (6012) - winsat\main.cpp:4474: > IsFormal=TRUE  IsMoobe=FALSE.
    34897548 (6012) - winsat\main.cpp:4585: Watch dog system enabled
    34897548 (6012) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
    34897782 (6012) - winsat\main.cpp:2490: > DWM Running.
    34898000 (6012) - winsat\main.cpp:2497: > turning off DWM.
    34898000 (6012) - winsat\main.cpp:2470: > EMD service will be restored on exit.
    34898234 (6012) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    34898234 (6012) - winsat\main.cpp:2793: > power policy saved.
    34898250 (6012) - 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.
    34898250 (6012) - winsat\main.cpp:2810: ERROR: Can't set high power state.
    34898266 (6012) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    34898266 (6012) - winsat\main.cpp:2855: > Power state restored.
    34898266 (6012) - winsat\main.cpp:2870: > Successfully reenabled EMD.
    34898281 (6012) - winsat\watchdog.cpp:0311: Watch dog system shutdown
    34898281 (6012) - winsat\main.cpp:4909: > exit value = 1.

    34910746 (4648) - winsat\logging.cpp:0815: --- START 2010\12\9 18:45:30 PM ---
    34910746 (4648) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" formal -cancelevent a2b99556-80dd-4470-b3bf-71260b3f2a92
    34910746 (4648) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
    34910761 (4648) - winsat\main.cpp:4474: > IsFormal=TRUE  IsMoobe=FALSE.
    34910808 (4648) - winsat\main.cpp:4585: Watch dog system enabled
    34910808 (4648) - winsat\main.cpp:4600: Main watch dog timer set to 600.0 seconds
    34911042 (4648) - winsat\main.cpp:2490: > DWM Running.
    34911276 (4648) - winsat\main.cpp:2497: > turning off DWM.
    34911276 (4648) - winsat\main.cpp:2470: > EMD service will be restored on exit.
    34911510 (4648) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    34911510 (4648) - winsat\main.cpp:2793: > power policy saved.
    34911510 (4648) - 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.
    34911510 (4648) - winsat\main.cpp:2810: ERROR: Can't set high power state.
    34911526 (4648) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    34911526 (4648) - winsat\main.cpp:2855: > Power state restored.
    34911526 (4648) - winsat\main.cpp:2870: > Successfully reenabled EMD.
    34911541 (4648) - winsat\watchdog.cpp:0311: Watch dog system shutdown
    34911541 (4648) - winsat\main.cpp:4909: > exit value = 1.

    I did the clean boot, with only the windows services, the problem still exist. 

    I bought this HP dv6 notebook from HP last month,  it came with Windows 7 Home premium 64-bit, and I upgrade it to Windows 7 Ultimate 64-bit.  The software is genuine microsoft product.

    the problem seems to be "can't set high power state".  I uninstalled HP power manager, it didn't work.  I uninstall, re-install Graphics card driver, and a bunch other drivers (BIOS, chipset and etc.), no help.

    If you have any suggestions, please do tell.  Thanks.

     

    Friday, December 10, 2010 12:54 AM
  • I have the solution for you. I also have a HP dv6 series laptop, installed a fresh new windows on it and could not index windows. Took me a while to find a solution but finaly found one!

    The problem is it want's to change the power plan to high performance to get the maximum out of your laptop for testing, but it's missing by default! Normaly you can restore all the power plans but if you do so it does not restore the high performance power plan. Stil a key in the registry exists with the default high performance plan.

    What i did:

    1. Open regedit and browse to: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Power\User\PowerSchemes.
    2. Right click the folder (key) and choose permissions, there give yourself Full Control.
    3. Copy the default high performance power plan from HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Power\User\Default\PowerSchemes called {8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c}. I had to do this manualy because it gave me an error when I exported the key under default and imported into User\PowerSchemes. But manualy worked for me.

    Then run Windows Index and it runs!

    Friday, October 14, 2011 2:55 PM