Hello,

There is a very annoying problem with Windows 8 (and up), this issue did not exist with Windows 7 or earlier.

Basically if you go to "Network" in Windows Explorer you will (as expected) see all of your network devices - any device with a web interface should have a "View device webpage" option if you right-click it. This works fine as long as the device is http, if you try to do it with an https device it will give you an error "Error 0x80004002: No such interface supported". 

Same thing happens on all Windows 8, 8.1 and Windows 10 machines (regardless of default browser) but it works perfectly fine on a Windows 7 machine... Anyone got any idea for a workaround? The device used I'm using is a Netgear ReadyNAS but it seems to happen with any device that uses https for its admin webpage.


Really thankful for any help I can get on this!

• Edited by Hesten123 Thursday, January 22, 2015 6:42 PM

Also wondered about this but never got around to actually making a thread about it! I don't have any solution more than creating a shortcut to the device web page, would like to see if there are any other ways.

• Edited by Mzeera Saturday, January 24, 2015 6:30 PM

Hi Michael,

Thank you for the reply.. I can't put pictures in here as my account is not verified but here are three screenshots:
http://imgur.com/wsZvTWz

And when you click it, this happens (no matter what browser is set to default):
http://imgur.com/eulVKHf

This does not happen in Windows 7 on earlier with the exact same device, only in Windows 8 and later.

Here are the properties for this specific device:
http://imgur.com/WZwlYEM

Note that clicking the web address from inside the "properties" window works just fine.. The error only occurs when you right-click and then "View device webpage".

• Edited by Hesten123 Tuesday, January 27, 2015 10:05 PM

Hi Michael,

I created a .gif to better demonstrate what's happening.. Somehow I managed to make a somewhat perfect looping gif so don't get stuck watching it for too long - it does loop ;)

http://imgur.com/XFCqMpO

Also note that the media device at the end of the gif is the same device but if you check properties it uses a http link rather than a https link - if I right-click that one and press "view device webpage" it works just fine.

----

Here's a process monitor capture of me trying "view device webpage":

https://onedrive.live.com/redir?resid=22B9C7037AD2E51B!249&authkey=!AML4mAr7NaB0d2w&ithint=file%2cPML

to find the action just search for "nas", or the full hostname; nas-2B-F7-7C

Hope you can help me find a solution for this.. I guess it's related to certificates but I don't see why it's an issue on Windows 8 but not Windows 7.

• Edited by Hesten123 Thursday, January 29, 2015 7:06 PM

Hi Hesten123,

Apologize for the late reply.

Would you mind to capture the worked example that access from the link on the properties tab?

It would be more efficient to check with both of the two traces.

Once ready, you may right click on the same call and check on the properties of the call.

Check and see if any difference between them on DLL files at the process tab.

Best r

Hi Michael,

No worries! 

I made a capture using the properties window now:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B!250&authkey=!AM70JOgKJWMzYSE&ithint=file%2cPML

As far as I can tell all it does is just launch Chrome with the command line
"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" https://192.168.2.123/admin/

which makes sense and what I guess "View device webpage" should be doing as well but for some reason isn't.. Any suggestion for a workaround would be greatly appreciated.

Hi Hesten123,

Apologize for the long delay.

I checked at the log files and it is hard for me to determine the root cause.

i will help to involve someone else to further look at this issue. There might be some time delay.

Appreciate you patience.

Best regards

I made a capture using the properties window now:

Try making the two traces more comparable.  E.g. I think the Process & Thread events in the second trace could be very significant.  E.g. is Delegate_Execute.exe equally apparent in both?  For an initial filter I used  Operation Begins with Process.

Btw does this mean that Chrome is your default browser?  Have you tried a different browser?   <eg>

 

HTH

Hello Michael,

Thank you, I'll try to go through the steps provided tonight.

@Robert, I'll make two new captures right after each other. The two previous captures were made with several days in between. As for the browser, it doesn't matter which browser is the default one (same issue regardless) but yes, Chrome is my current default.

Thanks!

Hey Michael and Robert,

Here are the network monitor captures and a new set of process monitor captures (made directly after eachother)... Process monitor of the properties window is a lot bigger since that one launches Chrome (as expected) which generates a lot of data.

Info:

• Computer hostname: HEXQUAD  |  IP: 192.168.2.128
• NAS hostname: nas-2B-F7-7C | IP: 192.168.2.123
• In addition to ethernet network interface I also enabled capturing on the Virtualbox adapter since well, in this case the NAS is a virtual machine - same thing happens even if it's a real non-virtual machine. VirtualBox host-only IP: 192.168.56.1 (not sure how relevant this is though).
  

Network capture using "View device webpage":
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21251

