Hi,
Thanks for that. At least I know that it should work.
Unfortunately, none of that seems to help. My PC meets requirements with miracast enabled and WiFi NdisVersion 6.70. The Xbox just doesn't show up as a device to project to.
All I can think to do will be to remove my Xbox from devices on the PC and see if re-establishing a connection helps.
<Edit>
Sadly, that didn't make any difference.
I also saw the following comment posted by someone:
I had a similar problem, I solved it by changing how my pc was connected to the network.
- If the xbox is connected using wifi and the pc is connected using wifi if works.
- If the xbox is connected using wifi and the pc is connected using lan the xbox does not show on the pc.
- If the xbox is connected using wifi and the pc is connected using both wifi and lan the pc can initiate a connection to the xbox, but the xbox is stuck on a screen saying
the pc is about to project.
I'm not sure if the wireless display standard requires both devices to be connected to wifi or if this was just pure coincidence, and has more to with the ip-addresses and subnets used on different networks?
Streaming the opposite way around (form the xbox to the pc) works in all configurations.
I thought that it might offer some help, as I realised that My Xbox is on Wi-Fi and my PC on LAN, but even reverting to Wi-Fi for my PC, removing the device (xbox) and adding it again, so that the whole process was done with both console and PC
on the same Wi-Fi, made no difference.
Just spitballing here and I have no idea if it means anything, but I noticed (while trying everything), that if I tried to make the wireless connection (win+p) while the Console Companion app is running, it loses it's connection to the Xbox and
I have to start it's connection up again.
It's all a bit puzzling, as the 'Xbox Console Companion' stream to PC works fine, no matter how my PC is connected to the network, with it passing the connection test at all speeds. I just cannot get my PC to see the Xbox as a device to project
to.