Searching DirectShow Components - it takes some 10 seconds

[Radioman]

Since some time ago I started to notice that when I start DBV-Viewer it takes some 10 seconds to start. It's during the sequence "Searching DirectShow Components". I have the latest Win11 driver from TBS. DVBViewer Pro 7.3.2.0.

In DVBViewer.log I find this: USceneRender         issuing WM_DEVICELOST, which indicates an error? Any hints to solve is welcome. Thanks.

I enclose my Support.zip

support.zip

[Griga]

Please reproduce the issue in DVBViewer debug mode, as recommended here. Then attach another support.zip.

 

vor 30 Minuten schrieb Radioman:

In DVBViewer.log I find this: USceneRender         issuing WM_DEVICELOST, which indicates an error?

 

A temporary error related to the video renderer, not to your problem.

 

[Radioman]

Tnx.

Here is the requested support.zip:
 

support.zip

[YARD2]

OK, have the same issue,

Together that my LCDhype Plugin crashes randomly at getting the status page via http.

I guess a Windows update

 

[HaraldL]

What also can cause a delay (must not be the main reason in every case): For me the first start of DVBViewer on every day also takes much longer on a very fast system, makes a pause on progress bar. If I close it and start it again it's fast. Seems the Windows Defender (or any other security software does pretty the same) checks every accessed file on start, makes hashes, sends them online to Microsoft Defender Cloud and waits for response if one of them is a known malware. Later on the results seem to be cached locally and the check runs much faster then.

[Griga]

The DVBViewer.log from the support.zip above contains three DVBViewer starts. The 10 seconds delay happens the first and third time (14.06.26 16:26:43.219 and  16:32:34.794), but not the second time (16:30:18.284). Strange... 

 

"Searching DirectShow Components" means, that DVBViewer lets Windows list decoders that are suitable for certain media types like H.264 or MP3 by using the IFilterMapper2 interface, and additionally usable audio renderers (audio devices) by using the ICreateDevEnum interface. It includes a lot of registry reading.

[Griga]

I can't reproduce the issue under Windows 10. Neither under Windows 11, patch level February 2026. I'm using Windows 11 as rarely as possible, because I don't like it at all.

 

Then I 've updated Windows 11 to the June patch level. Now Windows doesn't start anymore.  Windows 11 is just a bag full of bugs.

 

 

[Griga]

Fortunately, after a forced power-off, Windows 11 started again and processed the updates. Now I can reproduce the 10 seconds delay, but only once after a Windows restart. Subsequent DVBViewer starts are as fast as they should be. The issue does not occur after shutting Windows 11 down and starting it again, which is more or less putting it to a hibernation state due to the Windows Fast Startup feature.

 

Does this match your experience?

 

[Griga]

The 10 seconds delay doesn't happen after a Windows 10 restart, though. So it seems to be an exclusive Windows 11 feature.

 

Anyway, I will add some special logging to the DVBViewer filter mapping code, so I can check under Windows 11,  which part takes such a long time...

 

[mark2019]

I have the same issue.
But i use only a SAT-IP-Server (Digibit R1)

I have that Problem since the April Win11-Patchday

Edited 7 hours ago by mark2019

[Griga]

The extended logging revealed, that the delay is caused by the first media type (H.264 video) for which DirectShow decoders are searched. It lets the IFilterMapper2 interface dig through the registry for approx. 10 seconds. Maybe after that all relevant data is cached, so that searching for additional media types or performing the whole procedure again becomes fast - until the next Windows 11 restart or Windows 11 shutdown and start without the Fast Startup feature.

 

It can hardly be avoided, so it looks like we have to live with this Windows 11 issue until it gets fixed by Microsoft.

 

[Radioman]

3 hours ago, Griga said:

Does this match your experience?

 

Yes, if I do a restart of DVBViewer it starts next time with 'normal' Searching DirectShow Components. 
But if I do Restart of Win11 it's back to 10 seconds search.

 

OK, all this started some time back, with a Windows update, I believe.

Thanks for your support.