Windows 10 1909 Patches
Floriana Monterroza
I would also like to suggest some alternative way.
Try using third-party software instead of SCCM. For example, our free cloud-based product Action1 is capable of automating the update process , and you can also receive complete information about the installed patches and updates on your endpoints.
I am not seeing any updates for 1909 and I just added the selections for "Windows 10, version 1903 and later ". Doing a search for updates that are required and not downloaded and still not seeing any updates for 1909. Does it take some time before I will see these?
I am also having this issue, trying to update from 1809 > 1909 via windows servicing. This is not showing up in the software centre. Monitoring is showing as 100% success however winver shows 1809. Any suggestions.
More generally:
Gen 1 and 2 are not supported by Intel for Windows 10, while 3rd Gen only if supported by the OEM: Does My Intel Processor Support Microsoft Windows 10?
We have an article about CPU and GPU support on Windows 10: -us/articles/360008642799-Windows-10-Support-of-older-hardware
Using a Xeon E3-1231v3 in combination with an Intel z97 chipset mainboard and a simple GT710 VGA (WQHD resolution) and never run into issues specifically with Cubase 10/10.5 . I am using Windows 10 Pro N and removed most of the metro apps. Windows is on the latest release 1909 with most recent functional updates and patches.
Adding to the pain, Microsoft has a bad track record with Windows 10 feature updates, which are either bloated with new features that virtually no one wants, delivered in such buggy form that they must be pulled and reissued, or arrive much later than originally promised. Or some combination of those problems.
For Microsoft, it means that it can deliver a single patch for any vulnerability or bug, and not two versions, as it normally has to. That is, Windows 10 versions 1903 and 1909 will be serviced by the same patches, not different patches (as with all previous Windows 10 versions and previous Windows versions like Windows 7 and 8.1). This gets the software giant closer to its vision for Windows as Service (WaaS), a key tenet of which is that getting as much of the user base on the same Windows version, and thus the same servicing path, will be easier, more efficient, and thus more secure for everyone.
Inline notification management. Microsoft has made a few changes to the ways in which notifications appear in the Action Center in Windows 10 version 1909. Key among them, you can disable notifications from individual apps or services without having to navigate to Notification settings in the Settings app. The notifications settings interface for each app has been prettied up a bit in Settings as well.
I manage about 150 workstations in a work enviornment, which is not a lot, and I've gotten so tired of the constant need to upgrade our systems. We don't have Win10 Enterprise because of the costs, so we don't get the 30 months of updates on the "09" versions, so every single Windows install we have is only supported for 18 months. I still have about 30 machines on 1803, which goes out of support in November, which means I have until Patch Tuesday in December to get them updated. And then once I have them updated, I'll have to get started on the 50ish machines we have on 1809.
But this is a beacon of light. We've done a pretty big evergreening program in the last few months so I have about 75 computers on 1903, and I'm going to test the upgrade process on a few of them, but I'm not going to have to worry so much about this upgrade, and an just get them onto 1909. That means I'm going to have 75 machines I just don't have to worry about a version update on until at least late 2020, and that's going to give me a breather.
With 150 machines it's not like I spend all of my time doing version updates, but it's a lot more time than it should be, and a lot more time than it used to.
In reply to wunderbar:Totally agree! I have even less, probably 70 PC and 25 Surfaces. The PCs handles updates pretty well but my Surfaces will just flat out stop working (no wifi connection) or develop other issues when they have 'updates pending'. They magically work fine after the updates are applied. Luckily the Surfaces don't really hold any content so I try to round up all the 1803's and do a scratch install of 1903 from a usb key as its a lot faster than the update.
Presumably this is a typo: 1909 in "Windows 10 version 1903 at-a-glance".1903 changed many telemetry settings (other than those easily seen in the basic settings GUI) without asking. It will be interesting to see whether 1909 does NOT change any telemetry setting without asking.
looking forward to an ltsb version of this one to test! Should fix our last few niggling issues with the current ltsb which still has a painfully slow search functionality under the start menu where it does not catch your first 2-3 letters of your search.
In reply to Stooks:My biggest issue with Windows 10 (yes even with "active hours" set up) is that it reboots when it wants to.What they should advertise is that with MacOS, Linux, and previous versions of Windows, you could keep a complex desktop with open files and applications across multiple days or weeks as you work on things. With Windows 10, you have to be prepared to have the system shut you down in the middle of all that work in progress, any night. That is a huge PITA.
In reply to Stooks:It's great if Windows 10 works for you and you never have issues. However, I'm betting your case is not an enterprise experience. The issues related to Windows 10 for enterprises are numerous. WaaS as it exists now is untenable in the enterprise. Hence all of the complaining you are reading about.
And the new update experience Paul is writing about is only true for those going from 1903 to 1909. Enterprises will be going from 1809 to 1909 due to the 30 month support window for both. So we cannot take advantage of this new update experience.
In reply to crp0908:Like I said we have over 6000 Windows 10 installs. Is that "Enterprise" enough for you? We did use LTSB for about 1000 of those installs (retail POS) and I am not sure if that is still the case, as in that is not my department in IT.
We primarily use WDS to deploy. We did have issues early on with removing some stuff we did not want the users to see, just to cut down on support calls when they opened something that had nothing to do with their jobs. Those issues are gone now.
In reply to Stooks:Microsoft's official policy for fixing bugs is to complain on the internet, so don't complain about that.
I've, never, ever heard an experience as seamless as your for a Windows Service Pack (which is basically what these are) in more than 2 decades of doing this. And I've personally seen IT shops struggle with Windows 10 in uniquely terrible ways.
Yes, they're both anedotes, but since MS collects the data, and has made this course correction, it's at least possible that your experience is the unique one.
This release is very interesting. If I understand correctly, Microsoft can release feature updates piecemeal / under the radar, and then enable them via enablement packages. So users can 'opt in' to the 1909 update, but really, the bits are on their machine already. Whether they opt in or not?
This doesn't get said enough: as long as it's painless to install Classic Shell, Start 10, etc to provide alternative launchers for Windows 10, it's all good. Lots of improvements behind the scenes even if the default launcher is, er, an acquired taste. MSFT deserves credit for keeping this simple and far more comprehensive than anything available for macOS.
This article is saying you want a feature update that has no feature updates. I would prefer a feature update that has improved feature updates so everything they added previously is further improved. Then people will use them properly instead of ignoring them. They also took away features and gave us worse features. Perhaps put them back with upgraded features. In any case, Microsoft keeps tinkering with Windows to make it more mobile, but they don't work properly. Sorry to say this, but Google and Apple does this much better than Microsoft.
When Microsoft announced two feature updates per year, I wondered how long they could keep coming up with new features (wanted or not). I guess the answer was two years. If they are going this route, maybe they should make H1 a UI, bug fix and security update. H2 could focus on making Windows run more efficiently, bug fixes and security updates.
Side question: Does the addition of Windows 10X mean Microsoft will be less likely to remove legacy code from Windows 10?
To counter this the organisation I work for (large in its market) has gone from irregular long delayed system updates to being current and much better because of the consistency of Win 10/Office 365 updates. You can share info across functions knowing the recipient will have the resources/access to use it.I get a bit tired of the 'updates no one wants' line too as it harks back to the 'everyone on only needs 10% of X, but everyone uses a different 10%' issue. As an example; While the Windows Mixed Realty might be considered a waste of time for most it was vital for our function. Could argue 3rd parties would have filled that gap but then you get the mix of solutions/standards, patches etc which cause all sorts of problems.
In reply to robincapper:
Hear hear.
There's a bunch of stuff in Windows 10 20H1 which is "done", like showing an FPS counter in any application, GPU temperature monitoring in Task Manager, and setting limits on how fast updates can be downloaded.
This stuff could ship with 19H2. But no, we have to wait another 6+ months for this to appear in a non-tester version of Windows 10.