Windows 11

[Ethosik]

Oh YAY this is it but I have the 10th gen Intel so I might be affected by this issue. I wonder if something else came through with Windows 11 updates as I get the same error code (since this specifically references Windows 10).

Microsoft Store apps failed to install on Intel 11th, 12th Gen and AMD Ryzen 5000, 6000 PCs

A bug that was introduced with one of the recent Windows 10 builds was leading to Microsoft Store app install failures on modern Intel and AMD CPUs. An OOB update has been released which fixes this.

www.neowin.net

 

[nickdalzell1]

The Store is the same on both 11 and 10. They both got the revised UI and various other updates. I wouldn't be surprised that the error happens on both OSs. Once again, I'm glad I don't depend on app stores. at all.

Looking at the latest version of both OSs, the only thing really separating 10 from 11 is the taskbar and lack of rounded corners (UI-wise, that is). Unfortunately, Windows 10's idiot proofing and 'unidentified network no internet access' bug (a Vista vestige) remains unfixed. There's still one Windows 10 PC at work that up and decides there is no internet at all (says the default gateway is missing) but all the Win11 PCs remain connected no issue to the same router, same wifi. Even if you try to input a static IP matching what it would normally get from the DHCP server, it still manages to complain that it's an 'unidentified network' and refuses to allow connection outside the LAN/Intranet.

 

[StellarVixen]

The Store is the same on both 11 and 10. They both got the revised UI and various other updates. I wouldn't be surprised that the error happens on both OSs. Once again, I'm glad I don't depend on app stores. at all.

Looking at the latest version of both OSs, the only thing really separating 10 from 11 is the taskbar and lack of rounded corners (UI-wise, that is). Unfortunately, Windows 10's idiot proofing and 'unidentified network no internet access' bug (a Vista vestige) remains unfixed. There's still one Windows 10 PC at work that up and decides there is no internet at all (says the default gateway is missing) but all the Win11 PCs remain connected no issue to the same router, same wifi. Even if you try to input a static IP matching what it would normally get from the DHCP server, it still manages to complain that it's an 'unidentified network' and refuses to allow connection outside the LAN/Intranet.

View attachment 2007971

That handy tool fixed my internet quite a few times. What I hate about it in 11 is that they hid it behind too many clicks.

 

[PinkyMacGodess]

That handy tool fixed my internet quite a few times. What I hate about it in 11 is that they hid it behind too many clicks.

But 'that handy tool' often didn't fix anything. It was a mess, what it wouldn't fix, and in some cases wouldn't even identify. When it worked, it worked, when it didn't, it was useless and a waste of time. *shrug*

 

[StellarVixen]

But 'that handy tool' often didn't fix anything. It was a mess, what it wouldn't fix, and in some cases wouldn't even identify. When it worked, it worked, when it didn't, it was useless and a waste of time. *shrug*

Not in my experience. Whenever it didn’t work, it didn’t work because cause of the problem was beyond its abilities to fix.

But I do get other people had different experience. What can you do…

 

[PinkyMacGodess]

Not in my experience. Whenever it didn’t work, it didn’t work because cause of the problem was beyond its abilities to fix.

But I do get other people had different experience. What can you do…

The problem was users were meant to believe that it was 'the tool' and it was sometimes so vague in what it was and wasn't seeing. In my experience, it often didn't fix anything. But it's flogging a dead horse. Hopefully they made it better. Rock on...

 

[nickdalzell1]

It never could fix the 'the default gateway is missing'

First of all, the default gateway was not missing; the client PC just failed to get a DHCP address. The odd thing was even with static IP settings, with exactly what it would normally get when the DHCP was working, you could neither ping the router much less any site outside the intranet. Today, that bug has gotten worse, and is now affecting any and all Apple devices. No Mac, iPhone, iPod, or iPad can get a DHCP lease even though the router claims over 120+ leases remain available (and MAC filtering is off). They all get APIPA addresses (169.254.x.x) and that problem has NOT fixed itself or shows any signs of improving.

All Windows 11 and Android devices, oddly enough, continue to work perfectly fine, DHCP or static.

 

[PinkyMacGodess]

It never could fix the 'the default gateway is missing'

First of all, the default gateway was not missing; the client PC just failed to get a DHCP address. The odd thing was even with static IP settings, with exactly what it would normally get when the DHCP was working, you could neither ping the router much less any site outside the intranet. Today, that bug has gotten worse, and is now affecting any and all Apple devices. No Mac, iPhone, iPod, or iPad can get a DHCP lease even though the router claims over 120+ leases remain available (and MAC filtering is off). They all get APIPA addresses (169.254.x.x) and that problem has NOT fixed itself or shows any signs of improving.

