Others

Fix Microsoft.SharePoint.exe Blocking SystemParametersInfo Calls

Camila Milosovich Sep 28, 2026 868 views

Question details

A custom C# or C++ application completely freezes during SystemParametersInfo execution because Microsoft.SharePoint.exe blocks the API calls.

How to Fix Microsoft.SharePoint.exe Blocking SystemParametersInfo Calls

Product: Microsoft SharePoint
Device & OS: Windows 10 and Windows 11
Scenario: Modifying NONCLIENTMETRICS border sizes programmatically using the SystemParametersInfo function.
Observed behavior: The application freezes, and Task Manager shows Microsoft.SharePoint.exe as the blocking process, even if the final parameter is set to zero.

Before you start

Ensure you have Microsoft 365 administrator privileges and have gathered your process crash dumps or Task Manager logs to facilitate troubleshooting with support.

Solution 1Recommended

Open a Microsoft Online Support Ticket

Because this issue involves deep OS-level interactions between your application and the Microsoft SharePoint process, contacting Microsoft Support is the most effective way to identify the root cause.

Microsoft Support has the necessary internal tools to investigate the specific environment hooks and deadlocks caused by Microsoft.SharePoint.exe interacting with Windows shell metrics.

Access Microsoft 365 Admin Center

Log into the Microsoft 365 Admin Center using your administrator credentials.

Navigate to Support

Click on the 'Support' tab in the left-hand navigation menu and select 'Help & support'.

Create a Service Request

Open a new ticket describing the exact scenario: Microsoft.SharePoint.exe is blocking SystemParametersInfo calls during NONCLIENTMETRICS changes.

Provide Diagnostics

Attach your application freeze logs, Task Manager screenshots, and OS environment details (Windows 10/11) for the engineering team to review.

Admin Rights Required: Only users with an active Microsoft 365 Administrator role can create and manage support tickets through the Microsoft Online Support portal.

Solution 2

Temporarily End the SharePoint Process

As an immediate workaround during development, terminating the SharePoint sync process can prevent it from hooking into the system metrics and blocking your application.

Free Microsoft Office alternative

Switch to WPS Office for a Streamlined, Conflict-Free Experience

If heavy background processes like Microsoft SharePoint are causing system conflicts or performance issues, consider switching to WPS Office. It provides a lightweight, highly compatible alternative for your document needs without intrusive background sync services blocking your system APIs.

1. Download the Installer: Visit the official WPS Office website and click the free download button for Windows.
2. Install WPS Office: Run the installer to quickly set up the suite without cluttering your system registry or background services.
3. Enjoy Seamless Compatibility: Open, edit, and save your existing Microsoft Office files with perfect formatting.

Zero heavy background sync engines interfering with system APIs or causing development deadlocks.Fully compatible with Microsoft Office formats, including DOCX, XLSX, and PPTX.Lightweight architecture that consumes minimal system resources on Windows 10 and 11.Familiar tabbed user interface allowing for seamless and instant migration.

microsoft office alternative - wps office

Frequently Asked Questions

Why does Microsoft.SharePoint.exe interfere with SystemParametersInfo calls?

Microsoft.SharePoint.exe and related sync engines often hook into Windows shell UI metrics to provide file status overlays and context menus. Modifying system-wide non-client metrics can cause a deadlock if the SharePoint process is simultaneously querying or locking them.

Does this freezing issue only affect C# applications?

No, this freeze can occur in both managed C# applications and native C++ applications that utilize the SystemParametersInfo API to alter UI metrics on Windows 10 and Windows 11.

Will setting the final parameter to zero prevent the application freeze?

According to developer reports, the application may still freeze when conflicting with Microsoft.SharePoint.exe, even if the final parameter in the SystemParametersInfo call is explicitly set to zero. A support ticket is required for a permanent fix.

Office Quick Solutions