Windows 10 1903

Windows 10 1903 Cumulative Update (Build 18362.207)

1) Servicing Stack Update KB4506933 = http://download.windowsupdate.com/c..._9505dd15c7588513f12aeb9efae1934e65e55efe.msu

2) Cumulative Update KB4501375 = http://download.windowsupdate.com/c..._c54071d9b24a8efb7a48714883cf141a66b8c395.msu

3) .NET Framework Update KB4502584 = http://download.windowsupdate.com/c..._77c9c7f5f6cb837eafb42ef19db3581263a6730d.msu

4) Adobe Flash Update KB4503308 = http://download.windowsupdate.com/c..._b6478017674279c8ba4f06e60fc3bab04ed7ae02.msu

5) Intel Microcode Update KB4497165 = http://download.windowsupdate.com/d..._3fa260a5560cd843d467116267d0b5de9b1e148a.msu

Spoiler: Changelog

Here is what is fixed and improved in the new update:

• Fixed a cursor display issue when moving the cursor over the keyboard magnifier.
• Fixed a redirects issue in Edge and Internet Explorer 11.
• Fixed an issue with Scalable Vector Graphics marker display.
• Fixed a programmatic scrolling issue in Internet Explorer 11.
• Fixed a display issue in Internet Explorer caused "under certain conditions" on sites with "many elements and multiple nesting levels".
• Fixed Error 1309 when installing or uninstalling certain msi or msp files on a virtual drive.
• Addressed an issue that caused Night Light, Color Management profiles, or gamma correct to stop working after shutdowns.
• Fixed an issue that showed grayscale only during Windows Hello enrollment.
• Fixed an issue that caused playback of iOS media to fail under certain circumstances.
• Fixed a taskbar and desktop flickering issue in Windows Server 2019 Terminal Server.
• Fixed a policy issue that allowed users to set backgrounds even though a policy to prevent that was set.
• Fixed a connection issue when using fitness software on Android devices with Your Phone installed.
• Fixed a Windows Event Log issue that prevented the service from processing notifications that the log is full.
• Fixed an Office 365 opening issue when deployed as App-V packages.
• Fixed an issue that prevented Container Hosts from receiving addresses from DHCP servers.
• Addressed an issue that prevented Windows 7 to 10 installations from completing when certain antivirus applications were installed on the system.
• Reinforces the Certificate Revocation List on Internet Key Exchange version 2 machines for certificate-based virtual private network connections.
• Fixed an issue that triggered Group Policy updates even though there were no changes.
• Fixed the Preboot Execution Environment startup issue.
• Fixed the Custom Views issue in the Event Viewer.
• Fixed a WinHTTP registrations issue that delayed the startup of the operating system. The issue occurs on devices with proxy auto-config files. Microsoft notes that admins need to make the following changes to the Windows Registry to stop the incremental growth of the Registry:
  • Path: HKEY_CURRENTUSER\"Software\Classes\Localettings\Software\Microsoft\Windows\CurrentVersion\AppContainer\Mappings"
  • Setting: CleanupLeakedContainerRegistrations
  • Type: DWORD
  • Value: 1 (1 removes preexisting registrations, 0 retains them)

Microsoft lists just one known issue for KB4501375. The sandbox issue is still a thing in the new version.

 

Of course can't Micro$oft push out new patches without breaking something else
Windows 10 1903 Update Bug Causes RASMAN Service to Hang
In a new update to its support document, Microsoft has confirmed that Windows 10 May 2019 Update (version 1903) could break the Remote Access Connection Manager (RASMAN) service on some devices.

Why I recommend pausing Windows updates every month
http://forum.notebookreview.com/threads/windows-10.762434/page-567#post-10927787

 

On several of my PC’s running 1903 i’ve noticed that they now request me to manually download updates. Guess what, I ain’t pressing that download button.

The last thing I need is for MS to trick me and put me in the Update Beta program.

 

Yeah, I wouldn't touch that button

Btw. Want this?

Cortana Beta App for Windows 10 Appears on Microsoft Store
A beta version of an independent Cortana app has appeared on the Microsoft Store and it could finally allow Microsoft to update digital assistant with new features more frequently.

 

I cannot identify any legitimate need for Cortana bloatware to exist, much less be updated or more "features" added. Utterly worthless, silly, pointless smartphone rubbish for PC.

 