All Windows 11 and Android devices, oddly enough, continue to work perfectly fine, DHCP or static.

I had some issues with duplicate IP addresses, and stable access to the internet, so I now have my firewall doing DHCP, and everything seems to be happy, except for the Windows server complaining that it's not the one to provide addresses. I know the reason why, in a Windows environment you want the Windows Server to do that, but with all macs, it's not needed.

 

[nickdalzell1]

The oddest part is I can set the Mac to static and it acts like it's online (gets notifications from nearby iPhone, such as messages, apps, handoff works, etc, and update notifications come in, apps sorta work) but any attempt to open a site in Safari ends with 'you're not connected to the internet'

Terminal, try to ping yourself works. Ping 8.8.8.8 or the actual gateway results in 'host not reachable' or 'no route to host'

Using DHCP, it doesn't even wait. It instantly just defaults to 169.254 IPs. Same for any iPhone, iPad. Reboot router doesn't fix it. Windows PCs like my Windows 11 laptop and Windows 7 desktop have no issue getting a DHCP address from the same network router. Just Apple and that one Windows 10 PC fail. I spent hours yesterday troubleshooting without success. Tried even using different wireless NICs and a USB adapter for the Mac, no dice. Same issue.

The Windows 10 PC only works being connected via ethernet. The oddest part is this particular router won't let me get in via a static IP. At home, my router allows internet access even without the DHCP server if I set a static IP if I run out of leases, but this one is an oddball. It's an AT&T Uverse DSL router/modem from the year 2008, so it's probably on its way out anyway. I can however open its setup page via the Windows 11 laptop and it shows no errors, nothing out of the ordinary in the logs, and plenty of DHCP leases available. Even the MAC address of the Mac shows, but lists itself as 'inactive'. Any attempt to dig farther into the 'meat' of the router settings is blocked by AT&T of course.

I once had an instance at my mother's house where her DSL modem died. I tried to go to all sorts of stores; Best Buy, Walmart, Office Depot, even Kmart (when they existed) and they all told me that DSL is obsolete, and no one makes the modems anymore. That was in 2011. I am not sure how true that is, but mom ended up going with a cable modem, and work remains on this quiet old DSL system. Work is out in the middle of nowhere so only DSL and satellite is an option. With this bug however it's gonna be, well, interesting. Can't get a new modem/router and can't separate it by using a new router with modem in modem only mode because AT&T blocks the settings from being available to the user. Calling AT&T is met with their horrible customer service saying 'you still got Uverse?!' as if it were something right out of the 1980s or something.

 

[polyphenol]

Just Apple and that one Windows 10 PC fail.

About a year ago, I found Windows was the one that would not connect.

At the time, I had two Windows devices and one was, mostly, OK. The other simply would not connect wirelessly. For the first few weeks/months, I'd have to reconnect, reboot, play around, and could get it to connect - just a tedious nuisance. Then it would no longer connect. The other would always connect but became somewhat annoying by randomly losing connection, then reconnecting when I rebooted or told it to reconnect.

All Apple devices working flawlessly! All the way through.

Ended up getting rid of one Windows device and switching over to wired connection for the other one.

 

[PinkyMacGodess]

Are all these issues due to far range connections? Meaning on the fringe of your coverage?

I had a client that wanted me to help with their 'internet problems'. They had a longish ranch home, and all of their 'tech' was at one end of the house. 'We can't get a reliable connection, it keeps saying we aren't connected to the internet'. They were using their notebook and tablets at the other end of the house, not realizing they had very little connection. I used a spectrum analyzer and found they had such a low signal, and they *might* have been actually using one of their neighbors connections that was open, but still very weak. They had a full open basement so I recommended that they run wire to the other end of the house and put another AP there. They didn't want me to do it, and ended up buying a long 'patch cable' and drilling a hole in the floors, but the problem went away. Amazing, right.

People tend to oversell the idea of wifi. People at Worst Try, and others tend to oversell wifi as a bandaid to fix all connection problems.

All (most) OS's are based on well established standards so to have something as 'simple' as wifi not work is surprising. Either the system is over-designed, or the wifi isn't setup properly, or the signal just isn't there.

I also always recommended a hard wired connection for systems and for backhaul (if supported) for wifi extenders and access points.

 

[polyphenol]

Are all these issues due to far range connections?

About two feet/600 mm. From the machine to the access point.

It started about four or five yards/metres away but it was trivial for me to move the access point closer - so I did.