Network capture using the link in the properties dialog:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21252

Process monitor capture using "View device webpage":
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21253

Process monitor using the link in the properties dialog:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21254

Screenshot of the issue as it occurs:
http://imgur.com/eulVKHf

.gif animation demonstrating the issue:
http://imgur.com/XFCqMpO

Thanks for your help!

• Edited by Hesten123 16 hours 10 minutes ago

new set of process monitor captures

Both are still dependent on that mysterious delegate_execute.exe that you got from Chrome.

https://code.google.com/p/chromium/issues/detail?id=171355

(Google search for
    "class not registered" delegate_execute site:google.com
)

There is a possible solution in there that you could check.

 

Good luck

Hey Michael and Robert,

Here are the network monitor captures and a new set of process monitor captures (made directly after eachother)... Process monitor of the properties window is a lot bigger since that one launches Chrome (as expected) which generates a lot of data.

Info:

• Computer hostname: HEXQUAD  |  IP: 192.168.2.128
• NAS hostname: nas-2B-F7-7C | IP: 192.168.2.123
• In addition to ethernet network interface I also enabled capturing on the Virtualbox adapter since well, in this case the NAS is a virtual machine - same thing happens even if it's a real non-virtual machine. VirtualBox host-only IP: 192.168.56.1 (not sure how relevant this is though).
  

Network capture using "View device webpage":
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21251

Network capture using the link in the properties dialog:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21252

Process monitor capture using "View device webpage":
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21253

Process monitor using the link in the properties dialog:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21254

Screenshot of the issue as it occurs:
http://imgur.com/eulVKHf

.gif animation demonstrating the issue:
http://imgur.com/XFCqMpO

Thanks for your help!

• Edited by Hesten123 Thursday, February 12, 2015 7:36 PM

Hi Michael,

Thank you for continued help on this. I don't know if you saw my previous post, it contains process monitor captures using IE instead of Chrome. I will be away this weekend and can't provide network captures but I will provide them as soon as possible.

But please note that this issue is the exact same even on a system that does not even have Chrome installed, to me it seems unrelated to the browser.

Hi Michael, 

Finally got the IE captures as well. Linking the process captures again too. 

Setup is same as before:
Computer hostname: HEXQUAD  |  IP: 192.168.2.128
NAS hostname: nas-2B-F7-7C | IP: 192.168.2.123
In addition to ethernet network interface I also enabled capturing on the Virtualbox adapter since well, in this case the NAS is a virtual machine - same thing happens even if it's a real non-virtual machine. VirtualBox host-only IP: 192.168.56.1 (not sure how relevant this is though).

Process capture of "View device webpage" and one click at "retry" while IE is standard browser:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21255

Process capture using properties window while IE is standard browser:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%2125


Network capture of "View device webpage" while IE is standard browser:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21258

Network capture using properting window while IE is standard browser:
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21257


And once again I'd just like to point out that this exact same device and setup works just fine on Windows 7, just not on Windows 8 (or 10 RC).

Thanks!

Hi Michael,

Did you see the captures? Any ideas? I'd say the issue is with Windows, something was changed with the way https are opened from Network explorer when Windows 8 was released... Question is if the change can be tracked and reverted or if someone can figure out some sort of workaround?

Hi Hesten123,

Apologize for the long delay reply.

This monring I received the message from Mike:

I just finished the packet and promon analysis.

Here is the result.

From property

From device

I dont see any traffic between 192.168.2.128 and 192.168.2.123 from two packets.

Promon logs

From the process monitors logs collected when clicking to view Device.

There is no error or failure results in it.

Action plan

========

We may need to collect the desired information again. please help gather the netmon traces and process monitor logs again.

Best regards

Hi Michael,

Alright.. Maybe related to the device in question being a virtual machine hosted on the same computer as I'm doing the tests from. I'll bring home a physical device from work today or tomorrow and do another capture. Thanks!

 please help gather the netmon traces and process monitor logs again.

How about getting an explanation for those  Operation Begins with Process  discrepancies that I found first?

E.g. what are Google's  delegate_execute.exe and W8's dllhost.exe supposed to be starting?

Hello Michael,

I have now made new captures.. Both process and network while using IE as the default browser and also using an actual physical unit rather than a VM. I'm not sure we'll find the answer in the netcaps, I think Robert may be on to something.

Anyways, here they are (put everything in to one archive this time):
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21259

Setup this time is as follows:
Client hostname:  HEXQUAD      Client IP:  192.168.2.123
Device hostname: LAB314         Device IP: 192.168.2.133

Hopefully this will be helpful.

• Edited by Hesten123 10 hours 35 minutes ago

Hello Michael,

