Miracast, Again.

PhsMu

Active Member
Its a simple question, yet a loaded one:

Is miracast irreversibly broken in LTSC 2021? I've tried many times since it was released, and not even in an unmodded image, I can get it to work.

I have tried to enable Wireless Display in the FoD tab, update, drivers... to no avail. So I'm asking for help. All I want is to know I'm able to push an external display to a TV (which is Miracast capable, I've done it from Tablets and Cellphones without issues), so I don't need a bunch of dongles and cables when I go on a trip.
 
PhsMu I asked if you used NTLite and I sent the link above as NTLite has a problem disabling features on demand. Although your problem is different it could be related. But I don't think that's the case as I've tested it with Home and Enterprise on an older version (2.3.1.8454) and I also get errors when trying to enable Wireless Display.

What worked for me was adding the .cab files as updates. However NTLite lists it in the wrong order and tries to apply the language pack first (the file with en-us in the name).

Maybe it's something for nuhi to check out.

So I integrated the Microsoft-Windows-WirelessDisplay-FOD-Package~31bf3856ad364e35~amd64~~_3de5f9a5.cab file as an update and applied it to the Apply page then I loaded the image again and integrated the Microsoft-Windows-WirelessDisplay-FOD-Package~31bf3856ad364e35~amd64~en-us~_03428f1b.cab file.

About LTSC it seems that the solution that works is this one:
https://forums.mydigitallife.net/th...rprise-n-ltsc-2021.84509/page-52#post-1708526
 
Yeah, I've just managed to try that MDL workaround. I managed to assemble a script to do it (I don't trust myself to manage on the fly without typos), but every time I enable the Regulated Packages needed for it, wireless display gets disabled and can't be enabled without errors. So I added it to the dism batch!

And now the install Key for Enterprise LTSC doesn't work anymore, and I can't get past setup!

It just occurred to me I should try to enable just the Miracast/WirelessDisplay feature via dism on another dition, but its late where I live, so I'll try that tomorrow.I feel like I'm close to cracking this problem. ...Or going insane. One of the two.
 
ok, this is getting a little ridiculous but I managed to project the screen from the cellphone to the TV, the cellphone to the PC, yet projecting from the same PC to the TV disconnects straight after connection.

I think Microsoft just killed Miracast
 
I feel like I'm close to cracking this problem. ...Or going insane. One of the two.
How much time have you spent on this in total?
My advice, try again tomorrow but at the first failure put it on hold and walk away.
Have a good think, do you really need this? You might even get a "AHA" moment and realise where you went wrong, if you did of course.

Remember, defeat is summat you find at the end of delegs, nothing more.
 
How much time have you spent on this in total?
More time and energy than I should have, honestly. At this point more out of sheer spite towards Microsoft (**** you! Who do you think you are to tell me what I need or don't or what I should be using or not?!) than because I really really need it. Its useful, but can I live without it.

My advice, try again tomorrow but at the first failure put it on hold and walk away.
Have a good think, do you really need this? You might even get a "AHA" moment and realise where you went wrong, if you did of course.

Remember, defeat is summat you find at the end of delegs, nothing more.
But I managed to find the issue at last.

Future me, pay attention to these:

1: Never buy a ******* samsung device ever again. Never Ever. Their software kills whatever advantage their hardware can give you over competting brands unless you sell your soul to them.

2: Miracast needs:
Remoting and Privacy >
Device Setup Manager | Gerenciador de Instalação de Dispositivos
Multimedia >
Capture Service | Serviço de Captura
Network >
Quality of Service Package Scheduler (QoS) | Agendador de Pacotes Quality of Service (QoS)
Link Layer Topology Discovery Protocol (LLTD) | Protocolo de descoberta de Topologia na Camada do Link (LLTD)
Internet Conetion Sharing | Compartilhamento de Conexão da Internet (ICS)
Application Layer Gateway | Serviço Gateway de Camada de Aplicativo
Windows Connect Now (WCN)
System >
Consent UX
Shared Experiences (Video Settings force closes at connection without this) Not Needed anymore
Apps >
Capture Picker
PPIProjection | Connect App

Finally, make sure your test is unbiased by working with a device that... works, before you assume the problem is on what you're doing. It was all samsung's fault. It failed to do telemetry, it refused connection. Its not a standalone issue of mine, apparently there is a whole forum filled with complaints because their shared screen (multiple miracast devices at once) cannot be disabled and keeps any windows machine from connecting on Q series. What use it to connect two miracast devices at once if I can't connect one for that?!
 
Last edited:
At this point more out of sheer spite towards Microsoft
The reverse dry hump.

Its useful, but can I live without it.
;)

I managed to find the issue at last.
yayyyyy :D

For what i do i could still be using XP/XP64bit but as they are old(and other reasons :mad:) w7 is a better comparison for w10 and its still doing a stellar job :). Its why i can disable way more stuff than many people and still have a fully functional(for my needs anyway) machine :)
 
Last edited:
Yeah, my need for mobility, by enjoyment of gaming and also my stubborness make things more painful than they should have been., But
w7 is a better comparison for w10 and its still doing a stellar job :)
If it was still getting security updates and drivers for the newer machines, EVERYONE and their mothers would be using 7. It is the last good windows (not perfect, mind you, but good) and nothing which came afterwards compare. What little gamebreaker shortcomings it has, someone has a workaround somewhere, it is just that popular.
 
I had to take time away from pc work this week. Thinking of shaking off some of my stubborness. Need to build a 32bit capture for a project and it might be 1809. Need to check for my coffee lakes and laptops for w10 32bit chipset and igpu drivers.
 
For the moment I just want a working OS where I can work and play.

But yeah, aside of the current builds, all I know is that my next systems are going to be AMD, for better Linux compatibility and to avoid feeding Intel-Micro$hit alliance for an store-app-telemetry-filled future.
 
Back
Top