# Ray 1.12.0 Windows Issues

**URL:** <https://discuss.ray.io/t/ray-1-12-0-windows-issues/6319>\
**Category:** Ray Core\
**Created:** [May 29, 2022, 7:33am UTC](https://discuss.ray.io/t/ray-1-12-0-windows-issues/6319 "2022-05-29T07:33:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![yic](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ray.io/yic/32/437_2.png) [@yic](https://discuss.ray.io/u/yic)\
**Post date:** [June 1, 2022, 7:38pm UTC](https://discuss.ray.io/t/ray-1-12-0-windows-issues/6319/4 "2022-06-01T19:38:03Z")

</div>

@Mazyod Thank you for willing to help, but we already identified the root cause: the ray core layer is compiled with a protobuf not compatible with the newest protobuf (py). So until ray core upgrade the protobuf (cpp) we have to stick to the one \< 3.20.x. It’s actually also broken in mac/linux as well.

We never pin or restrict protobuf version in `ray/python/setup.py` before and that’s why when you install ray, it’ll always try to fetch the newest version of protobuf and unfortunately, it’s not backward compatible right now. The version restrict has been added in this [PR](https://github.com/ray-project/ray/pull/25211).

---

_[View the full topic](https://discuss.ray.io/t/ray-1-12-0-windows-issues/6319)._