I have now made new captures.. Both process and network while using IE as the default browser and also using an actual physical unit rather than a VM. I'm not sure we'll find the answer in the netcaps, I think Robert may be on to something.

Anyways, here they are (put everything in to one archive this time):
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21259

Setup this time is as follows:
Client hostname:  HEXQUAD      Client IP:  192.168.2.123
Device hostname: LAB314         Device IP: 192.168.2.133

Hopefully this will be helpful.

• Edited by Hesten123 Wednesday, March 11, 2015 8:41 PM

Hi all,

I have sent the message to Mike.

If any update, will post back.

Best regards

Hi Hesten123,

The trace result you uploaded contains no related informations in Network monitor and the process monitor,

The message from Mike:

In the network trace, client use dynamic port 55549,55550,55551 to communicate with 192.168.2.133

But from the process monitor logs, the client use TCP port 55554, 55555, 555556:

We need to collect the netmon trace and promon logs at the same time.

Whats more, from the GIF file. I see the IE tried to download one file from NAS server. But I did not see this behavior in netmon trace.

Apologize for any inconvenience.

Regards

Hi Michael,

Alright - so here are new captures.. All running at the same time; process monitor, network monitor and also gifcam to demonstrate exactly what is being done.
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21262

Setup is same as above;
Client hostname:  HEXQUAD      Client IP:  192.168.2.123
Device hostname: LAB314         Device IP: 192.168.2.133

Anything missing/mismatching between the captures now would be an issue with Windows - all captures at taken at the exact same moment. Hopefully this will help more :-)

To make things easier and if you want to reproduce it on your side, here's a guide on how to install a readynas in VirtualBox;
http://apps.readynas.com/pages/?page_id=143

I can also be available for remote session if that's required.

Cheers!

• Edited by Hesten123 12 hours 56 minutes ago

Hi Michael,

Alright - so here are new captures.. All running at the same time; process monitor, network monitor and also gifcam to demonstrate exactly what is being done.
https://onedrive.live.com/redir?resid=22B9C7037AD2E51B%21262

Setup is same as above;
Client hostname:  HEXQUAD      Client IP:  192.168.2.123
Device hostname: LAB314         Device IP: 192.168.2.133

Anything missing/mismatching between the captures now would be an issue with Windows - all captures at taken at the exact same moment. Hopefully this will help more :-)

To make things easier and if you want to reproduce it on your side, here's a guide on how to install a readynas in VirtualBox;
http://apps.readynas.com/pages/?page_id=143

I can also be available for remote session if that's required.

Cheers!

• Edited by Hesten123 Monday, March 16, 2015 6:22 PM

Hello Michael,

Just wanted to check if you saw my latest message and if it's been forwarded?

Cheers!

Hi Hesten123,

Apologize for the late response.

I might missed the Alert of your update.

Further, this case is under process discussion, I will forward the information you posted.

Thank you for your patience and understanding.

Best regards

Hi Michael,

Just curious if there's been any update on this case? Thank you

Since the alerts for this thread doesn't seem to work (at least I never got any myself) I'm bumping this one again. Cheers!

Hi Hesten123,

Really Apologize for the long delay.

The below is the result updated by Mike on this morning:

Thank you for your patience very much.

We already involve premier team to look at this issue and analyze the netmon traces and promon logs again. They also confirmed that it is not a network issue. Per their suggestion, they recommend that we should engage Desktop team to check this issue.

We already spent much time and effort on this forum case and prove that it is not a network issue. Based on our experice, we may need to collect DUMP files for further analysis, but it is not suitable to collect and analyze the DUMP files in a forum case. could you please persuade cx to open a paid case to us? so that our desktop team will continue help on it.

I will give you a summary

====issue====

Windows 8.1 client cannot open admin page when click on button view device

===Error information===

Error 0x80004002: No such interface supported

===Analysis===

We collect netmon traces and promon logs for analysis first. From them, we only can see the https traffic between client and NAS device on windows explorer process.

3              0              4:17:28 AM 3/12/2015    0.8549882            System 192.168.2.128     192.168.2.133     TCP        55549 (0xD8FD)             TCP:Flags=......S., SrcPort=55549, DstPort=HTTPS(443), PayloadLen=0, Seq=621523173, Ack=0, Win=65535 ( Negotiating scale factor 0x8 ) = 65535          {TCP:2, IPv4:1}

4              0              4:17:28 AM 3/12/2015    0.8552258            System 192.168.2.133     192.168.2.128     TCP        443 (0x1BB)                TCP:Flags=...A..S., SrcPort=HTTPS(443), DstPort=55549, PayloadLen=0, Seq=4159887130, Ack=621523174, Win=14600 ( Negotiated scale factor 0x5 ) = 467200        {TCP:2, IPv4:1}

