Last One To Post Wins [132]

Access Denied said:

Hiya Josey

How was work today?

Josey Wales said:

How was work today?

The usual good day. It was really nice with the cooler weather. It will be even cooler tomorrow

Access Denied said:

The usual good day. It was really nice with the cooler weather. It will be even cooler tomorrow

It is going to be cooler here as wee.

Josey Wales said:

It is going to be cooler here as wee.

Yup, about 10 degrees cooler here as well. Less sweating at work will be nice. I know it is good for you, but I get tired of sweating so much my clothes are soaked lol.

Just found a weird bug in 1809. If you connect to a different network, or at least for me, the MS Store and any apps that are from it.... will not see the internet. I had to do a network reset like I did to fix this, when I first upgraded to 1809 as well.

Access Denied said:

Just found a weird bug in 1809. If you connect to a different network, or at least for me, the MS Store and any apps that are from it.... will not see the internet. I had to do a network reset like I did to fix this, when I first upgraded to 1809 as well.

Make sure IPv6 is enabled on your LAN. Store and all Apps, including Edge depend on it. May not be your issue, but it borked all of mine till I enabled it.

f14tomcat said:

Make sure IPv6 is enabled on your LAN. Store and all Apps, including Edge depend on it. May not be your issue, but it borked all of mine till I enabled it.

I disable IPV6 thru my LAN device. IPV6 on Comcast here is slowwwwwwwww, with packet loss and just horrible. I have not used IPV6 in months and the Store + all apps work just fine.

17 hours ago they pushed a firmware (bad I might add) to my ISP provide modem, which turned back on IPV6. So today I then broke out my dependable 'ol wifi router and plugged it up, set it all up and connected my PC to it. Win10 detected the new network and connected just fine. The issue with the Store and apps resurfaced just as it did on my first install of 1809. Both times it took a Network Reset. Both times also the device my PC was connected too, had IPV6 disabled, so there was no way I could pull an IPV6 and the Store and apps worked fine.

I can see after you saying that... the network reset enabled IPV6 on my LAN properties but it cannot pull an IPV6 address. Weird that it has to be enabled, even if it cannot pull an IP for IPV6

Access Denied said:

I disable IPV6 thru my LAN device. IPV6 on Comcast here is slowwwwwwwww, with packet loss and just horrible. I have not used IPV6 in months and the Store + all apps work just fine.

17 hours ago they pushed a firmware (bad I might add) to my ISP provide modem, which turned back on IPV6. So today I then broke out my dependable 'ol wifi router and plugged it up, set it all up and connected my PC to it. Win10 detected the new network and connected just fine. The issue with the Store and apps resurfaced just as it did on my first install of 1809. Both times it took a Network Reset. Both times also the device my PC was connected too, had IPV6 disabled, so there was no way I could pull an IPV6 and the Store and apps worked fine.

I can see after you saying that... the network reset enabled IPV6 on my LAN properties but it cannot pull an IPV6 address. Weird that it has to be enabled, even if it cannot pull an IP for IPV6

It's not that it's using IPv6 for any DNS lookup. Rather, MS uses it in pseudo-links to it's Store and App Content. No DNS lookup involved. I don't understand all of it, but I know I had it disabled, and NONE of my Store Apps would work at all. Just sat there spinning. Soon as I enabled IPv6, wham - all came up.

f14tomcat said:

It's not that it's using IPv6 for any DNS lookup. Rather, MS uses it in pseudo-links to it's Store and App Content. No DNS lookup involved. I don't understand all of it, but I know I had it disabled, and NONE of my Store Apps would work at all. Just sat there spinning. Soon as I enabled IPv6, wham - all came up.

Same here, but I went the full everything route to fix it, because it worked last time LOL.

Good evening AD, I thought you were on 1803.....guess you decided to run 1809