Enable AERO on Windows 7 64-bit systems during OS Deployment using Configuration Manager


If you wish to deploy Windows 7 32-bit using Configuration Manager, and you need to enable AERO during deployment, you needs to add a “Run Command Line” step to the Task Sequence with the following command:

WinSAT.exe formal

If you do the same while deploying Windows 7 64-bit, the step will fail. The is due to the File System  Redirector, and the fact that the Tack Sequence is running in 32-bit context.

To workaround this minor issue, make sure that you select Disable 64-bit file system redirection, on this step.


About Author

My name is Ronni Pedersen and I'm currently working as a Cloud Architect at APENTO in Denmark. My primary focus is Enterprise Client Management solutions, based on technologies like AzureAD, Intune, EMS and System Center Configuration Manager. I'm is also a Microsoft Certified Trainer and Microsoft MVP in Enterprise Mobility.


  1. I am running MDT 2010 Update 1, but I do not see the same options for “Run Command Line” that you do, namely:

    “Disable 64-bit file system redirection”
    “Time-out (minutes):”

    Therefore, I can’t do this fix, but still can’t get the deployment to turn on Aero. What did you do to have those options enabled? I’ve installed MDT2010 on different systems, and I have never seen them.

  2. I’m not sure if you got my comment, so I’ll try again…

    The option of “Disable 64-bit file system redirection” is not there in MDT2010 Update 1. How did you get that option?

  3. Hi Ronni,

    do you have a tip for running winsat.exe formal from SCCM 2012 Task Sequence? I cannot make it work :(. I have tried it also without option “Disable 64-bit file system redirection” enabled.

    Here is the content of c:WindowsPerformanceWinSATwinsat.log

    68459307 (9532) – winsatmain.cpp:4301: Command Line = “WinSAT.exe” formal
    68459307 (9532) – winsatprocesswinsaterror.cpp:0095: ERROR: tried to read resource strings, unknown exception occured
    68460024 (9532) – winsatmain.cpp:2505: > DWM not running.
    68460523 (9532) – winsatsyspowertools.cpp:0983: > Read the active power scheme as ‘8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c’
    68460523 (9532) – winsatmain.cpp:2793: > power policy saved.
    68460851 (9532) – winsatsyspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c’
    68460851 (9532) – winsatmain.cpp:2814: > power policy set to maximum.
    68461709 (9532) – d3ddx9misc.cpp:1030: HRESULT = 8876086c
    68461725 (9532) – d3ddx9misc.cpp:1030: Error: Unable to create the D3D device
    68461725 (9532) – d3ddx9misc.cpp:1030: Error: Unable to check the capabilities of the video card because a d3d device could not be created
    68461725 (9532) – winsatlogging.cpp:1763: ERROR: pahse enter/leave imballance
    68461787 (9532) – winsatsyspowertools.cpp:1015: > Set the active power scheme to 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c’
    68461787 (9532) – winsatmain.cpp:2855: > Power state restored.
    68461787 (9532) – winsatmain.cpp:2873: > Not necessary to reenable EMD cache.
    68462005 (9532) – winsatmain.cpp:4909: > exit value = 1.

    What is interesting is that if I run winsat.exe formal from elevated CMD(Run as administrator) full set of assesments successfully run.

Leave A Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.