5              0              4:17:28 AM 3/12/2015    0.8553284            System 192.168.2.128     192.168.2.133     TCP        55549 (0xD8FD)             TCP:Flags=...A...., SrcPort=55549, DstPort=HTTPS(443), PayloadLen=0, Seq=621523174, Ack=4159887131, Win=1024 (scale factor 0x8) = 262144 {TCP:2, IPv4:1}

6              156         4:17:28 AM 3/12/2015    0.8556060            System 192.168.2.128     192.168.2.133     TLS         55549 (0xD8FD)             TLS:TLS Rec Layer-1 HandShake: Client Hello.    {TLS:4, SSLVersionSelector:3, TCP:2, IPv4:1}

7              0              4:17:28 AM 3/12/2015    0.8557215            System 192.168.2.133     192.168.2.128     TCP        443 (0x1BB)                TCP:Flags=...A...., SrcPort=HTTPS(443), DstPort=55549, PayloadLen=0, Seq=4159887131, Ack=621523330, Win=490 (scale factor 0x5) = 15680          {TCP:2, IPv4:1}

8              1338       4:17:28 AM 3/12/2015    0.8726446            System 192.168.2.133     192.168.2.128     TLS         443 (0x1BB)                TLS:TLS Rec Layer-1 HandShake: Server Hello.; TLS Rec Layer-2 HandShake: Certificate.; TLS Rec Layer-3 HandShake: Server Key Exchange.; TLS Rec Layer-4 HandShake: Server Hello Done.        {TLS:4, SSLVersionSelector:3, TCP:2, IPv4:1}

9              0              4:17:28 AM 3/12/2015    0.8727314            System 192.168.2.128     192.168.2.133     TCP        55549 (0xD8FD)             TCP:Flags=...A...., SrcPort=55549, DstPort=HTTPS(443), PayloadLen=0, Seq=621523330, Ack=4159888469, Win=1018 (scale factor 0x8) = 260608 {TCP:2, IPv4:1}

10           0              4:17:28 AM 3/12/2015    0.8802681            System 192.168.2.128     192.168.2.133     TCP        55549 (0xD8FD)             TCP:Flags=...A...F, SrcPort=55549, DstPort=HTTPS(443), PayloadLen=0, Seq=621523330, Ack=4159888469, Win=1018 (scale factor 0x8) = 260608 {TCP:2, IPv4:1}

11           0              4:17:28 AM 3/12/2015    0.8804761            System 192.168.2.133     192.168.2.128     TCP        443 (0x1BB)                TCP:Flags=...A...F, SrcPort=HTTPS(443), DstPort=55549, PayloadLen=0, Seq=4159888469, Ack=621523331, Win=490 (scale factor 0x5) = 15680          {TCP:2, IPv4:1}

12           0              4:17:28 AM 3/12/2015    0.8805569            System 192.168.2.128     192.168.2.133     TCP        55549 (0xD8FD)             TCP:Flags=...A...., SrcPort=55549, DstPort=HTTPS(443), PayloadLen=0, Seq=621523331, Ack=4159888470, Win=1018 (scale factor

TCP three handshakes complete and certificate information exchanges successfully.

After comparing the working traces and non-working traces, we cannot find error information match with the error Error 0x80004002: No such interface supported it means that the error is not caused by network. Since the operation of clicking on view device does not call IE to open admin page, we believe the issue is caused by local component and should focus on the problem why the operation cannot call IE to open page.

Thank you for your patience and understanding. And apologize for any inconvenience.

Regards

Hello Michael,

Thank you for the response - so from what I'm gathering I'm supposed to pay for further support on this case? I will not do that, I do believe this is a bug in Windows based on the following;

1. The exact same setup works perfectly fine pre-Windows 8; something most have changed when it comes to opening device webpage between Windows 7 and Windows 8.
2. Several different computers in various combinations with different models of NASes, both mine and customers' has been tried and are all showing the same problem
3. The specific type of device  I'm trying to connect to (Netgear ReadyNAS) works fine if it advertises http instead of https for it's 'device webpage address'
4. I have yet to find any device advertising https that can be accessed through "view device webpage"

Now I guess that a possible workaround would be for Netgear to start advertising http instead of https by default and then re-direct http://x.x.x.x to https://x.x.x.x, but in the end of the day it's a feature in Windows that is not working.

Anyways Thanks Michael and Mike, you've both been helpful- I guess further support would be out of your hands. I guess I will have to go back to pursuing a workaround on my own.

Hesten123,

Thank you for your understandings, and really apologize for that I can't help further on this issue.

Hope we will have another topic and I could offer a Better solution that really helped.

Have a nice day.

Regards