VPN VPN IKEv2. The connection is normal, but the routes do not come.
OS: Windows 10
The operating system of the router 6.46.1

Windows does not support split include. Instead DHCP options are used to work around the limitation. Check IPsec debug logs, you should see something like this immediately after the tunnel establishes:

If your WAN Type is PPPoE on MikroTik this would not work, issue also described here:
viewtopic.php?f=2&t=154743&p=764979#p764979
And I also have (still) an open ticket regarding this, SUP-3815, support acknowledged an issue that fits my description.
I was hoping the fix would make it in 6.46.2 but looks like it didn't, based on the changelog.

If your WAN Type is PPPoE on MikroTik this would not work, issue also described here:
viewtopic.php?f=2&t=154743&p=764979#p764979
And I also have (still) an open ticket regarding this, SUP-3815, support acknowledged an issue that fits my description.
I was hoping the fix would make it in 6.46.2 but looks like it didn't, based on the changelog.

Thank's. I will have to use Powershell

If your WAN Type is PPPoE on MikroTik this would not work, issue also described here:
viewtopic.php?f=2&t=154743&p=764979#p764979
And I also have (still) an open ticket regarding this, SUP-3815, support acknowledged an issue that fits my description.
I was hoping the fix would make it in 6.46.2 but looks like it didn't, based on the changelog.

Unfortunately, the issue appears to be caused by Fast Path driver for PPPoE which is why it takes a longer time to resolve it, however we are still working on it. You could try disabling Fast Path on your router (if that is an option for you of course) to see if starts working then.

If your WAN Type is PPPoE on MikroTik this would not work, issue also described here:
viewtopic.php?f=2&t=154743&p=764979#p764979
And I also have (still) an open ticket regarding this, SUP-3815, support acknowledged an issue that fits my description.
I was hoping the fix would make it in 6.46.2 but looks like it didn't, based on the changelog.

Unfortunately, the issue appears to be caused by Fast Path driver for PPPoE which is why it takes a longer time to resolve it, however we are still working on it. You could try disabling Fast Path on your router (if that is an option for you of course) to see if starts working then.

Does it turn off here?
/ip settings set allow-fast-path=no

I tried, but nothing has changed.

Did you reboot the router after setting it?

I've tried, but I don't know how to disable FP for PPPoE.
I've set allow-fast-path=no in IP settings and in bridge settings (though it is not part of a bridge but I've disabled everythig that had fast path in it).
I've disabled the fasttracking FW rule.
Rebooted.
And I still see traffic in "FP Rx Rate" for the PPPoE interface. Traffic in FP Tx/Rx on the interface it sits on also visible (ethernet1), and on the other ethernet ports too.
(Have I found another issue? i'm damn lucky. lol).
Also still no DHCP Inform in the IPsec debug logs.

Did you reboot the router after setting it?

Yes