diff --git a/rust/Cargo.aarch64-pc-windows-msvc.toml b/rust/Cargo.aarch64-pc-windows-msvc.toml
new file mode 100644
index 0000000000000..1e5d512b2fa74
--- /dev/null
+++ b/rust/Cargo.aarch64-pc-windows-msvc.toml
@@ -0,0 +1,6 @@
+# cargo --config Cargo.aarch64-pc-windows-msvc.toml build
+#
+# Workaround ring issues to build on Windows ARM64.
+# See https://github.com/briansmith/ring/issues/1167 for details.
+[patch.crates-io]
+ring = { git = "https://github.com/awakecoding/ring", branch = "0.16.20_alpha" }
\ No newline at end of file
diff --git a/rust/README.md b/rust/README.md
index c4724259dbbe1..38cca535d0ef8 100644
--- a/rust/README.md
+++ b/rust/README.md
@@ -81,6 +81,10 @@ INFO	/home/boni/.cache/selenium/chromedriver/linux64/106.0.5249.61/chromedriver
 
 Alternatively, you can replace `cargo run` with `bazel run //rust:selenium-manager`, for example `bazel run //rust:selenium-manager -- --browser chrome --debug`
 
+### Windows ARM
+
+There are issues when building on Windows ARM64. To workaround, use `cargo` with `--config Cargo.aarch64-pc-windows-msvc.toml` flag.
+
 ## Roadmap
 The implementation of Selenium Manager has been planned to be incremental. In the beginning, it should be a component that each Selenium language binding can optionally use to manage the local browser infrastructure. In the mid-term, and as long as it becomes more stable and complete, it could be used as the default tool for automated browser and driver management. All in all, the milestone we propose are the following: