That might sound a bit stupid but I can't get my head around on where netflix.exe is actually located. I can see in my process manager that such a process actually exists when I open the app in Windows 10. The problem comes when I actually try to locate it.
Hi guys. The Microsoft Edge is my favorite browser of all times, really, but not when I try to watch netflix or other video streaming services, it always breaks, I have no ideia what to do anymore. Always when I try to play something there's an error and then I need to reload over and over again, sometimes even when I just play the video it stop working when I try to play again. Help me to keep using this best browser that I've ever seen.
I've ever tried to disable hardware acceleration, enable DRM content, install Microsoft Silverlight and a lot of other things, but I didn't get to watch so far without an error I keep receiving these error codes: D7356-7701 and others related. Is there's still something that can be done to really fix theses erros or I just have to be patient and wait for news versions of the browser?
Look in the list on the left 'cookies on computer' for anything netflix, click them one by one and use the arrows in the middle to move them into 'cookies to keep'. (Or you could right click to do the same).
I was concerned for a bit that all the Netflix-related cookies that showed up had a Chrome icon next to them, and I was trying to find the cookies for the W10 UWP app. Does that app run on Chromium or something?
Why am I unable to connect to my many Chromecast devices from windows 11, like i can from my android phone. I have netflix installed on my windows 11 laptop but there is no option to project the vision to to my Chromecast. I know you can use Chrome and cast a screen but this is cumbersome and not the best picture. It works perfectly on android and wondering why its not the same on windows 11.
Windows 11 is an entirely seperate operating system than android or chromeOS so there will be limitations. The best way to cast is using Chrome and casting from Netflix, you should still be able to cast the video and not just the browser/screen as long as you are on the same wireless network. As an alternative, you can ask your Google assistant to play a title from Netflix on your Chromecast, have you tried that?
Dell PC running WIN 10. Netflix generally seems to run fine. When mouse pointer moved over control icons on lower bar, popup windows appear as they should. However, when mouse pointer is moved upward to engage control (e.g. move volume slider or choose an episode), the control popup immediately disappears. Hence cannot e.g. change volume or choose another episode. Same issue, two different Dell desktops, two different mice (wired & bluetooth). No problem with Edge or Chrome. Hence assume it is a Firefox / Netflix interaction problem. Any fix other than to use another browser?
Rather by accident, I've learned that the issue is linked to use of Subtitles. The control popup disappears when the mouse pointer travels over a subtitle box. The size of the text box appears to vary as a function of how much dialog is contained (reasonable; edges of box cannot be seen) so sometimes it's possible to navigate to the control without mousing over a text box and then the control works. (Netflix seems inconsistent in use of subtitles - sometimes when there is no dialog, there is no box at all; other times, they present a description of sounds, e.g. "dramatic music" or "raindrops falling". Control popup does not disappear when no text is presented.) If Subtitles is turned off, the the control popup does not disappear. I've been using Subtitles recently as a noise abatement solution in a crowded environment. The issue is specific to Netflix, most likely because the arrangement of controls, etc is unique to them.
Thank you. Running in Troubleshoot Mode eliminates the problem. However, clearing Netflix cookies and cache does not, although the behavior has changed somewhat (the control popups don't disappear immediately as before but do when I try to make a change.)
If the problem continues, disable some more (restartingFF). Continue until the problem is gone. After, you knowwhat group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF)until the problem returns.
That was very good work. Well Done.Please flag your last post as Solved Problemas this can help others with similar problems.Go to that post and click the 'Solved' button to its right.
Validate with: Run Netflix via edge Browser or native Windows App, Pick a 4k/HDR program, play, press SHFT-CTRL-ALD-D to see diagnostics. Observe resolution is only 1920x1080 instead of 4k. Note that to be able to play in Edge Browser you should in before have also enabled PlayReady via "edge://flags".
The last three lines are the problems. They show there is no HDCP 2.2 support, HDR10 support or 4k support. This is specifically for PlayReady rendering via edge of course, but the Netflix app does of course also use PlayReady.
Its mindboggling now negligent Intel is about this and how Intel does not seem to care about the frustration this creates with customers (ok: with me. Don't want to talk for others). NVidia has HDCP 2.2 status in its control panel.
Of course, Netflix is equally annoying. They also do not have any user information about whether or not HDCP 2.2 is supported. Netflix app/web-page just don't show 4K and HDR logos on the media when it does not detect HDCP 2.2 support.
My suspicion is that HDCP 2.2 with Intel iGPU (even all those 11th/12th gen iGPU with built-in HDMI 2.0!) will not work unless the device manufacturer goes through a lot of additional BIOS/ME work and maybe even other hassles. And seemingly none of the lower cost mini pc vendors has done this. I say this, because beelink for example is also missing the Windows 3D mode setting, and the ak1plus box does not even support HDMI 2.0 18 Gbps solutions, but only the 10Gbps resolution of 3180x2160@60Hz - but then of course without HDR. Aka: all the details of video output that seemingly with Intel iGPU are part of (video) BIOS.
On AMD APU, it looks to me as if this is all only in the AMD driver, and i have not seen any hardware with AMD iGPU that has managed to NOT deliver 3D, 18Gbps or HDR. In fact, motherboards built before Ryzen was out and claimed to support only HDMI 1.4 where later updated in documentation to also support HDMI 2.0, because Ryzen then supported HDMI 2.0 and the pin is just pased from APU to HDMI connector. And i was hoping the same would be true now with 11th/12th gen Intel iGPU. Alas, seemingly not.
I see you mentioned you opened a case and you were promised to get an email that you never received, can you tell me when was the case opened? How did you open this case? For example via email, chat, etc.
These are all day 1 problems of boxes i bought and will return to Amazon unless i get the problem fixed, because i am trying to find a good mini-pc as a HTPC. And as mentioned in the first post, i tried with both the OS/drivers provided by the vendor and then when that did not work with fresh windows install and Intel drivers.
I cannot confirm the behavior with my Intel NUC11TNKv7. Film is "War Machine". The NUC is connected to the HDfury VRROOM > Yamaha AVR HDMI 2.0 > TV HDMI 2.0. The green signal diagnosis below is from the HDfury device.
Which cable do you use to connect your projector? How long is it? I can say that a 10 meters (33 ft) conventional HDMI 2.0 cable mostly will not enable 4K @ 60 Hz RGB/YCbCr 4:4:4 due to signal degradation. I suppose you always use the same cable for all mentioned devices but nevertheless this may have an influence.
SSU report does not seem to like to report version number of drivers it did not install itself, but that was from 12/22, and did not solve the HDCP issue, so i installed the WHQL driver from Intels page. Didn't help either, but is newest non-beta i guess. Just tell me if you want to see output for another driver version.
Had also checked that all device level security was on (TPM, core isolation, bitlocker, secure boot). HDCP service is also running. Kinda running out out of idea what to do randomnly. Some diagnostics frm the HDCP service itself would be peachy.
This should work. However, HDMI cables can be even too short (2 ft). This can lead to interference caused by electromagnetic emissions ("EMI"). Additionally, the complex electronic timing can mismatch (HDCP handshake, handshake repeatability). Keep cables between 2 and 3 meters (6 - 12 ft). I know that the rack interior is less photo worthy then but do you have such a cable for testing purposes? I've noted that you've already tried a direct connection without AVR. But the AVR can even help here to provide a sufficient voltage to the Fiber cable the projector is connected to. Since all other devices work, I don't want to rule out a deficit in the Intel HDMI interface implementation showing up just with your conditions.
90f70e40cf