Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.
Open and run DxDiag.exe - Microsoft Support
Open and run DxDiag.exe. This tool is used to collect info about devices to help troubleshoot problems with DirectX sound and video. A support person might ask for this info, or you might post it in a forum when you ask for help. In Windows, select Start and enter dxdiag into the search box on the taskbar. Select dxdiag from the results. In the ...
The EdgeTransport.exe process consumes 100 percent of CPU resources on ...
Fixes an issue in which the EdgeTransport.exe process on an Exchange Server 2010 Edge Transport server or an Exchange Server 2007 Edge Transport server consumes 100 percent of CPU resources for a long time. This issue occurs when the Edge Transport server receives an email message that a large attachment of a known file type, such as a PowerPoint attachment.
A Description of the Windows Management Instrumentation (WMI) Command ...
The versions of Windows that are listed at the beginning of this article include a command-line utility (Wmic.exe) to access Windows Management Instrumentation (WMI). Previously, an end user would generally write a script to gather information by means of WMI. Wmic.exe can only be used by the local system administrators regardless of WMI ...
Use Bootrec.exe in the Windows RE to troubleshoot startup issues
To run the Bootrec.exe tool, first start the Windows RE: Put the Windows Vista or Windows 7 media in the DVD drive, and then start the computer. Press a key when you are prompted. Select a language, a time, a currency, a keyboard, or an input method, and then click Next. Click Repair your computer. Select the operating system that you want to ...
A handle leak occurs when an .exe file is called by the CreateProcess ...
For example, the file system filter driver denies the execution of an .exe file. When you try to run the file later, the file does not start as expected. If you check the Explorer.exe process in the Process Explorer utility, you find that the .exe file leaks a handle in the Explorer.exe process. Resolution Hotfix information
Event ID 1009 and high CPU or memory usage in noderunner.exe in ...
Memory usage may exceed 10 GB for a single noderunner.exe process, and handle counts may exceed 20,000. Additionally, the following event may be logged in the Application log: If you review the Search Service logs, you may see several events that contain the following text: Also, the following event is logged in the System log:
When the Health Service (HealthService.exe) runs timed scripts in ...
When the Health Service (HealthService.exe) runs timed scripts in Microsoft System Center Operations Manager 2007, high memory usage may occur. This problem occurs when you use a System Center Operations Manager 2007 Management Pack that was converted from a Microsoft Operations Manager 2005 Management Pack. The Health Service restarts because ...
Splwow64.exe process does not end after a print job finishes in Windows ...
Note The Splwow64.exe process is used to translate the driver model of a 64-bit operating system and a 32-bit program. Splwow64.exe is used to support the Printer Driver Isolation feature. The 32-bit version of Windows 8 has its own Splwow64.exe file, and the 32-bit version of Splwow64.exe is also affected by this issue.
PowerPoint freezes and the Powerpnt.exe process cannot be stopped in ...
However, the Powerpnt.exe process cannot be stopped. Cause. This issue occurs because of an issue in the algorithm that PowerPoint uses to render slides. Resolution Hotfix information. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article.
IExpress self-expanding .exe file that is created in Windows 8 or ...
Fixes an issue in which you cannot run a self-expanding .exe file that is created in Windows 8 or in Windows Server 2012. This issue occurs when you try to run the file on a computer that is running Windows Vista, Windows Server 2008, or a version of Windows that is earlier than Windows Vista or Windows Server 2008.