Cumulative Update KB4480116 Windows 10 v1809 Build 17763.253 - Jan. 8 Win Update

Page 11 of 21 FirstFirst ... 910111213 ... LastLast

  1. Posts : 5
    Windows 10 Home X64
       #100

    Just double checked some extra examples:
    VirtualBox with Linux MINT 19.1, Firefox and all others no problem.
    Windows 10 , BRAVE browser and all others no problem.
    Only Edge failing after windows update 17763.253.
      My Computer


  2. Posts : 4,666
    Windows 10 Pro x64 21H1 Build 19043.1151 (Branch: Release Preview)
       #101

    Bree said:
    I restored some Macrium images just to test this. Edge worked with my router up to and including 17763.195. It only broke with this update to 17763.253.
    I can confirm that 17763.195 has no issues connecting to my router using Edge. We seem to have found a breaking bug.
      My Computers


  3. Posts : 10,311
    Wndows 10 Pro x64 release preview channel
       #102

    slicendice said:
    I can confirm that 17763.195 has no issues connecting to my router using Edge. We seem to have found a breaking bug.
    I think so, I just tried logging into my router twice more using Edge. Both times it failed resulting in 2 more of the Event Viewer entries I posted here Cumulative Update KB4480116 Windows 10 v1809 Build 17763.253 - Jan. 8 Windows Update - Page 10 - Windows 10 Forums
      My Computer


  4. Posts : 2,450
    Windows 10 Pro x64
       #103

    DooGie said:
    Just looked at my Event Viewer and noticed a new entry in it.

    The program MicrosoftEdgeCP.exe version 11.0.17763.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    Process ID: 2e10
    Start Time: 01d4a83fb9fd3523
    Termination Time: 4
    Application Path: C:\Windows\System32\MicrosoftEdgeCP.exe
    Report Id: 56ef79bc-b3ac-4ffe-881d-919683a01f4e
    Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe
    Faulting package-relative application ID: MicrosoftEdge
    Hang type: Cross-process

    I have 18 MicrosoftEdgeCP.exe errors. I didn't count the times I tried it, but it's pretty much that many!!!
      My Computer


  5. Posts : 2,557
    Windows 10 pro x64-bit
       #104

    DooGie said:
    Just looked at my Event Viewer and noticed a new entry in it.

    The program MicrosoftEdgeCP.exe version 11.0.17763.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    Process ID: 2e10
    Start Time: 01d4a83fb9fd3523
    Termination Time: 4
    Application Path: C:\Windows\System32\MicrosoftEdgeCP.exe
    Report Id: 56ef79bc-b3ac-4ffe-881d-919683a01f4e
    Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe
    Faulting package-relative application ID: MicrosoftEdge
    Hang type: Cross-process
    All are under event ID: 1002 and I have many just like yours:

    The program MicrosoftEdgeCP.exe version 11.0.17763.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
    Process ID: 10c0
    Start Time: 01d4a85d75062c5d
    Termination Time: 44
    Application Path: C:\Windows\System32\MicrosoftEdgeCP.exe
    Report Id: 928f9cd8-5c0c-4b01-9f7a-320faf99ac0b
    Faulting package full name: Microsoft.MicrosoftEdge_44.17763.1.0_neutral__8wekyb3d8bbwe
    Faulting package-relative application ID: MicrosoftEdge
    Hang type: Cross-process
      My Computers


  6. Posts : 4
    Win 10
       #105

    Found here that everything that's adressed by ip number instead of a name doesn't work in Edge any more.
    Reverted KB4480116 and it works again.
    Just a thought: could it have anything to do with the smb level, have some devices on 1.
      My Computer


  7. Posts : 1,248
    Windows 10 Pro (Build 19043.1110)
       #106

    rudrood said:
    Found here that everything that's adressed by ip number instead of a name doesn't work in Edge any more.
    Reverted KB4480116 and it works again.
    Just a thought: could it have anything to do with the smb level, have some devices on 1.
    Sounds like a DNS plumbing snafu. I.e., Edge wants to go through DNS, and can't deal with IP addresses or something. I don't use Edge, so I'm not going experiment to find out.
      My Computer


  8. Posts : 4
    Win 10
       #107

    Looks more that it tries to send adresses through the specified search engine for the adress bar, and can't find them like that.
      My Computer


  9. Posts : 75
    Windows 11 Pro
       #108

    on the router issue in Edge. Same Event Viewer errors. I have a Linksys WRT1900ACS v1 with non-default IP-address. Accessing it via https://www.linksyssmartwifi.com/ (using local account) still works.
      My Computer


  10. Posts : 981
    W10 Pro v21H2
       #109

    Bree said:
    I restored some Macrium images just to test this. Edge worked with my router up to and including 17763.195. It only broke with this update to 17763.253.

    Not sure if a WiFi hotspot is relevant, but I am able to access its IP using Edge...

    Attachment 220344
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:30.
Find Us




Windows 10 Forums