devicedisplayobjectprovider.exe is a Windows system file. It has a useful function. But I cannot think of any good reason why it should connect out, yet it does so from time to time. Any ideas as to why it connects our, & should I let my Firewall block it?
Per File.net ..(No date disclosed).. "DeviceDisplayObjectProvider.exe is an important part of Windows, but often causes problems. DeviceDisplayObjectProvider.exe is located in the C:\Windows\System32 folder. The file size on Windows 10/8/7/XP is 86,528 bytes. https://www.file.net/img/space.gif It is a Windows system file. The program has no visible window. The file is a Microsoft signed file. Therefore the technical security rating is 2% dangerous; but you should also compare this rating with the user reviews."
Thanks, @StillBorn. I did my online "homework" (including File.net) before posting but found no answer to the question I asked in this thread. To put my original question in different words: As to devicedisplayobjectprovider.exe, is its connecting-out essential to Windows system, or is it just another case of questionable Microsoft telemetry?
You should let it connect. I had no idea either what its function was until I Googled it and I had to look a few results before I found a meaningful description. https://community.norton.com/en/comment/5543413#comment-5543413 This is what Microsoft had to say about it in one of the results I looked at
Thanks, @roger_m -- useful link. It reads, in part... Hmm.... I haven't opened that menu in ages. However, I shall give devicedisplayobjectprovider.exe the go-ahead to connect -- ONE go-ahead at a time for now, until maybe I can figure out what is triggering it. (Hey, I'm retired so... there's plenty of time to mess around.)
