Newly acknowledge bug in Edge keeps you from accessing some local pages – if you’ve installed this month’s cumulative updates

Topic

New Reply

Ah, the joys of installing the latest patches as soon as they’re available. Microsoft has officially acknowledged that this month’s cumulative updates
[See the full post at: Newly acknowledge bug in Edge keeps you from accessing some local pages – if you’ve installed this month’s cumulative updates]

7 users thanked author for this post.

Elly, GreatAndPowerfulTech, abbodi86, Karlston, trailcook, columbia2011

Reply | Quote

Replies

I had this issue myself with Edge, but also with Chrome as well sometimes. I typically use IE for accessing router or modem because it seems more compatible with these UI built into the devices.

Reply | Quote

_Reassigned Account wrote:

I typically use IE for accessing router or modem because it seems more compatible with these UI built into the devices.

… unfortunately.

Well, depending on device, you could also go out of your way to install Firefox 52 ESR (the last one to work with some of those), or possibly Pale Moon or even Midori…

Really dislike the part where you have to install an ancient and known-insecure browser extra (Java plugin, ActiveX control, even a Flash-based thing in one case) to configure your devices.

Not sure which is worse – server hardware like a RAID adapter or iSCSI disk array, or network devices like a VPN router…

Reply | Quote

I use EdgeBlock to completely disable Edge (foreground/Background) on all my systems.

https://www.sordum.org/9312/edge-blocker-v1-4/

1 user thanked author for this post.

Reply | Quote

And how does this help us? How does this correct an issue with Edge?

Reply | Quote

Microsoft needs to improve the updates. We have certain people, especially senior citizens, with newer PCs who only know Edge and don’t know how to install or run alternate browsers, not to mention accessing IE 11.

I am no longer an active member of the forums.

1 user thanked author for this post.

GoneToPlaid

Reply | Quote

But they do know how to access their router and configure it? (If not, no problem.)

Windows 11 Pro version 22H2 build 22621.1194 + Microsoft 365/Edge

Reply | Quote

Hello B, I agree. If someone can get into a router to configure it. they should know about other browsers. Using IE is dangerous to get into a router? Seriously? Logging into a local INTRANET website 2 feet from you is dangerous with IE? Jescott418 is right, IE seems to function better with those built in webpage configuration screens.

This has been brought up to Microsoft and they are working on it. I feel that if Edge won’t work, let me try another browser. Win10 comes with both Edge and IE, so it already has 2 browsers. Having a 3rd browser like Firefox would be even better.

Thank you B.

Reply | Quote

Logging into a home router is not something most would do unless forced to set the admin password. If anyone set it up, it was likely a nerd-buddy who did it. So while this is an embarrassing stupidity on MS’ part it is not likely to be that big of an issue. In fact, the nerd-buddy probably downloaded and installed Firefox and Chrome. So for the nerd-buddy, if they are aware of the problem, they can switch to different browser.

The embarrassment is the fact this would be an easy item to test if you had testers.

Reply | Quote

It is a case, in part, of vested interest to learn regular computer maintenance and exercise caution when applying updates.

Carpe Diem {with backup and coffee}
offline▸ Win10Pro 2004.19041.572 x64 i3-3220 RAM8GB HDD Firefox83.0b3 WindowsDefender
offline▸ Acer TravelMate P215-52 RAM8GB Win11Pro 22H2.22621.674 x64 i5-10210U SSD Firefox106.0 MicrosoftDefender
online▸ Win11Pro 22H2.22621.1194 x64 i5-9400 RAM16GB HDD Firefox110.0b9 MicrosoftDefender

Reply | Quote

Yep can confirm Win10Home 1803×64, WINVER 17134.556 is so afflicted, although IE11 still gets the job done.
There is a fix of sorts in the associated KB Article: https://support.microsoft.com/en-ca/help/4480976

Reply | Quote

I’ve found that I can work around the issue by adding local addresses explicitly to the hosts file, c:\windows\system32\drivers\etc\hosts

192.168.1.1   myrouter

and then browsing to https://myrouter/

 

5 users thanked author for this post.

GoneToPlaid, Karlston, HiFlyer, gborn, woody

Reply | Quote

Neat trick!

Reply | Quote

