Those apps can surface the following error: “The EMS System encountered a problem” with “Message: [Microsoft][ODBC SQL Server Driver] Protocol error in TDS Stream” or “Message: [Microsoft][ODBC SQL Server Driver]Unknown token received from SQL Server.” On the Windows Health Dashboard, Microsoft points out the bug is a problem for both client and service versions of Windows starting from Windows 7 and also affecting Windows 8.1, Windows 10, and Windows 11. There is no way to avoid this issue other than luck. Microsoft says there is no workaround to use until an official fix comes. That will happen in a fix that Microsoft is currently working on and should drop within the coming weeks.
App Test
I guess most people will now be asking if they are running any apps that can be hit but this bug? Well, you can run the following test that Microsoft provides to find out: “If you are unsure if you are using any affected apps, open any apps which use a database and then open Command Prompt (select Start then type command prompt and select it) and type the following command: tasklist /m sqlsrv32.dll” If you are experiencing this bug, the only option right now is to simply not use that app until Microsoft rolls out its official fix. Tip of the day: When Windows 10 or Windows 11 has issues, it’s not rare to run into startup problems. Corrupted Windows files, incorrect system configuration, driver failure, or registry tweaks can all cause this issue. Using Windows startup repair can fix boot issues caused by the most prevalent issues. Though it may seem that all is lost when you run into startup problems, it’s important to try a Windows boot repair so you can at least narrow down the source of the issue. If it doesn’t work, you may have to reinstall the OS or test your hardware.
