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.
The memory usage of the DFS Replication service keeps increasing on a ...
Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page. Prerequisites
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:
Tips for improving Excel's performance - Microsoft Support
Set this registry key in Windows 10 version 17763.832 or later to turn off the scan. Slowness pressing ALT+ shortcut keys in Excel. In Office 365 version 1908 or later, add this registry key. Slowness when Excel launches. Open Excel in Safe Mode to see if the slowness is caused by add-ins. You see out-of-memory issues opening multiple workbooks
Applies To: Excel for Microsoft 365
Windows Remote Management service leaks memory when it handles ...
Fixes a memory leak that occurs when the Windows Remote Management (WS-Management) service handles certificate authentication requests. This issue occurs on a computer that is running Windows 7 or Windows Server 2008 R2. ... In this scenario, the memory usage of the WS-Management service keeps increasing. After a while, the available memory is ...
High memory and CPU usage in Lsass.exe when you export keys in Windows ...
Assume that you run an application that calls the NCryptExportKey function to export a key on a Windows Server 2008-based computer. The key has more than one master key. In this situation, Lsass.exe experiences high memory usage and a rapid increase in the number of used handles. Additionally, the computer exhibits high CPU usage.
Manage drive space with Storage Sense - Microsoft Support
Manage drive space with Storage Sense. Windows 11 Windows 10. Windows 11 Windows 10. Storage Sense can automatically free up drive space for you by getting rid of items that you don't need, like temporary files and items in your Recycle Bin. Here’s more info on how it works and how to set it up to meet your needs.
Internet Explorer 11 consumes high memory and CPU cycles after you ...
This article describes an issue in which Internet Explorer 11 consumes high memory and CPU cycles in Windows 8.1, Windows RT 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1. A cumulative update and a hotfix is available to fix this issue. Before you install this hotfix, see the Prerequisites section ...
Searchindexer.exe consumes lots of memory in Windows 7 or Windows ...
Symptoms. Assume that you perform a search in the Start menu or in Windows Explorer by using wildcard characters in Windows 7 or Windows Server 2008 R2. For example, you search "ren*1". In this scenario, the memory usage of Searchindexer.exe increases and does not decrease as expected after the search. Note If several users perform multiple ...
Runtime Broker is using too much memory - Microsoft Support
If your RAM use is high and your PC is running slowly, an app may be the cause of the problem. Press Ctrl+Shift+Esc to open Task Manager and then, on the Processes tab, check to see how much memory Runtime Broker is using. If its using more than 15% of your memory, you probably have an issue with an app on your PC. To stop Runtime Broker from ...
High memory usage by mobsync.exe when you try to synchronize items in ...
You have a computer that is running Windows 7. When you try to synchronize items that have long file names, the computer slows down, and the mobsync.exe process experiences high memory usage. Cause. This problem occurs because of an issue in the Client-Side Caching extension (Cscui.dll) when files have long paths. Resolution Hotfix information