locked
Lenovo with i5 chip doesn't run Aero RRS feed

  • Question

  • For some reason this brand new computer doesn't run Aero by default.  How do you fix that?  How do you set a different theme in the Default profile anyway?  (after Sysprep)

     

    • Moved by Carey FrischMVP Wednesday, September 14, 2011 1:52 PM Moved to more appropriate forum category (From:Windows 7 Installation, Setup, and Deployment)
    Monday, September 12, 2011 5:16 PM

Answers

  • This seems to fix my case:

    reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat" /f /v VideoMemoryBandwidth /d 4756060    /t reg_dword
    reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat" /f /v VideoMemorySize      /d 1840447488 /t reg_dword

    Dwm checks for these during login, and disables Aero if they're set to 0.  They're supposed to be set during windows setup by winsat, but that doesn't always work.  Winsat is also run by Task Scheduler every Sunday (under Windows\Maintainence), but I would have to disable Deepfreeze and enable autologin for it to work and have permanent results.

     

    Hmm, I can run this over Session 0, but the computer still has to be logged in:

    schtasks /run /tn \microsoft\windows\maintenance\winsat
    pause

    • Marked as answer by JS2010 Tuesday, September 20, 2011 5:53 PM
    • Edited by JS2010 Tuesday, September 20, 2011 7:46 PM
    Tuesday, September 20, 2011 5:53 PM

