This problem is solved now. The following instruction needs to be updated:
https://docs.m5stack.com/#/en/quick_start/unitv/v_function
The instruction does not specify what driver is needed to communicate with hardware. It came out that the user needs a different driver than the one used for M5Stack core products.
In case anyone has the same problem, please make sure you have the newest VCP driver by FDTI installed on your machine. My advice is to use their website to check out the latest version:
https://www.ftdichip.com/Drivers/VCP.htm

This problem is solved now. The following instruction needs to be updated:
https://docs.m5stack.com/#/en/quick_start/unitv/v_function
The instruction does not specify what driver is needed to communicate with hardware. It came out that the user needs a different driver than the one used for M5Stack core products.
In case anyone has the same problem, please make sure you have the newest VCP driver by FDTI installed on your machine. My advice is to use their website to check out the latest version:
https://www.ftdichip.com/Drivers/VCP.htm

I'm working with my M5Stack Grey and have no problems, it always appears as one of the COM ports. M5Stack Grey works perfectly fine with my machine.

I resterted the computer and also updated M5Burner to the latest version. No success so far, UnitV is still not discoverable.

My UnitV is not discoverable by M5Burner and EasyLoader. I installed the CP210x driver and have no problems connecting and burning firmware to my M5Stack Grey. I'm on Widnows 10 and the device is visible by Windows in the Device Manager:

The COM port does not show up in M5Burner and EasyLoader. Seems that UnitV is not discoverable. Any suggestions on fixing this?