Windows 10 October 2020 Update arrives: Nothing that will drop your jaw, but we've had enough of 2020's fun surprises anyway
- Reference: 1603279805
- News link: https://www.theregister.co.uk/2020/10/21/windows_10_october_2020_update/
- Source link:
After lurking in the beta and release preview channel of the Windows Insider program for what seemed like an age, the Windows 10 October 2020 (aka 20H2) has arrived, bringing with it Microsoft's new Chromium-based Edge browser and, frankly, precious little else.
The glorified update follows the pattern established in 2019, where a major update hit during the spring, and something that felt a whole lot like a cumulative update arrived in the autumn. While the approach might be a little frustrating for Windows enthusiasts, those looking for stability on the desktop will welcome a repeat of the approach - certainly after the mayhem unleashed by the infamous [2]Update of the Damned back in 2018.
Things are altogether more sober this time around, and many of the toys lurking in the update are likely already on users' PCs, requiring only a flick of a switch from Microsoft to activate them rather than a bandwidth-destroying download. That's assuming, of course, those PCs are on the Nice list: as before, Microsoft is "throttling availability" and restricting devices to which the update is offered.
As for what is actually in it, other than the new Edge, there isn't a huge amount. The Start Menu has been given a lick of paint, as Microsoft gingerly applies dressings to the self-inflicted wounds of Windows 8, Alt+Tab will flick through Edge tabs as well as apps and logos on notifications will make it easier to identify where they are from.
The overall interface has been polished up a bit, but nothing that will frighten the horses, with minor improvements when the screen is detached on 2-in-1 devices, and a decluttering of the taskbar for new logins.
These "H2" updates tend to attract the attention of the commercial world since not only do they benefit from the fixes rolled out after the "H1" release, they also enjoy [3]30 months of servicing (longer for a Long Term Servicing Channel version) rather than the 18 months of the latter.
This time around, those commercial customers saw updates to the Mobile Device Manager (MDM) with a Local Users and Groups policy that gives administrators the same options as on-premises Group Policy, a more secure biometric sign on and beefed up protection for Microsoft 365 and Edge via the Windows Defender Application Guard.
Despite the lengthy gestation of the build (and the fact that much of the codebase is shared with May's update), there are still issues. One, where Windows throws up an error during the installation of third-party drivers, has been resolved, while others (related to [4]Conexant drivers ) remain.
Enthusiastic users wondering why Windows 10 20H2 is refusing to put in an appearance on their kit would be advised to check out Microsoft's helpful [5]health dashboard for pointers with regard to what is blocking an update. Otherwise it may simply be a case that you have yet to migrate to Windows Update's Nice list. ®
Get our [6]Tech Resources
[1] https://blogs.windows.com/windowsexperience/2020/10/20/whats-new-in-the-windows-10-october-2020-update/
[2] https://www.theregister.com/2018/10/23/microsoft_windows_10_crisis/
[3] https://docs.microsoft.com/en-us/lifecycle/faq/windows#windows-10
[4] https://www.theregister.com/2020/07/01/windows_10_2004_rollout/
[5] https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-20h2
[6] https://whitepapers.theregister.com/
Re: Update blocking info
My 2004 update was blocked apparently because I had a Ryzen CPU and Motherboard. Not sure if it was the CPU or the motherboard though.
I tried to update to the 2020 install last night. When I got the notification the update was ready to install, I clicked "Restart" and the PC restarted quickly. Although the version does now show as the 2020 build, I'm not convinced. I didn't see any difference on the desktop, and the PC did not display any of the normal "Windows is updating, do not shut down" or "We are installing a new feature update" message.
Also, it took several reboots for Windows Update not to hang (it did this repeatedly, despite the Windows Update Troubleshooting wizard finding nothing).
When I get home, I'm going to a try a re-install, to see if that sorts the problems.
Re: Update blocking info
If you run "winver", it tells you what build you're on. I'd recommend checking before doing a reinstall.
Re: Update blocking info
When I get home, I'm going to a try a re-install
Last year I built a Ryzen system with FreeBSD on it. no problems related to CPU nor motherboard.
But, since you're re-installing anyway... got Linux? (or BSD)
Re: Update blocking info
The version of FreeBSD running my pfSense 2.4.5p1 doesn't let me create queues on the NIC because ALTQ is disabled because they couldn't deploy a stable solution being Intel NICs capable of 10Gb.... should I switch to something else?
Re: Update blocking info
I had the same issue with v2004, refusing to install on Zen2+X570 meanwhile my i7-4770k system from 2012 updated to v2004 without issue.
I checked all my motherboard, chipset and peripherals for updated drivers and I was already on the latest driver for all of those, so I went through the MS Update Assistant to force v2004 onto my system and everything worked perfectly fine post install and I never unplugged any peripherals pre-update.
Previously on my i7-4770k system Windows Update itself b0rked that machine from recieving any updates (even the usual minor suspects - dotnet, defender etc) and I had to force it to update to v1909 by using the often never mentioned Upgrade-In-Place option, ever since it has been fine and v2004 installed first time with no issues.
IMO the Windows Update system, while it is great for keeping everything updated, is not free of its own self-defeating flaws which I have experienced twice on two entirely different systems running different versions.
In any case I'm going to let the v20h2 update hold off for a week on both systems before I take the plunge as I'm fairly sure there will be the usual MS-snafu of something breaking along the way that hasn't been reported yet.
the known issues list isn't as bad as the last one
So, beta quality this time then?
Please God nooooo...
I was cooking my mince naked yesterday when I accidentally clicked on Solitaire. I then spent the next hour going through some hell usually only reserved for people who click "user preferences" when trying to avoid cookies on a web site. This little gem was obviously installed when I connected to the Internet a couple of weeks ago and as part of some update I didn't want, ask for and thought I'd switched the service off. MS seems determined to kill off as many of its customers as possible so it can concentrate on all that cloudy goodness (profit).
Just installed it.
Read the article, thought I would give it a shot. Took 5 minutes to download and install, started the reboot, went and made a coffee, came back, watched the restart complete and logged back on. Total time, less than 15 minutes. Issues none. I did notice that I went from Version 2004 to 20H2. This is how an update should be. I must however note that I have never had an issue with bad updates on this or any of my other machines.
Update blocking info
Quote: "Enthusiastic users wondering why Windows 10 20H2 is refusing to put in an appearance on their kit would be advised to check out Microsoft's helpful health dashboard for pointers with regard to what is blocking an update."
Would be nice if there was some way for system specific issues, i.e. update blockers, to be shown on the machine itself. i.e. Under Windows Update.
2004 was blocked on my desktop PC until just a couple of weeks ago, (I was on 1909). Up to that point it just provided a generic message letting me know 2004 wasn't 'ready' for my machine and that it was being worked on. Then 2004 just turned up one day!
Presumably something specific must have been blocking it on my system. I have no issue with the blocking itself, e.g. if that avoids blue-screens due to incompatible drivers etc. But it would be nice to know exactly what did cause the block, as then I could potentially have a looked at resolving the issue myself. (e.g. If it was some driver issue with a peripheral plugged in but not used often, I could unplug and uninstall the drivers).