All replies

  • Hi,

     

    I would like to know if you can enable Aero later. What did you mean of set a different theme in the default profile. Do you want to copy the default profile to other user profile?

     

    The Aero desktop experience is available in the Home Premium, Professional, Ultimate, and Enterprise editions of Windows 7. Please confirm your edition first.

     

    Then, please update your graphic card driver (video card driver) from manufacture's site and use Aero troubleshooter to narrow down the issue.

    http://windows.microsoft.com/en-US/windows7/open-the-aero-troubleshooter

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Wednesday, September 14, 2011 9:51 AM
  • Yes, I can enable Aero later.  I was asking how to set a theme in the Default profile, since every user that logs in creates a new profile.  This is Windows 7 Enterprise 64-bit.  I've tried upgrading the driver.  I will try the Aero troubleshooter.  I've found this in the Application logs:

    The Desktop Window Manager did not start because an analysis of the hardware
    and configuration indicated that it would perform poorly

    Wednesday, September 14, 2011 1:23 PM
  • Ok, the troubleshooter fixed it for the admin account, although I don't know how to script that.  But new users still don't get aero.  All it said was 'Desktop Window Manager was disabled.'

     

     


    • Edited by JS2010 Wednesday, September 14, 2011 5:48 PM
    Wednesday, September 14, 2011 5:47 PM
  • Hi,

     

    Since the application log is related to hardware, I suggest checking Windows Experienced Index rating. Click Start -> right click Computer -> Properties -> Windows Experience Index -> verify the Graphics score.

     

    If you want to set theme for default profile, it should be specified in the answer file. It will cause problem if you specify CopyProfile=true in the autounattend.xml.

     

    More information

    http://blogs.technet.com/b/deploymentguys/archive/2010/04/28/issues-with-copyprofile-and-windows-7-wallpaper.aspx

     

    http://support.microsoft.com/default.aspx?scid=kb;EN-US;973289

     

    Best Regards,

    Niki


    Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Edited by Niki Han Thursday, September 15, 2011 5:38 AM
    Thursday, September 15, 2011 5:38 AM
  • Actually rating the computer and rebooting fixed it.  Unless it was in combination with other things.  I'm not sure how to pull that off remotely.  I don't think I'll be reimaging them just to fix this with a different sysprep answer file.

    Aero is actually already set in the Default profile (HKCU\Software\Microsoft\Windows\CurrentVersion\Themes\CurrentTheme), and it's been working fine until this new model.  I see some failures in C:\Windows\Performance\WinSAT\winsat.log.  It seems impractical that it would rate the video card during boot.  Where do I get 'ThemeTool.exe' from?

    What's the registry entry that gets set when the test fails?

    Here's winsat.log, it's dated 8/17, run during windows setup?

    028298 (0968) - winsat\logging.cpp:0815: --- START 2011\8\17 19:10:08 PM ---
    028329 (0968) - winsat\main.cpp:4301: Command Line = "C:\Windows\system32\winsat.exe" moobe -cancelevent b72bb193-2ab7-46cb-a7b4-b21ff48bd519 -moobegoevent 40ff9c58-d1c5-4bb8-b950-76581ce6d848
    028360 (0968) - winsat\processwinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
    028501 (0968) - winsat\main.cpp:4474: > IsFormal=TRUE  IsMoobe=TRUE.
    028548 (0968) - winsat\main.cpp:4585: Watch dog system enabled
    028548 (0968) - winsat\main.cpp:4592: Main watch dog timer set to 60.0 seconds
    028672 (0968) - winsat\main.cpp:2505: > DWM not running.
    030763 (0968) - winsat\syspowertools.cpp:0983: > Read the active power scheme as '381b4222-f694-41f0-9685-ff5bb260df2e'
    030763 (0968) - winsat\main.cpp:2793: > power policy saved.
    030919 (0968) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c'
    030919 (0968) - winsat\main.cpp:2814: > power policy set to maximum.
    031184 (0968) - d3d\dx9misc.cpp:1030: HRESULT = 8876086a
    031184 (0968) - d3d\dx9misc.cpp:1030: Error: Unable to create the D3D device
    031184 (0968) - d3d\dx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created
    031200 (0968) - winsat\logging.cpp:1763: ERROR: pahse enter/leave imballance
    031200 (0968) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=TRUE  RanOverTs=FALSE  RanOnbatteries=FALSE
    031200 (0968) - winsat\main.cpp:1775: > Run Assessment features
    034367 (0968) - winsat\main.cpp:1775: > Run Assessment dwm -aname DWM -time 10 -fbc 10 -disp off -normalw 12 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock
    034491 (0968) - d3d\graphicsop.cpp:0263: Driver is not WDDM; aborting assessment.
    034913 (0968) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0
    034913 (0968) - winsat\main.cpp:2037: > DWM Assessment results processing SUCCESS
    034991 (0968) - winsat\processresults.cpp:4018: > Wrote video memory bandwidth to the registry 0
    034991 (0968) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability
    035006 (0968) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0
    035006 (0968) - winsat\main.cpp:0948: > IsOfficial=TRUE  IsFormal=TRUE  IsMoobe=TRUE  RanOverTs=FALSE  RanOnbatteries=FALSE
    035505 (0968) - winsat\processresults.cpp:1274: Limiting DWM Score to 1.0 - no DX9 capability
    035505 (0968) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0
    035755 (0968) - winsat\main.cpp:2339: > Finalized MOOBE key
    035771 (0968) - winsat\syspowertools.cpp:1015: > Set the active power scheme to 381b4222-f694-41f0-9685-ff5bb260df2e'
    035771 (0968) - winsat\main.cpp:2855: > Power state restored.
    035771 (0968) - winsat\main.cpp:2873: > Not necessary to reenable EMD cache.
    035958 (0968) - winsat\main.cpp:2899: INFO: DwmpRestartComposition() did not return OK!
    035958 (0968) - winsat\watchdog.cpp:0311: Watch dog system shutdown
    035958 (0968) - winsat\main.cpp:4909: > exit value = 0.



    • Edited by JS2010 Thursday, September 15, 2011 10:55 PM
    • Marked as answer by JS2010 Tuesday, September 20, 2011 5:51 PM
    • Unmarked as answer by JS2010 Tuesday, September 20, 2011 5:51 PM
    Thursday, September 15, 2011 2:54 PM
  • This seems to fix my case:

    reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat" /f /v VideoMemoryBandwidth /d 4756060    /t reg_dword
    reg add "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winsat" /f /v VideoMemorySize      /d 1840447488 /t reg_dword

    Dwm checks for these during login, and disables Aero if they're set to 0.  They're supposed to be set during windows setup by winsat, but that doesn't always work.  Winsat is also run by Task Scheduler every Sunday (under Windows\Maintainence), but I would have to disable Deepfreeze and enable autologin for it to work and have permanent results.

     

    Hmm, I can run this over Session 0, but the computer still has to be logged in:

    schtasks /run /tn \microsoft\windows\maintenance\winsat
    pause

    • Marked as answer by JS2010 Tuesday, September 20, 2011 5:53 PM
    • Edited by JS2010 Tuesday, September 20, 2011 7:46 PM
    Tuesday, September 20, 2011 5:53 PM
  • This is how a Dell Intel video driver installer enables Aero.  It puts this command in the 'runonce' registry key:

    'winsat dwm -xml results.xml'

    This can't be run remotely in the Session 0 window as the System user.

     


    • Edited by JS2010 Wednesday, October 5, 2011 9:27 PM
    Wednesday, October 5, 2011 9:26 PM