Considering that my posts, unedited above yours, repeat what you have claimed, this is unlikely.
I am aware that you experience this issue after logging into Zorin OS. I am aware that you say that you experience it in Windows after logging into Zorin OS.
I think that this is what is misleading you. It gives an illusion that you are following.
As stated above, Zorin OS does not send any signal to the mouse.
You can try:
sudo apt install --reinstall xserver-xorg
The easy way of testing this is to remove your ~/.config directory, then reboot. This will create a new .config directory with all Default Settings (as if a fresh installation occurred.)
Rename ~/.config to .config-bkp. Then reboot and log in.
Having the -bkp config directory allows you to revert to your previous configurations.
I can only repeat:
Nothing On Zorin OS, absolutely nothing... No Config file, no setting, no Xorg, No Screen Resolution can affect your mouse operation On Windows or in BIOS. It is Not Possible.
It is possible that in the frustration, you mis-perceived the mouse as incorrectly working on Windows somehow... I think that is a stretch though.
Windows Does Not access the Zorin Configuration files on another partition. And BIOS most certainly does not.
As far as it is concerned, that stuff may as well be on your neighbors computer. It has no way of accessing it and Zorin OS has no way of signaling the mouse, much less if it is being used on Windows.
@337harvey may have some thoughts on some BIOS settings that can affect mouse behavior.
EDIT: I also should point out that users must be very wary of trying to find a pattern in a random intermittent problem with cause unknown. Currently, we do not know that it is not coincidence that the mouse fails to work properly at the times after you log in.
What is known is that if it was Zorin Creating the issue, then it would only fail to work properly on Zorin OS. It is impossible for it to carry over into Windows or into BIOS.