I considered replacing the wifi card in the PC but cost was similar to getting a small switch - which would also allow my Mac mini to be wired.

 

[pshufd]

Are all these issues due to far range connections? Meaning on the fringe of your coverage?

I had a client that wanted me to help with their 'internet problems'. They had a longish ranch home, and all of their 'tech' was at one end of the house. 'We can't get a reliable connection, it keeps saying we aren't connected to the internet'. They were using their notebook and tablets at the other end of the house, not realizing they had very little connection. I used a spectrum analyzer and found they had such a low signal, and they *might* have been actually using one of their neighbors connections that was open, but still very weak. They had a full open basement so I recommended that they run wire to the other end of the house and put another AP there. They didn't want me to do it, and ended up buying a long 'patch cable' and drilling a hole in the floors, but the problem went away. Amazing, right.

People tend to oversell the idea of wifi. People at Worst Try, and others tend to oversell wifi as a bandaid to fix all connection problems.

All (most) OS's are based on well established standards so to have something as 'simple' as wifi not work is surprising. Either the system is over-designed, or the wifi isn't setup properly, or the signal just isn't there.

I also always recommended a hard wired connection for systems and for backhaul (if supported) for wifi extenders and access points.

I ran a CAT5 cable from the basement to the living room 20 years ago. It took me several hours but it was well worth it. We weren't getting a signal on the second floor and adding a router in the living room solved that. We eventually got a powerline solution to the second floor for even better performance. Powerline can be a decent alternative for casual WiFi use these days.

 

[nickdalzell1]

My two PCs are in the shop in a building long, long away from the router and have no issues connecting. The Windows 10 PC is in the office right next to the router (which is sitting on the same desk). The 10 PC won't connect via wifi only ethernet (I think its wifi is bad TBH)

Only Apple won't connect wirelessly. Boss's iPhone, my iPhone, any iPad, any Mac (even those never associated with the network/never connected previously) just get APIPA addresses INSTANTLY. They don't even bloody try to get a DHCP address. Setting a static IP doesn't work with the Apple products, but does work with Windows. I've never heard of an issue that blocks specific manufacturer's products from a router. I'm blaming AT&T's router on this. They got a network tech coming out to upgrade the IP cameras to get away from the issues we've had with those (plus they only work via Internet Explorer anyway) and replacing some network equipment but since DSL is our only option I doubt there's going to be an easy solution because in my experience, DSL is apparently the new dial-up.

This 'bug' was random but got worse with time, now no Apple device can connect period. I can use a Mac with the 'personal hotspot' option via iPhone which points to the issue not being the hardware of the Mac. This solution will allow the culprit devices to connect as well so their internal hardware seems fine. What's the oddest is that with a static IP, while you cannot browse, the network prefs shows a green 'light' icon, and you get notifications from nearby Apple devices via handoff, which also works (can see iMessages, websites, etc via that) and Software Update works, and apps 'sorta' work. I mean that you can open the Mac App Store and it shows listings, but downloading anything just hangs at spinning icons. Search is broken.

Spotify loads, logs in, but won't play anything. Just sits there indefinitely. So it's sorta online but not.

Unrelated but today my Vista machine wouldn't connect. It's getting wired connection via a range extender and it was showing green for good to go but Vista said no internet. I reset the extender, played with it for hours and it's blinking red for 'your network ain't available' but I'm online now. Typing this post. Modern hardware/network stuff is goofy. It's also got an odd default gateway that doesn't match my config but hey it's online I ain't messing with it.

 

[polyphenol]

My two PCs are in the shop in a building long, long away from the router and have no issues connecting. The Windows 10 PC is in the office right next to the router (which is sitting on the same desk). The 10 PC won't connect via wifi only ethernet (I think its wifi is bad TBH)

Only Apple won't connect wirelessly. Boss's iPhone, my iPhone, any iPad, any Mac (even those never associated with the network/never connected previously) just get APIPA addresses INSTANTLY. They don't even bloody try to get a DHCP address. Setting a static IP doesn't work with the Apple products, but does work with Windows. I've never heard of an issue that blocks specific manufacturer's products from a router. I'm blaming AT&T's router on this. They got a network tech coming out to upgrade the IP cameras to get away from the issues we've had with those (plus they only work via Internet Explorer anyway) and replacing some network equipment but since DSL is our only option I doubt there's going to be an easy solution because in my experience, DSL is apparently the new dial-up.

That reads as if "Is there a DHCP service avaiulable?" DHCP broadcast query isn't finding one!

 

