Steam Client Update Fixes Startup Login Dialog and Network Transfers

Valve shipped a Steam client update on August 3, 2026, with fixes aimed at two recurring annoyances: a login dialog that appears at startup even when it shouldn’t, and local network game transfers that fail to start. The client downloads and installs automatically.

The patch carries three changes, per Valve’s changelog:

• Fixed login dialog showing at startup when auto account login has already started.
• Fixed additional cases preventing local network game transfers from starting.
• Fixed user chooser appearing on startup even when not requested.

The login-dialog fix was not in the release as first posted. Valve appended it afterward, flagging in the notes that the release “was updated with an additional change,” and the same revised changelog now appears on the Steam Deck news page.

Steam’s second pass at the startup login dialog

Two of the three fixes target what the client shows in its first seconds. The user chooser, the account-picker screen, could surface at launch even when nobody asked for it. The login dialog could appear even after auto account login had already begun signing the user in, stacking a redundant prompt on top of a sign-in already in progress.

The appended fix is also the second time in a week Valve has patched this dialog’s trigger logic. The July 27, 2026 client update stopped the login dialog from showing when Steam is launched with the -silent command-line flag, a switch that tells the client to start without presenting its interface. The August 3 fix closes the adjacent case: the dialog firing when the client is already handling the sign-in on its own.

What the network transfer fix restores

Local network game transfers let a PC pull a game’s installation and update files from another machine running Steam on the same local network instead of downloading them again from Steam’s content servers. Before a download starts, the client checks the LAN for other PCs running Steam that already hold the needed content, and if the transfer goes through it fetches as much as it can locally, falling back to Valve’s servers for any remainder. Valve’s support documentation puts throughput at 100MB/sec over a wired connection and pitches the feature as a way to stay under ISP monthly transfer limits.

The transfer feature is also coming off a recent break. The July 27 update fixed local game transfers that had stopped working outright; the August 3 notes describe “additional cases” that kept transfers from starting, extending that repair rather than opening a new one. The conditions the feature operates under, both clients online on the same LAN, the sending machine idle, the game up to date on the host, remain as documented on Valve’s support pages.