Fixes an issue that triggers elevated CPU or memory usage in noderunner.exe, failed content indexes, and database failovers in Exchange Server 2013 when Cumulative Update 10 or 11 is installed.

To fix this issue, install Cumulative Update 11 for Exchange Server 2013. Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. Learn about the terminology that Microsoft uses to describe software updates.

To fix the issue, limit the amount of memory that the noderunner process can consume. Follow these steps on each Exchange server: Locate the Noderunner.exe.config file in the %ExchangeInstallPath%Bin\Search\Ceres\Runtime\1.0 folder. Open the Noderunner.exe.config file, and then locate the <nodeRunnerSettings memoryLimitMegabytes="0"/> XML node.

Follow these steps to automatically diagnose and repair problems with files and folders in Windows. These problems might include the inablility to delete files or folders from the Recycle Bin, or troubles with trying to copy, move, rename, or delete a file. Select the Download button on this page.

When you select an AppFix, you can start the program executable (.exe) file, and the AppFix is applied. If a suitable AppFix is found, the tool eventually helps you generate and test matching file information.

After October 14, 2025, Microsoft will no longer provide free software updates from Windows Update, technical assistance, or security fixes for Windows 10. Your PC will still work, but we recommend moving to Windows 11. Learn more. Note: Use these steps for Windows programs.

If you want to set more properties for the computer, click Apply to enable (or disable) DCOM. Otherwise, click OK to apply the changes and quit Dcomcnfg.exe. Restart the operating system for the changes to take effect. More Information The following registry string value is used to enable or disable DCOM on all operating systems:

When you try to install, update or start a program or a file, you receive the following error message: Error: Windows cannot access the specified device, path, or file. You may not have the appropriate permission to access the item.

Fixes a Cmd.exe utility issue in which the utility does not let you specify a NUMA node when you create a process by using the "start" command in Windows Server 2008 R2 and in Windows 7.

This issue occurs because of incorrect memory reallocation logic that is used to create a new query node. Note When you use more than 64 V2 performance counters to collect system data, the query node must be reallocated.