Description:
After installing R 4.5.2 on Windows 10 and updating to RStudio 2025.09.2+418 (“Cucumberleaf Sunflower”), the R session fails to start. No output appears in the console, and the logs repeatedly show system error 10053 (An established connection was aborted by the software in your host machine).
The issue persists even when rolling back to older R versions (tested with R 4.4.1, R 4.3.3, and R 4.2.3). Every attempt to launch RStudio results in the same “R session failed to start” message with no visible R console.
System Information:
- OS: Windows 10 (x64)
- RStudio Version: 2025.09.2+418 “Cucumberleaf Sunflower” (12f6d5e2, 2025-10-20)
- R Versions Tested: 4.5.2, 4.4.1, 4.3.3, 4.2.3
- R Installation Path:
C:\Program Files\R\R-4.5.2
Error output shown in RStudio:
Error Starting R
[No error available]
[No output emitted]
Relevant log excerpt (rsession-Administrator.log):
2025-10-31T00:36:12.260586Z [rsession-Administrator] ERROR system error 10053 (An established connection was aborted by the software in your host machine)
[request-uri: /events/get_events]; OCCURRED AT void __cdecl rstudio::session::HttpConnectionImpl...
Troubleshooting already attempted:
Confirmed R works independently
- Opened R GUI manually → runs successfully
R.home()returns correct path (C:/Program Files/R/R-4.5.2)
Reinstalled both R and RStudio cleanly
- Uninstalled all R versions and RStudio
- Rebooted before reinstalling
- Verified
R.exelaunches directly via command prompt
Reset RStudio configuration and cache
- Deleted:
C:\Users\Administrator\AppData\Local\RStudio
C:\Users\Administrator\AppData\Roaming\RStudio
- Relaunched RStudio (fresh config rebuild)
Manually set R path in RStudio preferences
Created or edited:
C:\Users\Administrator\AppData\Local\RStudio\rstudio-prefs.json
With contents:
{ "rpath": "C:\\Program Files\\R\\R-4.5.2\\bin\\R.exe" }
Disabled Windows Defender and antivirus temporarily
- Added exclusions for:
C:\Program Files\RStudio
C:\Program Files\R
Tested manual RStudio diagnostics
- Ran
rstudio --run-diagnostics - Confirmed R path resolves correctly but session still aborts
- Same issue occurs under Administrator account
Checked for socket interference or port conflicts
- No proxy or VPN active
- Firewall not blocking local connections
Result:
RStudio GUI launches but immediately shows “R Session Failed to Start.”
No R session is established; the same “system error 10053” repeats in logs regardless of R version.
Question:
Is there a known cause or workaround for persistent system error 10053 during R session startup on Windows 10?
Could this indicate a deeper local socket/loopback issue between RStudio and R, or a configuration regression in the recent release?
