@Amm0
With all due respect, I disagree with updating to latest stable before knowing for sure if it can make a difference, the OP is not a longtime expert on Mikrotik and directing him to the complications of updating the OS and the possibility that some settings need to be changed just because the version is changed seems risky to me.
Creating the supout.rif and asking Mikrotik’s support seems to me a better choice, though probably it will take some time to get an answer.
@radiobob
Now that you can access the devices, do create and post the /export of both, follow the instructions in this post:
http://forum.mikrotik.com/t/forum-rules/173010/1
Maybe something in those needs a little modification and some forum members may be able to spot it.
The “main” parts of the configuration should be the ones posted here:
http://forum.mikrotik.com/t/default-conf-cube-60g-ac-ptp/145573/1
so, unless something has changed the devices (their bridges that include both ether1 and bond1 interfaces) should have an IP address, 192.168.88.2/24 and 192.168.88.3/24 (other Mikrotik devices usually have 192.168.88.1/24 by default, so it makes sense). If you set your Windows nic to (say) 192.168.88.10/255.255.255.0 you should be able to ping/access them by IP.
Then, likely, you might want to change these addresses to your network ones and/or if you have a DHCP network, you need to add a DHCP client to the bridge, as seen here:
http://forum.mikrotik.com/t/how-to-configure-wireless-wire-cube-pro-cubeg-5ac60aypair/171675/1
But it is strange, if the factory setting - as spippan posted - is that of a “transparent L2 bridge”, IP addresses should not be relevant for the actual Wireless bridge to work, only for accessing the devices by IP.