WinSAT Runs after Clean LTSB Install

Discussion in 'Windows 10' started by adric, Jun 12, 2017.

  1. adric

    adric MDL Addicted

    Jul 30, 2009
    536
    161
    30
    On a new install for W10 LTSB 2016, the first time the system shows the desktop, there is a cmd window that pops up showing the following:
    Code:
    Windows System Assessment Tool
    > Running: Feature Enumeration ''
    > Run Time 00:00:00.00
    > Running: WinSAT Direct3D Assessment '-aname DWM -time 10 -fbc 10 -disp off -normalw 1 -alphaw 2 -width 1280 -height 1024 -winwidth C(1144) -winheight C(915) -rendertotex 6 -rtdelta 3 -nolock'
    > Assessing Desktop Graphics Performance
    Shortly after that, it disappears. Anyxone know where this is being started from?

    I don't think it's from the task manager since it shows the task has not yet run (0x41303) and not scheduled to even run at all. Also, this seems to be a one-time thing after the initial install because it never happens again - only the first time the desktop gets accessed. I'm wondering why this is even running at all . I thought they got rid of this function for W10
     
  2. MrG

    MrG MDL Addicted

    May 31, 2010
    885
    213
    30
    I took a look at the WinSAT log file but don't see much on where it runs from (I got a raw set of WinSAT measurement data directly from the WinSAT tool on the command line. At an elevated command prompt: WinSAT formal)

    from log file @ C:\Windows\Performance\WinSAT\DataStore
    68825734 (12248) - exe\logging.cpp:0841: --- START 2017\6\12 7:22:04 AM ---
    68825734 (12248) - exe\main.cpp:4347: WinSAT registry node is created or present
    68825734 (12248) - exe\main.cpp:4378: Command Line = WinSAT formal
     
  3. NeoLojik

    NeoLojik MDL Novice

    Oct 13, 2009
    7
    5
    0
    The Intel GPU drivers usually cause this, chances are Windows is installing them for you automatically and then they trigger the WinSAT run.