diff --git a/.bazelrc b/.bazelrc
index 38f3bfdbd07926..33c29b363f74a0 100644
--- a/.bazelrc
+++ b/.bazelrc
@@ -41,12 +41,6 @@ common:macos --remote_local_fallback_strategy=sandboxed
 
 # Windows config -------------------------------------------------------------------------------------------------------
 common:windows --strategy=standalone # Valid values are: [dynamic_worker, standalone, dynamic, remote, worker, local]
-# TODO(agent-build): rules_python 1.9.0 transitions py_binary to enable_runfiles=true on Windows, creating a second
-# Bazel configuration. build_python.bat writes PCbuild/ intermediate files into the shared execroot source tree, so two
-# concurrent builds of python_win (one per configuration) race on those files. Setting enable_runfiles globally makes
-# the transition a no-op (same flag value => same config hash => one build). The proper fix is to make build_python.bat
-# hermetic by redirecting MSBuild's OutDir and intermediate paths to $(@D) instead of the source tree.
-common:windows --enable_runfiles
 # Neither repo_env nor shell_executable affect action keys. It can be both an advantage and a disadvantage.
 # For instance, if we need to have some special behavior in bash we can add it, however, in some cases
 # it may lead to cache poisoning.