Cumulative Update KB4515384 Windows 10 v1903 build 18362.356 Sept. 10 Win Update

this update might have bungled up more than I thought (or the issues on my end are all me); in here, this update might've bungled up all the system taskbar icons part of windows 10. can't use the wifi/internet icon or the sound control icon without it taking more than a minute for the menu to load, when it should be near-instant, maybe a 1-1.5 second delay.

no amount of clean booting, chkdsk'ing, dism'ing, sfc'ing, safe mode booting, nothing has worked to fix it, short of seeing about a repair install

RingTailCoon said:

Ah yes, so I myself have encountered bugs, like wiping updates from the list, unexplained deletion of cookies (resetting EVERTHING, entering passwords n stuff to revive it all), after pressing prnt-scrn it gives a black screen in photoshop (so you can't make normal prints).....

Really horrible things you did there, Microsoft! Fix it!

Oh, they'll fix it alright. It's just they'll break 5 more things when they do. I honestly don't think MS has the chops to manage a program of this complexity, with all the 'rings' and builds and A/B tests and crap flying around.

sgage said:

Oh, they'll fix it alright. It's just they'll break 5 more things when they do. I honestly don't think MS has the chops to manage a program of this complexity, with all the 'rings' and builds and A/B tests and crap flying around.

Agree. And to add to the list one can cite the terminology confusion, just to name a few: Windows Defender for Microsoft Defendder, the renaming of the Builds' names, sometimes the fusion of two flights in the same Insider build, like when they join Fast and Skippy or for v.1903 one has two 18362./18363. (the 10%). If I go for what is going on in the Insiders Programs, it is like getting into a maze with regard to this topic (terminology confusion).

My personal favourite:

To offer a clarification on these releases – 19H1 and 19H2 share the same servicing content. That means they share the same Cumulative Update package. For the small subset of Windows Insiders (the 10%) in Release Preview who were given the option to install 19H2, an enablement package is downloaded from Windows Update that turns on the 19H2 features. This *changes* the build number for the OS from 19H1 Build 18362 to 19H2 Build 18363. Because they use the same servicing content, the build revision number (the number that comes after the dot) will always match between 19H1 and 19H2. As we continue to test our servicing packages in the Release Preview ring, Insiders on 19H1 and 19H2 will get a single Cumulative Update with the same fixes.

Cumulative Update KB4517245 Windows 10 v1909 Build 18363.329 - Sept. 5

IronZorg89 said:

Agree. And to add to the list one can cite the terminology confusion, just to name a few: Windows Defender for Microsoft Defendder, the renaming of the Builds' names, sometimes the fusion of two flights in the same Insider build, like when they join Fast and Skippy or for v.1903 one has two 18362./18363. (the 10%). If I go for what is going on in the Insiders Programs, it is like getting into a maze with regard to this topic (terminology confusion).

My personal favourite:



Cumulative Update KB4517245 Windows 10 v1909 Build 18363.329 - Sept. 5

Seems to me they might consider a moratorium on 'feature updates', and send the whole Windows team off on a retreat somewhere to fundamentally rethink what they're trying to do here. I wonder how people on the Windows team feel about what's going on? I mean, they can't be real pleased. But I fear that Windows is not Microsoft's highest priority these days, and the Windows team is part of another division, and it's all a hot mess. They could start by having one big update a year, and do bugfixes and security patches on that every month. Then, have ONE Insider ring - an honest-to-god beta test kinda thing. Not this bullsh*t Release Preview/Slow/Fast/SkipAhead nonsense. Sheesh.

- - - Updated - - -

RingTailCoon said:

Another one of their MS-F*ckups and it's off to Linux Minty freshness and gonna sell my games to the nearest pawn shop.

NO MORE MISTER NICECOON!

I'm a Debian man, myself.

Seriously, I've been a MS customer for literally 40 years (!). Yes, I ran MBASIC on my Commodore PET/CBM's and then on my CP/M machines. Then came DOS, then Office, then Windows, and then... well, here we are. I'm retired now and don't need to run any MS software (though I understand that there are millions that do). I keep my hand in simply out of curiosity, and because Windows came pre-installed on my computer. Good luck to us all!

sgage said:

But I fear that Windows is not Microsoft's highest priority these days, and the Windows team is part of another division, and it's all a hot mess. They could start by having one big update a year, and do bugfixes and security patches on that every month. Then, have ONE Insider ring - an honest-to-god beta test kinda thing. Not this bullsh*t Release Preview/Slow/Fast/SkipAhead nonsense. Sheesh.

Their priority, rumor has it, is Azure. With regard to one Feature Update/year, I think they are heading this way unless things change again. One never knows with MS. TBH, one Beta or even two builds for testing are good enough and in a way that would avoid or at least mitigate all those known issues for each build released in the Insiders Program. Just my take!