A bit of dilemma for me. I just made a custom W7 with latest updates integrated and was testing on a VM and Scaling on FHD display with full screen mode was much better than Win 10 v1809/1903. The ISO is small around 2.7GB with Pro and Ultimate version in ESD format.

 

How or why is that a dilemma? We already knew Windows 7 was superior to Windows 10 and this is simply additional corroborating evidence of that fact.

 

New is always better

Windows 10 v1903 still plagued by latency and audio spike issues Windowsreport.com | July 1, 2019

Although some time has passed from the official release of Windows 10 May update, many bugs and software issues still remain unresolved.

What’s worse is that new patches don’t solve the old problems, but create new ones. That’s the case with Windows 10 v1903 Build 18362.207 which has a lot of problems with high latency and audio spikes for many Windows 10 users

---------------------------------------------------

NetMarketShare
About 35% of all Windows PCs are still running Win7, just a bit behind Win10.



Maybe Micro$oft should stop releasing 2 main Win 10 upgrades a year? All they create is a Huge mess for the users. And for themself!

https://reports.adduplex.com/#/r/2019-06

Windows 10 May 2019 Update (1903) has gained around 5% since last month and is now on 6.3% of close to 100,000 PCs surveyed.

"This puts it on par with the pace of 1809 one month after its re-release. And this is, probably, not a good sign as we've seen how this ended (just over 30% install base before the next release went out)."

 

Not quite the "big splash" the Redmond Retards have been striving for.

 

What I find really interesting is the gall is takes for the goons from Micro$lop to think they can just wave their magic wand and say *poof* " we don't support 50% of the world's Windows users any more" LOL. With about 2% difference in size between the Windows 7 and the Windows 10 user base, and Windows XP and 8.1 users (just under 5%) added in, Windows 10 users are clearly representative of less than half of all Windows OS users. This month is the 4th anniversary of the official release of Windows 10 and they still haven't hit the 50% mark. So, they're really pushing their luck with the Nazi control freak tactics. It can still bite them in the butt, and they'd do well to mind their P's and Q's if you ask me. The bigger they are, the harder they fall.

 

We can talk about MAGIC And I don't talk about a new Screw up from Redmond Moron HQ. New Version of WPD is aviable.


http://forum.notebookreview.com/threads/windows-privacy-dashboard.825321/page-2#post-10928318

 

Windows 10 Cumulative Update 1903 (18362.239)


1) SSU (Servicing Stack Update) KB4509096 = http://download.windowsupdate.com/d..._7037ec335c58a4d6afa92c0d54c1f4400ad59372.msu

2) CU (Cumulative Update) KB4507453 = http://download.windowsupdate.com/c..._79902381f303bd21104b0f9067c086e5dd6cd3f2.msu

3) .NET Framework Cumulative Update KB 4506991 = http://download.windowsupdate.com/d..._a0962ce8ceeb7faf10c6c95696eca09b36563f76.msu

4) Adobe Flash Player Update KB4503308 = http://download.windowsupdate.com/c..._b6478017674279c8ba4f06e60fc3bab04ed7ae02.msu

5) Microcode Update KB4497165 = http://download.windowsupdate.com/d..._3fa260a5560cd843d467116267d0b5de9b1e148a.msu

 

What's the difference between a SSU and the cumulative update?

 

SSU (Servicing Stack Update) is a pre-requisite update which needs to be installed before you can install the CU. sometimes it is not needed if it's already installed or the SSU hasn't changed since the last cumulative update but in this week's updates it HAS changed so you wanna install that and the other updates in the order I've listed.

Be smart...be like Ultra Male....

 

After many hours of trying to get the update to run, someone posted the solution on another board: Turing off Secure Boot in the BIOS allows the update to run on my Gigabyte P35x v5. I'm not sure why techs from Gigabyte and Microsoft didn't think of it, but I'm happy it worked. I'm now at 18362.239.
Best,

Joe

 

Question? If you pause the updates for a few weeks then click on "resume updates", does that automatically put you in the Windows Update Beta program? I ask because as soon as I clicked "resume updates" all the updates that wanted me to manually download began to automatically download.

 

I don't know that it is intended to do that. Hopefully, not. I'm guessing it was a glitch.

 

Why would you jump to calling it Beta? Did the updates say Beta?

If you click resume updates then yes any waiting updates will automatically start installing.

That's why I don't like Windows 10 updates, they just come in and start installing and you don't have any say over which ones do or don't get downloaded and installed.

On previous Windows versions you'd get a list of recommended and optional updates and you could uncheck recommended updates and check optional updates to moderate your update downloads / installs.