I got a feedback from a German blog reader as a comment to my German article. The guy tested a lot. The error pattern is really complex. I’ve translated the findings into English – it may be read as a comment here.

Ex Microsoft Windows (Insider) MVP, Microsoft Answers Community Moderator, Blogger, Book author

https://www.borncity.com/win/

2 users thanked author for this post.

GoneToPlaid, Karlston

Reply | Quote

Thanks for this post. One has gotta wonder about the logic behind what MS decides is a resolvable IP address, versus which MS decides it not resolvable — in terms of potential malware which tries to spread. Anyway, it appears to be a scenario of the right hand trying to cut off the left hand, in terms of dealing with malware. Just a guess. In any event, the programmers who were responsible for this fiasco should be looking for new jobs.

Reply | Quote

If Windows 10 v1809 doesn’t make this more than obvious to them, I’ll say it.

Microsoft would be better off hiring some real testers instead of relying on the “customer experience” to find their issues.

Byte me!

Reply | Quote

I am wondering if you are one of the original Phrozen Crew from years ago.

Reply | Quote

Router admin pages that use obsolete code kinda bug me, not to mention that I’m betting many routers don’t have easy or user-friendly ways of updating them. This could potentially present itself to be a problem when newer browsers can’t open router admin pages because said pages are using too much obsolete code and are too difficult for the average home user to update.

Reply | Quote

I don’t think that this should be a problem since all routers should use basic HTML to present all router web pages. HTML 3.5 compliant, perhaps?

Reply | Quote

and after all these years, I thought that routers were linux based with an HTML interface..learn something new every day..

WaaS = Windows as a Syphon...suckers!

Reply | Quote

For all I know, you may be entirely correct. The only basic things which a router needs to expose is its IP address, and then to display its configuration pages using really old HTML standards which any web browser should be able to display.
Hmm…I just decided to check the HTML version of the login page for my Arris router. Here is what I got:
“DOCTYPE html PUBLIC “-//W3C//DTD XHTML 1.0 Transitional//EN””
It was a pain to get the above to show up correctly.

Reply | Quote

Microfix wrote:

and after all these years, I thought that routers were linux based with an HTML interface..learn something new every day..

Well, some of them are, but by no means all of them. And even with the Linux-based models, sometimes the only “supported” interface is something weird. (Yes, the one with only the Java configuration tool apparently had Linux in there somewhere, but no supported way to get console access, let alone documentation on doing the configuration from there.)

It’s a time-honored tradition to build routers on top of a BSD-family operating system, Juniper’s JUNOS is a good example. Cisco IOS is apparently all its own, and I’ve even seen something that wanted to claim to be a descendant of RT-11 …

1 user thanked author for this post.

Microfix

Reply | Quote

I have a question.  Installed Jan updates including the cumulative update for Win 10 1809.  afterwards, I had issues printing from Edge to a home network printer assigned a static IP. Occasionally I could print one page from Edge. Chrome printed without issues. Since I have occassionally experienced this in the past, I attributed it to a driver problem for my HP 1505n laserjet printer. My question is does this printer setup with a static ip, fall into the same problems with Edge not being able to access certain local ip addresses? Or should I stick with my driver theory?

Reply | Quote

banzaigtv wrote:

Microsoft needs to improve the updates. We have certain people, especially senior citizens, with newer PCs who only know Edge and don’t know how to install or run alternate browsers, not to mention accessing IE 11.

Sadly, computer instruction has never been up to par for anyone not interested in looking under the hood. Sites like this one are truly a blessing but many folks don’t want to know how it gets there only that you put in gear and steer. M$ has been remiss from day 1 and still are.

Reply | Quote

Fixed by cumulative updates on February 12, 2019:

Addresses an issue that prevents Microsoft Edge from loading webpages using a local IP address or a VPN connection.

Version 1809: February 12, 2019—KB4487044 (OS Build 17763.316)
Version 1803: February 12, 2019—KB4487017 (OS Build 17134.590)
Version 1709: February 12, 2019—KB4486996 (OS Build 16299.967)
Version 1703: February 12, 2019—KB4487020 (OS Build 15063.1631)

Windows 11 Pro version 22H2 build 22621.1194 + Microsoft 365/Edge

Reply | Quote