[nickdalzell1]

Shouldn't it sit there waiting for a few seconds to a minute before giving up? It connects then instantly shows APIPA address. It's not waiting for a query at all. It's just giving up immediately. Also, why doesn't a static IP work around the issue? Works for Windows, but not any Apple device. I still cannot fathom anything about an Apple device that blacklists it from this particular network.

Network Utility goes immediately from 'wifi is not connected and does not have internet access' to 'Wifi has self-assigned address and may not have connection to the internet'

 

[mi7chy]

If you set a static IP and still get no connectivity then it's a lower than OSI layer 3 issue. Probably some router WIFI setting that the Apple clients don't like.

 

[nickdalzell1]

hmmm. Yeah it gets zero web connectivity but I get some type of partial connection since Handoff and Continuity work, and apps load data but that's it. I mean I can open Mac App Store and it lists stuff, but hangs downloading. Open Spotify it logs in, displays content but won't play anything. That's only with static IP.

 

[mi7chy]

That's weird. Seems to be broken between layer 3 and 2. Are you using IPv6 on LAN? Maybe try switching LAN to IPv4 only.

 

[nickdalzell1]

Nope. IPv6 has caused nothing but trouble on my home network and the work network. That got disabled in 2012. I know folks online whinge saying 'OMG people like you gonna make us run outta IPs!' but I don't care since it has not benefited me in any way. Kinda like 64-bit being the 'future'. I can't see any benefits to that either, only that some of my favorite apps and games won't work with it like Half life 2 and so on.

 

[PinkyMacGodess]

That reads as if "Is there a DHCP service avaiulable?" DHCP broadcast query isn't finding one!

OR finding more than one. A client tried to segment their network by using two Netgear access points, but they had the 'inside' networks facing each other. Their business network had two DHCP servers, and it depended on what one you got as to if you had any access.

You can't have two DHCP servers, unless you have them carefully setup to not overlap, but even then, you should only have one. I was surprised their network functioned at all. I set it up to work, and came back a few weeks later, and someone had undone the physical connections I had changed. You can't fix stupid?

 

[PinkyMacGodess]

Nope. IPv6 has caused nothing but trouble on my home network and the work network. That got disabled in 2012. I know folks online whinge saying 'OMG people like you gonna make us run outta IPs!' but I don't care since it has not benefited me in any way. Kinda like 64-bit being the 'future'. I can't see any benefits to that either, only that some of my favorite apps and games won't work with it like Half life 2 and so on.

Since most people use private addresses internally, it's not people like you or me that are wasting addresses. Years ago I read that cell phones are wasting addresses. I read part of it in passing, and haven't looked into it since. Didn't make sense, but what does these days... In subnetting there are addresses that are just not usable. The wastage is large.

Private addressing was created to deal with the overuse/limits of public addresses.

 

[nickdalzell1]

All over the internet are forums chock full of doomsday predictions that the world will 'run out of IP addresses' if we don't go head-first into IPv6 100%. That doomsday prediction means as much to me now as it did back in 2004 when I first heard of it. As in it means nothing. But still the myths that you 'should never uncheck IPv6 in Windows' keeps being promoted. Where's the 'anti-misinformation' campaign for that?

It doesn't take a college degree in IT to figure out when Vista claims there's an 'unidentified network' and has no internet that unchecking IPv6 magically fixes it.

 

[diamond.g]

All over the internet are forums chock full of doomsday predictions that the world will 'run out of IP addresses' if we don't go head-first into IPv6 100%. That doomsday prediction means as much to me now as it did back in 2004 when I first heard of it. As in it means nothing. But still the myths that you 'should never uncheck IPv6 in Windows' keeps being promoted. Where's the 'anti-misinformation' campaign for that?

It doesn't take a college degree in IT to figure out when Vista claims there's an 'unidentified network' and has no internet that unchecking IPv6 magically fixes it.

To be fair unchecking that checkbox in the network settings doesn't actually keep Windows from using IPV6. You have to go into the registry and disable it.

Open the registry editor. Press Windows key + R. In the Run dialog box, type regedit and click OK.
In the Registry editor, navigate to HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services > TCPIP6 > Parameters.
Create a new DWORD.
Right-click on Parameters, select New, then DWORD (32-bit).
Set the name to DisabledComponents and press Enter.
Right-click on the new entry and select Modify. Set the Hex value to FFFFFFFF and click OK.
Reboot the client.

 

[nickdalzell1]

Yeah I did all that and, surprisingly, the world didn't end.

I had already disabled it via the router so it's only getting link-local on the client end.