Hi @scientifikk.
Was the board new in a sealed box when you received it, or was it previously used?
I ask for this information because it could be useful for the forum helpers to understand whether or not we need to consider whether the problem you are encountering could have been the result of specific usage of the board by the previous owners.
Was the board ever recognized by your computer, or were you having the "invisible to my computers" problem from the first time you used the board? The reason I ask is similar to that for the previous question.
Excellent troubleshooting technique!
If you have another USB-C device (e.g., a mobile phone), try connecting that other device to your computer with one of the cables. If your computer recognizes the device as connected, then this would prove that specific cable is in a functional state.
You were definitely wise to check whether the problem occurs with multiple cables. However, going forward it will be best to verify one specific cable is good, then use that cable for all further troubleshooting efforts. Otherwise, you risk a "russian roulette" situation where one or more of the cables might be non-functional. If you are unlucky enough to happen to use the "bad" cable, then that would derail further troubleshooting efforts based on the assumption a good cable is in use.
Note that it is possible a cable could provide power to the connected device, but not allow it to communicate with the computer. So you should make sure to check whether your computer recognizes the device; not solely that the device is receiving power/charging via the cable.
It was a great idea to try multiple machines. However, I would recommend focusing on the Windows machine going forward (as long as you have access to that machine). The reason for this advice is that the helpers here are more experienced using Windows than ChromeOS. The UNO R4 WiFi is supported by Arduino Cloud Editor on ChromeOS. It is maybe also possible to use with some 3rd party development tools (I don't have any experience with that, so I can't say for sure). However, ChromeOS is very locked down, so this makes things a bit more complicated when it comes to communication between the computer and board (Cloud Editor does this via a browser feature called "WebSerial")
We can always switch to focusing on the ChromeOS machine after looking into the problem using the Windows machine.