Como posso desativar os avisos de desempenho Aero do Windows 7?

Sometimes this dialog box will pop up (see screenshot above). Every time it appears I select “Keep the current color scheme, and don’t show this message again”. Windows then reminds me again - either the next day or after reboot, or sometimes another 5 minutes later

Do you want to change the color scheme to improve performance?

Windows has detected your computer’s performance is slow. This could be because there are not enough resources to run the Windows Aero color scheme. To improve performance, try changing the color scheme to Windows 7 Basic. Any change you make will be in effect until the next time you log on to Windows

• Change the color scheme to Windows 7 Basic
• Keep the current color scheme, but ask me again if my computer continues to perform slowly
• Keep the current color scheme, and don’t show this message again

Is there some reason why Windows is ignoring/forgetting my attempts to suppress the dialog? I’d love to never ever see it again, it’s annoying, and it alt-tabs me out of fullscreen applications.

If it matters, I’m running Windows 7 x64 Professional. I believe the dialog appears because I’m forcing Vsync and Triple Buffering for DirectX applications.

Assuming you realize this message is informing you your system is low on resources and is asking you to disable Aero so it can keep performing at optimum speed,

1. Go to the Start Menu and type Action Center on the Search box
2. Start it (it should be the top entry, under the “Control Panel” group)

3. On the left sidebar, click

   Change Action Center settings

4. Desmarque o

   Windows Troubleshooting

   caixa de seleção, em “Mensagens de Manutenção”.

5. Clique no

   Ok

   botão e você está feito.

Aqui está uma captura de tela da tela de configuração:



• Você pode tentar manter essa configuração exatamente como está e alternar para o modo de área de trabalho básica antes de iniciar os aplicativos que normalmente acionarão essa notificação da Central de Ações. Ou,

• Você pode clicar com o botão direito nos ícones que você usa para ativar esses aplicativos de tela cheia, clicando em propriedades e na guia Compatibilidade

  Disable desktop composition

  . Isso desativará oGerenciador de sessão do Gerenciador de janelas da área de trabalho serviço durante a execução desta aplicação, que irá aumentar a memória do sistema e vídeo e evitar algumas incompatibilidades de aplicativos. Uma causa provável para a sua mensagem da Central de Ações se você tiver memória de vídeo e sistema suficiente, mas estiver recebendo esta mensagem com certos jogos ou aplicativos de tela inteira.

Outro colaborador, Oliver Salzburg, mergulha na solução Disable Desktop Composition. Um Dwarf destaca no final. Ele escreve:

I’m constantly in a similar situation even though I never get that exact same message, and have done a bit of testing around.

To my understanding, the core resource that is under stress here, is the GPU memory. But this doesn’t necessarily indicate that you’re running out of this resource in general. It might just mean the Desktop Window Manager has detected that you’re running so low that one specific feature of this service could be disabled to free up more memory.

To test this, I started opening up GPU memory intensive applications:



I had to push a bit further and start a couple more Visual Studio instances…







Now, when I’m already at a critical level, and I start an application that uses excessive amounts of GPU memory in fullscreen, I can even go beyond this critical limit. Here’s the result after running Black Mesa for a while on 2560×1440 at max details:



So, two things can be deducted from this. While going over the 75% mark on the desktop can force Windows to disable desktop composition, when reaching the same limit in a fullscreen application (and, optionally exiting that application) desktop composition is not disabled. The second thing is, while you’re in your game, you can get the idea “Hey, I have enough resources to run this game, why don’t I have enough resources for the desktop?”. The reason is, both require memory at the same time.

Windows might only be able to tell you about the memory situation after you exited the game. So, when I start another Visual Studio after exiting Black Mesa…



Get more GPU memory

Sweet and simple.

Disable Desktop Composition (per process)

As was already suggested, you can disable desktop composition for a single executable. This has the effect that desktop composition is temporarily disabled while the executable is being executed. This drastically reduced the overall memory consumption while the application is executed in my tests:



Disable Desktop Composition (globally)

I wouldn’t consider this a solution as desktop composition is usually desired. But this is where to disable it:



I just want to get rid of the annoying message!

Just because you remove the warning “ Your battery is almost empty! You can only talk for 10 more minutes! ” does not mean you can talk for longer than 10 minutes. In fact, your phone will most likely simply shut off and that’s it. Now how’s that for an improvement?

I never assumed the message can be turned off and I don’t see how that could be considered a benefit.

You might think you know better, but you don’t. If the system is telling you it’s running out of resources, it is.

But it isn’t! I know!

Ok, let’s assume Windows is just not smart enough to detect the special situation you’re in and the warning message is simply an annoying inconvenience. What now?

The thing is, me personally, I’m also affected by this and it’s annoying the hell out of me. Because I don’t even get that warning message. Windows simply switches my color profile and that’s it. And I like that actually.

When it happens I usually quickly run a script that calls

net stop uxsms & net start uxsms

Isso reinicia o Desktop Window Manager e me traz de volta à minha área de trabalho composta (e libera muitos recursos no processo, yay).

Sabendo disso, você também pode construir um ambiente de jogo especial onde você interrompe o serviço antes de iniciar o jogo para combater todo esse comportamento. No entanto, isso causará um comportamento idêntico ao desabilitar a composição da área de trabalho para um único executável por meio das propriedades do arquivo.

Tem algo a acrescentar à explicação? Soe fora nos comentários. Quer ler mais respostas de outros usuários do Stack Exchange com experiência em tecnologia? Confira o tópico de discussão completo aqui.