Windows 10 1607 won't update
-
Oh, and use it on any browser but IT - for some damned reason in IE, it wants to install an activeX control, but won't do it unless you're logged in locally as an Admin - and I think you have to have the site listed as a trusted site.
-
I just saw an article this morning that a new update for 10 breaks DHCP. I'll have to see if I can find it.
-
@stacksofplates said in Windows 10 1607 won't update:
I just saw an article this morning that a new update for 10 breaks DHCP. I'll have to see if I can find it.
I feel like things are going downhill quickly for Windows.
-
@scottalanmiller said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
I just saw an article this morning that a new update for 10 breaks DHCP. I'll have to see if I can find it.
I feel like things are going downhill quickly for Windows.
We have to do update testing for compliance. This makes me see why. The RHEL stuff is easy to roll back. I don't imagine the Windows 10 stuff is though.
-
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
-
@stacksofplates said in Windows 10 1607 won't update:
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
LTSB - lol.
-
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
LTSB - lol.
Ha I just copied it from the article. No idea if that's what it's actually called or anything about it. I've got a Server 2016 class in March so hopefully I'll pick up some info ha.
-
@stacksofplates said in Windows 10 1607 won't update:
@scottalanmiller said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
I just saw an article this morning that a new update for 10 breaks DHCP. I'll have to see if I can find it.
I feel like things are going downhill quickly for Windows.
We have to do update testing for compliance. This makes me see why. The RHEL stuff is easy to roll back. I don't imagine the Windows 10 stuff is though.
Different worlds.
-
@stacksofplates said in Windows 10 1607 won't update:
I just saw an article this morning that a new update for 10 breaks DHCP. I'll have to see if I can find it.
Holy crap! I'm not in the UK, but I had one windows 10 machine that would randomly just refuse to get an IP address from DHCP. I could eventually coax it to work again, but damn, talk about a hassle. I thought it was a wifi problem just on that one machine. I gave up and rebuilt it yesterday. No issues with it today.
-
@stacksofplates said in Windows 10 1607 won't update:
@scottalanmiller said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
I just saw an article this morning that a new update for 10 breaks DHCP. I'll have to see if I can find it.
I feel like things are going downhill quickly for Windows.
We have to do update testing for compliance. This makes me see why. The RHEL stuff is easy to roll back. I don't imagine the Windows 10 stuff is though.
With WSUS it's suppose to be, and I have used it to good effect in the past (an outlook update changed behavior users couldn't live with until the replacement update so I had to roll it back).
-
@stacksofplates said in Windows 10 1607 won't update:
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
LTSB - lol.
Ha I just copied it from the article. No idea if that's what it's actually called or anything about it. I've got a Server 2016 class in March so hopefully I'll pick up some info ha.
LTSB - Long Term Servicing Branch - i.e. some old version of Windows 10 that's still getting patches, but no feature updates. Kinda like MS supporting a non current service pack for a longer period than just 'until the next service pack'
-
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
LTSB - lol.
Ha I just copied it from the article. No idea if that's what it's actually called or anything about it. I've got a Server 2016 class in March so hopefully I'll pick up some info ha.
LTSB - Long Term Servicing Branch - i.e. some old version of Windows 10 that's still getting patches, but no feature updates. Kinda like MS supporting a non current service pack for a longer period than just 'until the next service pack'
That seems like a very bad idea.
-
@scottalanmiller said in Windows 10 1607 won't update:
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
LTSB - lol.
Ha I just copied it from the article. No idea if that's what it's actually called or anything about it. I've got a Server 2016 class in March so hopefully I'll pick up some info ha.
LTSB - Long Term Servicing Branch - i.e. some old version of Windows 10 that's still getting patches, but no feature updates. Kinda like MS supporting a non current service pack for a longer period than just 'until the next service pack'
That seems like a very bad idea.
Apparently large corps demand it. They don't want to roll out what are essentially Service Packs + feature updates on MS's new hyperspeed schedule. Since the release of Windows 10 we have:
July 2015 RTM
Nov 2015 1511 Autumn update
July 2016 1607 redstone 1
March 2017 1703 redstone 2 (now called the creative update)
Sept 2017 1709* <- this is a guesstimate.Sadly MS is still supporting all of them. Now, by redstone 2, they might finally dump support for RTM, but not sure.
-
@Dashrender said in Windows 10 1607 won't update:
@scottalanmiller said in Windows 10 1607 won't update:
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
@Dashrender said in Windows 10 1607 won't update:
@stacksofplates said in Windows 10 1607 won't update:
Here's a quick find. Looks like it might just be renewing and flushing DNS cache (for some).
https://www.neowin.net/news/microsoft-breaks-dhcp-with-latest-windows-10-update-suggests-a-reboot-to-get-back-onlineOnly in the UK though. Are they on a newer schedule?
Looks like LTSB isn't affected.
LTSB - lol.
Ha I just copied it from the article. No idea if that's what it's actually called or anything about it. I've got a Server 2016 class in March so hopefully I'll pick up some info ha.
LTSB - Long Term Servicing Branch - i.e. some old version of Windows 10 that's still getting patches, but no feature updates. Kinda like MS supporting a non current service pack for a longer period than just 'until the next service pack'
That seems like a very bad idea.
Apparently large corps demand it. They don't want to roll out what are essentially Service Packs + feature updates on MS's new hyperspeed schedule. Since the release of Windows 10 we have:
July 2015 RTM
Nov 2015 1511 Autumn update
July 2016 1607 redstone 1
March 2017 1703 redstone 2 (now called the creative update)
Sept 2017 1709* <- this is a guesstimate.Sadly MS is still supporting all of them. Now, by redstone 2, they might finally dump support for RTM, but not sure.
So instead of going to rolling releases, they just renamed their versions Windows 10 with a build number. No different than before, just a marketing change.
-
I'm not sure of the architectural changes under the hood so I can't really say.
But the main version changes in Windows 10 are considered by the media as whole new OSs, or perhaps versions is a better way to call it.
One thing for sure, Until very the next update, and perhaps really only after that update, these huge updates have required GBs of downloads, basically like reinstalling the OS. Its been reported that after Redstone 2 next spring, the future major updates won't require as much on the download side will only be new things, I guess they are continuing to work on their differencing engine so they can save on the downloads. -
http://www.theregister.co.uk/2016/12/14/microsoft_windows_10_dhcp/
I guess up config release and renew didn't work for a lot of people.
Someone pointed out that they put an update out online for people who can't get online.
