Hello T10D, thank you for posting in the Microsoft Q&A community.
When aN application authenticates successfully but fails to initialize data streaming post-update, it generally points to security payloads introduced in recent cumulative updates. The most common technical reasons include stricter validation for DCOM/RPC connections that legacy applications may not natively support, or modifications to Schannel (Secure Channel) enforcing strict TLS cipher suites that might block the streaming port.
Since removing the updates temporarily restores functionality, the most effective standard resolution is to temporarily pause these updates while isolating the root cause. You can leverage Group Policy or Microsoft Intune to pause Quality Updates for the affected radiology workstation Organizational Units. Additionally, I recommend engaging GE Healthcare support alongside our troubleshooting, as enterprise medical applications frequently require specific vendor-provided configuration patches to comply with new Windows security baselines.
To help us pinpoint the exact change causing this streaming failure, I need to review some diagnostic data from a machine where the update is currently installed. Could you please open Event Viewer and navigate to Windows Logs > System to look for any Schannel errors (such as Event ID 36871 or 36874) or DCOM errors (such as Event ID 10036)? Also, please check Windows Logs > Application for specific .NET or application crashes during the exact time the streaming fails.
Official Microsoft Documentation for reference:
- Manage Windows updates in your organization: https://learn.microsoft.com/en-us/windows/deployment/update/waas-manage-updates-wufb
- TLS/SSL overview (Schannel SSP): https://learn.microsoft.com/en-us/windows-server/security/tls/tls-ssl-schannel-ssp-overview