With the old method you could ignore old driver updates - you've already downloaded and installed newer versions from the product vendor - and you could uncheck and not install updates that are problematic.

With Windows 10 you get all of them, and then you can uninstall the ones you don't want, but they will come right back as soon as you enable updates again.

 

No, they didn't say Beta but I remember reading that if you click on "Check For Updates" it starts checking and downloading what's termed as B and C updates which Microsoft classifies as Unstable/Beta updates.

https://www.howtogeek.com/369656/do...-unless-you-want-unstable-windows-10-updates/
Does this still hold true if you manually check for updates?

 

If you are pausing and unpausing updates that isn't the same as manually clicking "Check for updates", so no in that sense you aren't changing to getting "beta" updates.

As per Microsoft:

“We Encourage You Not to Click ‘Check for Updates'”

"As Microsoft revealed, only people who clicked “Check for Updates” got bitten by Windows 10’s file deletion bug. When you click the “Check for Updates” button, Microsoft gives you updates early, skipping a normal part of the testing process."

Which is also a really bad change of effect for a long time standard user operation to "Check for Updates" to see available updates before deciding to select and download / install them.

MS has really screwed up the whole Update process by deciding to force updates, then be pounded on by users until MS decided to give users control to pause updates - even if only for a limited time - but still Windows 10 has reduced flexibility in it's inability to selectively choose updates instead of a single on/off spigot setting, "pause".

I use Shutup10 + WPD to disable / block Windows Updates - as well disable a whole bunch of other privacy and useless cruft, and you can then re-enable Windows Updates in both tools - reboot - in order to take Windows updates.

The recommended method is to leave Windows Update disabled all of the time and to manually download and install desired updates, although that can be time consuming it's the only sure way to know what you are updating and why.

 

This takes below 10 min of your time. And there is no need for driver updates pushed out from Redmond HQ.

 

Yes, this is very wise. I have been using all versions of Windows with updates disabled for like 7 or 8 years now, and that has always served me extremely well. I have never had any system screwed up by Windows Updates since I started playing god of my computers and allowing nothing to occur unless I do it on purpose. And, with a Macrium Reflect image ready to fix my mistakes there have been zero mishaps or regrets. A few times I erred in my judgment allowing updates without a Macrium Reflect image and it was my fault when things turned out to my own chagrin.

Indeed. If you are very selective and don't fix anything that isn't broken, that doesn't leave many "important" or security updates to ponder whether or not they need to be applied. Feature updates are almost always retarded. "Important"updates are generally unimportant. "Security" updates deserve consideration if you are paranoid. Driver updates should almost never be allowed if the system functions correctly. You can almost always get what you need, if you actually need it, directly from the device manufacturer. Assuming that newer is better is stupid. Micro$lop drivers frequently are the best, often not the newest, frequently have missing features and are often lacking in some functionality. Cumulative updates and roll-ups are usually trojans that should be scrutinized closely if not avoided.

 

When blocking Windows 10 Updates, you have to be vigilant in maintaining your regimen of blocker app settings - especially if you run an Update - manually or via allowing Windows Update to get the latest updates. And, don't forget to reboot for those changes to take effect...I left Windows Update Service running...

After you run a Windows update go into O&O Shutup10 / WPD and re-set to disable Windows Updates, because a applying a Windows Update may re-enable Automatic Windows Update. And, don't forget to reboot for those changes to take effect... sigh.

