Steam News11 February 20264mo ago

Build v0.13.1 - Fixes and Windows Defender

This is a bug fix only release, addressing a couple of things: Steam wouldn't let you reconnect after a few hours of playing a round, and you would have to reboot the launcher If you disconnected during the course of us

In this update1

Full notes

Full CM-SS13 update

Read the full published notes in a cleaner layout. The original post stays linked below.

What changed

0 fixes1 addition1 change1 removal

Server
Gameplay

changedSteam wouldn't let you reconnect after a few hours of playing a round, and you would have to reboot the launcher

removedThis build is currently only live on the latest branch, as every version we push has to be manually submitted to Windows to remove the Defender warnings you may have encountered, and we have to wait a few days for the whitelisting to be distributed to everyone's devices.

addedA note on Windows DefenderEvery new build is manually uploaded to the Defender team, who inspect the file to ensure it is not malware. The exact version of the launcher is then whitelisted, and when your device updates malware definitions, it will no longer be flagged by this exact version. This process has to be repeated anytime we change the .exe.

CM-SS13 changes

changedSteam wouldn't let you reconnect after a few hours of playing a round, and you would have to reboot the launcher

addedEvery new build is manually uploaded to the Defender team, who inspect the file to ensure it is not malware. The exact version of the launcher is then whitelisted, and when your device updates malware definitions, it will no longer be flagged by this exact version. This process has to be repeated anytime we change the .exe.

This is a bug fix only release, addressing a couple of things:

Steam wouldn't let you reconnect after a few hours of playing a round, and you would have to reboot the launcher
If you disconnected during the course of usual play, you would be reconnected to the Guest authentication screen

This build is currently only live on the latest branch, as every version we push has to be manually submitted to Windows to remove the Defender warnings you may have encountered, and we have to wait a few days for the whitelisting to be distributed to everyone's devices.

A note on Windows Defender

This application is sometimes captured by Windows Defender's Machine Learning algorithms, which look for applications that have code patterns that look similar to that of actual malware. In our case, this is likely due to the launcher downloading the engine from the internet, then immediately running the executable to connect you to the game.

Every new build is manually uploaded to the Defender team, who inspect the file to ensure it is not malware. The exact version of the launcher is then whitelisted, and when your device updates malware definitions, it will no longer be flagged by this exact version. This process has to be repeated anytime we change the .exe.

In order to force an update of your definitions, you can navigate to your Virus & threat protection settings, go to Protection updates and Check for updates

[carousel]