Hi @Mihail Solovyov,
Thank you for posting your query on Microsoft Q&A.
As per our understanding, you want to configure the Microsoft Entra Global Secure Access (GSA) Windows client so that it remains disabled by default after system restarts, updates, or reboots. Your goal is for users to have to manually enable the client when needed, to avoid DNS issues when connected to an on-premises network. You have tried registry edits and conditional access policies but have been unsuccessful, even encountering BSODs related to the GSA driver.
The GSA client for Windows includes both a kernel-mode driver (globalsecureaccessdriver.sys) and a user-mode service. The documented registry key (like PrivateAccessEnabled) controls the private access feature but does not control the start behavior of the underlying driver or service. Conditional Access policies similarly do not manage the service or driver startup.
Incorrect attempts to disable the driver or service using unsupported methods can cause system instability or BSODs like the one you reported.
Please review the steps below to resolve the issue:
- Identify the GSA services and drivers on the client system Open an elevated PowerShell or Command Prompt and run:
get-service | Where-Object DisplayName -Match "Global Secure Access"
sc query type= driver state= all | findstr /i "globalsecureaccess"
This reveals the exact service and driver names to manage.
- Disable auto-start of the GSA driver and service
Using Services MMC (Graphical):
- Run services.msc as Administrator.
- Locate services like “Global Secure Access Driver” and “Global Secure Access Service”.
- Right-click each, choose Properties, and set the Startup type to Disabled.
Using CLI commands:
sc config globalsecureaccessdriver start= disabled
sc stop globalsecureaccessdriver
sc config globalsecureaccessservice start= disabled
sc stop globalsecureaccessservice
- Set the private access registry key to disabled Execute this command in an elevated prompt:
reg add "HKLM\SOFTWARE\GlobalSecureAccess\Client" /v PrivateAccessEnabled /t REG_DWORD /d 0 /f
This ensures private access is off by default.
- Provide a manual enable procedure for users Instruct users to start the services manually in an elevated prompt as needed:
sc start globalsecureaccessdriver
sc start globalsecureaccessservice
- Test thoroughly in a controlled environment
- Restart the device to verify GSA remains disabled.
- Manually start services and confirm GSA functionality.
- Monitor for DNS conflicts or crashes.
Please refer to:
Please "Accept as Answer" if the answer provided is useful, so that you can help others in the community looking for remediation for similar issues.