Today when I was making the post describing the tools I use to block Windows Updates I tested enabling Automatic Windows Updates (for Science) - rebooted - allowed the Updates (yes it's risky), then went back and re-set the options in Shutup10 and WPD, but got distracted and forgot to reboot and didn't use WUB to verify Windows Updates were blocked.

WUB on it's own can block Windows Updates, but since I am already using Shutup10 and WPD I only use WUB as a sanity check to verify Windows Updates have really been disabled.

Just now I noticed I have a Windows notification, and it was requesting a reboot to apply Windows Updates - automatic updates done since I did the test earlier today and accidentally left Windows Update Service running. Fortunately nothing bad happened (I hope).

So I checked Shutup10 and sure enough the last 2 options in the Windows Update section were Red, and should be Green - blocking as shown here.


My failure to reboot after changing settings in Shutup10 / WPD allowed the Automatic Windows Update to run - the Windows Update service wasn't stopped - and the Automatic Windows Update went in and re-enabled itself.

It's fixed now, and I verified by checking the state of Windows Update with WUB:


WPD blocking shows green as well:


This is another reason I don't like Windows 10, hyper-vigilance isn't 100% possible, human distractions or errors can bite you when these things are being reset by Windows 10 Updates.

 

The cancer continue. With Windows Update enabled you have a Ticking Bomb in front of you...



Microsoft Acknowledges Another Bug Brought by the Latest Windows 10 1903 Cumulative Update

The initial roll out may have been near flawless, but the Windows 10 May 2019 Update has now fallen into the same pandemonium of problems over problems. Regardless of how few users may be affected, it goes without saying that an update that is supposed to bring fixes should not be bringing more issues to users.

 

Jeez, they can't even manage to get it right for their own products.

"To safeguard your update experience, we have applied a compatibility hold on Surface Book 2 devices with Nvidia dGPUs from being offered Windows 10, version 1903, until this issue is resolved."

https://docs.microsoft.com/en-us/windows/release-information/status-windows-10-1903#517msgdesc

btw "To safeguard your update experience" "applied a compatibility hold" etc ...who the heck is responsible for their use of such utterly stupid wording.

 

In the past 1-2 yrs, Apple has gotten just as bad with some of their updates as well.

 

assuming you are using the latest version of O&O Shutup10 because only the latest version of that tool supported the Win10 v1903 release. older versions of Shutup10 may not work with the newest Win10 version like 1903. O&O didn't yet update their Shutup10 page to mention 1903 support.

 

Already posted long time ago that Microsoft has lackluster test routines. They isn’t able to test it properly

You mean older or newest version?

 

Yup, I downloaded the latest and so far it's all working great. Thanks for suggesting I check for a new version.

The OOShutup10 About menu selection gave me the details about the environment and version:


And, there is a link at the bottom of the Main UI top level that lets you check for the latest version, and when I clicked it after install - just to make sure - it verified I have the latest version:
https://www.oo-software.com/en/shutup10/latest-version

The need to reset the options after Windows Update is run, or a patch is installed (?), is due to Windows installer / Update munging around in it's installation state to "self-repair" itself. So we need to re-run any tool that changes Windows Update settings after Windows Update or manually installing a Windows patch, re-apply the changes we desire, and then reboot for them to take effect.

 

I almost never need touch O&O Shutup. I disable Network, turn on WUB and run the patch installers I want. The machine re-boot back to Windows again and I disable Service with WUB and then connect to the netwoork. It's very rare there will be unwanted changes so I need re-add settings in O&O Shutup. Same also with WPD. But expect new firmware rules will come right before and or right after new Patch day. Check it so you won't be fooled by Mircro$lope.

 

It may be rare but I check to be sure both for option changes and for the services to have been restarted. It only takes a few moments and I update rarely so it's not a burden. That is also good time to check for new versions of privacy / security apps, and run the new version and check for new options.

 

the 1903 media creation tool is now downloading build 18362.239 (1903 + KB4507453) ESD files like these ( 32bit) ( 64bit) [en-us client consumer]

 

Cumulative update for v1903 - KB4505903 (build 18362.267)
https://www.catalog.update.microsoft.com/Search.aspx?q=4505903
https://support.microsoft.com/en-us/help/4505903/windows-10-update-kb4505903

also new Servicing Stack update for 1903 - KB4508433
https://www.catalog.update.microsoft.com/Search.aspx?q=4508433
https://support.microsoft.com/en-us/help/4508433/windows-10-update-kb4508433

 

Cumulative Updates for Windows 10 1903 18362.295 (KB4512508) August 13, 2019

Known issue with the KB4512508

• Windows Sandbox does not start 0x80070002 - Microsoft is working on a solution
• Devices that start with Preboot Execution Environment (PXE) images from Windows Deployment Services (WDS) or System Center Configuration Manager (SCCM) might not start with a "Status" error: 0xc0000001, Info: A required device is after the Installing this update on a WDS server is not connected or can not be accessed ". Again, Microsoft is working on a solution

Fixed issues with the KB4512508

• Fixes a problem that can prevent devices from booting or cause them to continue to be restarted when connected to a domain configured to use MIT Kerberos realms. Both domain controllers and domain members are affected.
• Windows Application Platform and Framework security updates, Windows Storage and Filesystems, Microsoft Scripting Engine, Windows Input and Composition, Windows Wireless Networking, Windows Cryptography, Windows Data Center Networking, Windows Virtualization, Windows Storage and Files, the Microsoft JET Database Engine, Windows Linux, Windows Kernel, Windows Server, Windows MSXML, Internet Explorer and Microsoft Edge.
• support.microsoft

Manual download of the KB4512508

 

KB4512508 Failed cant get it to install, same issue as last months one even though I installed KB4508433 first which installed without a problem.
Seems like it's a issue according to this site for quiet a few people.
https://windowsreport.com/kb4512508-error-0x80073701/

 

And new is better @Mr. Fox @Falkentyne @Vasudev +++

"This is quite a worrisome normal trend, as the last month’s Patch Tuesday brought a lot of problems. Some of them haven’t been fixed yet, and Windows 10 users are getting more and more annoyed"

 

Didn't even download the offline update, I usually wait for a week or two after GP testing is done.

 

I've got an update waiting that says click here to download and install. Haha i'm not pressing that red button. I'm just going to wait for 1909 since it's supposedly going to be a traditional SP.

 

I updated, it's fine

 

Always fine

Report that Win10 1903 cumulative update KB 4512508 clobbers Outlook 365 startup
Posted on August 14th, 2019 at 14:39 woody Comment on the AskWoody Lounge
A new report from the patchmanagement.org group:

KB 4512508 causes Outlook 365 (Version 1902 Build 11328.20368 Click-to-Run – July version) to get stuck on loading profile. Uninstalling KB4512508 corrected the issue.​

I don’t see this listed as a known bug in either Win10 1903 or in Office.

 

As you can see "New" is always better I talk about the OS and the patches.

August Windows 10 Update Fixes Critical “Wormable” Bugs – But, It Fails to Install and Causes Random Restarts for Some Users

The problems affect only a small number of users, but that doesn’t mean the operating system is flawless. Microsoft seems to have a long way to go before it can deliver updates that are trusted by its users pushing them to install these updates as soon as they are released. Right now, even when some of these updates are carrying fixes for serious vulnerabilities, users have to think twice before installing these updates because they don’t know what surprises await them.

------------------------------------

Latest Surface Pro 6 and Book 2 Updates Are Causing CPU Throttling and WiFi Issues

The Windows maker has historically had issues with the quality of updates it delivers to Windows 10. While the company promised to improve the quality of updates after the disaster that was the version 1809, users are yet to get out of this “beta update” cycle.

 

I didn't update to latest version. Haha...

 

@Papusan I did more digging into Surface Pro 0.4GHz bug and looks like I discovered that few weeks back on my colleague's PC on HP skylake laptop. The CPU was stuck at 0.4GHz forever and I had to turn off fast startup and it brought back the clocks to advertised 3.3GHz on single core and 2.9GHz on all core active. After reboot, the CPu was stuck at 0.4GHz again and I use TS to prevent that issue and switched to Speedshift and now its super snappy! The odd thing here is, Win 10 was v1803 and not v1903.

 

What a beauty...



Microsoft Confirms Windows 10 1903 Update Error 0x80073701, Working on Fix
In an update to the Windows 10 Health Dashboard, Microsoft has confirmed that they are working on a fix for the 0x80073701 error that users are receiving when installing new v1903 updates.

And what will they break with the next patch who will fix this mess?

-------------------------------------

And no love their new and shiny. Afraid screw up too much so Win 7/8.1 users won't jump on it?

Microsoft: These Windows 10 updates fix broken Visual Basic apps but not for 1903
Microsoft rushes out fix for Visual Basic problems affecting Windows 10 to Windows 7, but version 1903's update won't arrive until August's end.

 

Lovely? When will they make a OS that works properly? And when will they start making patches that doesn't break their new and shiny after each and every update? @Mr. Fox New is always better
Windows 10 1903 Bluetooth speakers will not work after July update workaround Deskmodder.com | Aug 23, 2019

Microsoft has today made a contribution to the problem that after the July update ( KB4505903 ) Bluetooth speakers can no longer function when an internal speaker is installed. The possible error messages:

• A Bluetooth speaker can not connect to the computer.
• A Bluetooth speaker can connect to the computer. The speaker output sounds noisy (poor quality).
• A Bluetooth speaker can connect to the computer. However, the sound is generated by the internal speaker, not the Bluetooth device.
• In addition, you will see an entry in the Device Manager under the entry Sound, Video and Game Controller for Microsoft Bluetooth A2dp Source, which displays a yellow icon (exclamation point).

Workaround: And now it comes. Although Microsoft is aware that since mid-July sfc / scannow no longer works normally, but also here only a workaround must be applied, it is recommended to just run sfc / scannow on the command prompt and reboot the computer.

Will certainly give some who wonder that sfc / scannow can not do anything itself. The problem itself will be fixed in an upcoming Windows Defender antivirus antimalware software update.

SOURCE: SUPPORT.MICROSOFT

 

That bug which destroyed v1803 BT audio has come back again in v1903. The return of the Sith.

 

Damn lovely. Everything they touch will be destroyed!

Windows 10 1903 Has a Nasty Audio Stutter Bug Microsoft Hasn't Managed to Fix Techpowerup.com | Aug, 26, 2019
Windows 10 May 2019 Update (version 1903) is the pinnacle of neglect and contempt Microsoft has shown towards the all-important audio subsystem of the modern PC. With it, Redmond has one-upped its last big move against audio, by killing the DirectSound hardware pipeline and mongrelizing PC audio under Intel's lousy and fundamentally anti-competitive Azalia specification that solves common audio compatibility problems under a scorched-earth guiding principle - "kill any feature that could possibly lick our aftersales support budget, by dumping every aspect of audio onto a very restrictive host-signal processing (HSP) architecture, let people come up with their own soft DSPs, because CPUs can handle them." Windows 1903 proves how this approach wasn't a silver bullet against PC audio problems, and is fallible.

What's Wrong
Drawing inspiration from the other world-famous Washingtonian product, the Boeing 737 MAX airplane, Microsoft introduced Windows 10 1903 with a boatload of insufficiently-documented under-the-hood changes. Some of these changes affect Deferred Procedure Call (DPC) tick-rate, causing spikes in DPC latency, affecting the audio pipeline. Focusrite beautifully summarized DPC affecting audio:

------------------------------------------

Of course Micro$haft haven't the time make current OS version useable...

Win10 version 1909 (“19H2”) now has three current beta versions
Posted on August 27th, 2019 at 10:48 Askwoody.com

Microsoft’s putting the finishing touches on the next new version (“feature update”) for Win10 version 1903. Except it isn’t being distributed as a new version. It’s being distributed as a plain-vanilla monthly patch (“quality update”).

I tend to think of the next version of Win10 as Win10 1903 Service Pack 1. But you’ll probably end up calling it Win10 version 1909.

Here’s where you need a decoder ring.

The Windows Release Preview ring has been used, historically, for all sorts of things. Recently, it’s been used to test updates to Win10 version 1903 prior to officially rolling them out. (It’s also been photobombed by an odd update, build 18947, which was quickly pulled.) On August 21, Microsoft released a new test version of Win10 1903, build 18362.325, into the Release Preview ring. Presumably, 18362.325 includes fixes for the VB/VBA/VBScript bugs introduced on Patch Tuesday in 18362.295.

Starting yesterday, a subset of those in the Release Preview ring (about 10%, according to Dona Sarkar), were given the keys to the executive washroom. If you’re in the Release Preview ring and you’re one of the chosen few, you’ll see a link to update to “Windows 10, version 1909.”

Click on that link and you’ll be able to test Win10 build 18363.327. That’s the first Win10 1909 update allowed out of the Redmond barn.

Note the monkey business with the build numbers — Win10 version 1903 is build 18362.blahblahblah. Win10 version 1909 (nee “19H2”) is build 18363.mumblemumble.

Sarkar says “to designate 19H2 as a feature update, we are revising the baseline build number by one full build” in the Windows Obfuscation Numbering Scheme. But note that:

-------------------------------------------------------

Windows 10: We're now gearing up for 1909 with new throttled release, says Microsoft
Microsoft starts testing its controlled release in the most stable of its Windows preview rings.

 

Most likely 1903 and 1909 will be merged to one thereby limiting OS upgrades to one per year.

 

They was too scared to do major changes for coming 1909. This because a lot people/companies will migrate (forced) over from Win 7 now as its near EOL. Don’t have big hopes that things will be so much better.

 

And that's the way it should be. Figure out and deploy the desired feature set for 8 months then bug test the hell out of it for 4 months. Rinse and repeat the following year.

The problem Microsoft got into is they think Windows 10 can follow the same deployment schedule as Linux. It's not going to happen because Linux is Open Source and Windows 10 is not. And even Linux Distro's have gone from a 6 month schedule to 7-9 months between release updates.