We received your inquiry and I understand that you are having a glitch with windows media player classic. Please accept our apologies for any inconvenience this may be causing. We will be more than happy looking for a solution.
Upon reviewing the information on your case we were able to verify that the Intel® HD Graphics 520 is up to date, we will like to replicate the scenario, for that could you provide us with the following:
Brand and model of your computer/motherboard: (Please provide)
The version of the windows media player classic: (Please provide)
Codecs pack version: (Please provide)
Hello and thanks for the reply!
Here is the necessary information:
Brand and model of your computer/motherboard:
The version of the windows media player classic:
Version: 1.7.13 (e37826845)
Compiler: MSVC v19.00.24215.01
Build date: Jul 16 2017 18:47:17
LAV Splitter: 0.70.2.1
LAV Video: 0.70.2.1
LAV Audio: 0.70.2.1
FFmpeg compiler: MinGW-w64 GCC 7.1.0
Name: Windows NT 10.0 (build 15063)
Version: 10.0 (64-bit)
CPU: Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
GPU: Intel(R) HD Graphics 520 (driver version: 220.127.116.1177)
That, I hope, should be it.
Thanks for your efforts!
1 of 1 people found this helpful
Thank you for patiently waiting,
I recreated the your scenario on our laboratory using the Intel® HD Graphics 520 whit the driver 18.104.22.16877 and the same configuration for Windows® media player classic that you have provided, the glitch that you are having did not appear during the test, I also updated to the latest version of graphics driver available for Intel® HD Graphics 520 and run the scenario and still did not find the glitch.
We can try to complete the update on your Intel® HD Graphics 520 you can find that at the following link
Please let me know the outcome
Thanks for taking the time!
I have updated my drivers as well and will see what happens.
Do you have any idea what else could be causing a glitch like that?
Anywhere else I might look?
Thanks for your response,
It could be really difficult to point to a specific cause, it could be ether software or hardware related, due to of that we can start with the driver updated, consult the computer manufacturer could be an option or the software developer since this is only happening on this specific software.
Let know the out come
Thanks for getting back to me.
I have tried a few other things (some of which I can't even remember) and am currently cautiously optimistic that the issue has worked itself out.
Time will tell...