Microsoft continues its bifurcating betas with two new versions of Win10 19H2 (aka 1909)

Topic

New Reply

I just love how they’re doing this. A few minutes ago, Microsoft (once again) released not one, but two “latest” beta versions of Win10 version 1909.
[See the full post at: Microsoft continues its bifurcating betas with two new versions of Win10 19H2 (aka 1909)]

1 user thanked author for this post.

GreatAndPowerfulTech

Reply | Quote

Replies

All of Microsoft’s BETA versions of Windows 10 are actually ALPHA versions and the “Release” versions are, and always will be, BETA with the end users doing the QA/QC the hard way for everyone and everything but MS’s balance sheet.

Somewhere at Microsoft’s Redmond based cubicle farm: What’s a QA/QC? Is that some sort of new Queso Combo at Chipotle?

 

1 user thanked author for this post.

WildBill

Reply | Quote

Not a service pack, it’s a cumulative update.

Reply | Quote

What’s even more fun is that Microsoft silently made privacy settings “global” in Windows 10 1903 affecting “Win32” software as well, not just UWP “apps”. Of course, other than with UWP “apps” there is no way to enable or disable privacy settings for select “Win32” programs.

Reply | Quote

Are not the Win32 ones governed by CEIP?

Reply | Quote

It’s not about CEIP, it’s about privacy settings for store apps (a.k.a. UWP apps). Those settings can be found in the ‘Settings’ tool under Privacy / App permissions; and these settings no longer apply to store apps only, but to all software running on the computer. While you can enable/disable settings for select store apps, you can’t for ‘Win32’ software. For the latter, it’s an all-or-nothing switch and you can’t apply without breaking ‘Win32’ software (desktop, services, name it). So if anything ‘Win32’ stops working after installing Windows 10 1903, check the privacy settings.

2 users thanked author for this post.

WildBill, abbodi86

Reply | Quote

Whoops… maybe I will convert to a Linux distro before Win8.1 ends in Jan. 2023. I was hoping Win10 1909 AKA 19H2 AKA “1903 Service Pack” would be uneventful like everyone else. Mainly bug fixes rather than new “features”… I’m interested in Clipboard improvements, the Your Phone app, an improved Photos app, Night Light mode, even emojis in 1903. But 19H2 Insider Preview Builds 18362.10012 & 18362.10013 add creating Calendar events “straight from the flyout on the Taskbar”? (whatever a flyout is)… & you can maneuver Notifications?! Then Builds 18362.10014 & 18362.10015 are “updating the search box in File Explorer to now be powered by Windows Search”?!? The search box in Win8.1 Explorer is fine as is… I don’t need Windows Search to look over my shoulder!

I’m afraid more “features” to add means more things that break month to month… & more bugs popping up here & there instead of a “boring but stable Service Pack”. Glad I’m still on Windows 8.1 instead of being a Windows 10 Insider in the Slow ring. Also glad that I’m waiting for the OK from Woody & MVPs to upgrade to 19H2 in late 2019 or early 2020!

 

Bought a refurbished Windows 10 64-bit, currently updated to 22H2. Have broke the AC adapter cord going to the 8.1 machine, but before that, coaxed it into charging. Need to buy new adapter if wish to continue using it.
Wild Bill Rides Again...

Reply | Quote

Oh no, just no no no! with that updating the search box in File Explorer to now be powered by Windows Search! That smacks of full OS cloud integration and a MS cloud umbilical cord attached to your private system file searching history. Talk about Big Brother MS and any sort of system that can never be anything but air-gapped to maintain privacy, and that’s with the wifi/bluetooth card/cards removed from the system.

It’s getting harder and harder to think of anyone’s PCs/Laptops under Windows 10 as anything but always connected nodes on Redmond’s Cloud. Your PCs/Laptops will be assimilated as just one of the billions of nodes on that Redmond Cloud Collective.

I can’t keep from getting that Cyberdyne Systems feeling every time that a new Windows 10 build comes out and it’s all apparently coming to pass beginning in 2020 and continuing until 2023 when after that there will be no way to remain dependent on the OS product from the folks from Redmond and still retain a single shred of privacy.

It’s time for everyone to bone up on their TuxBird OS knowledge and give the appropriate Torvalds Salute in the general direction of Redmond.

Reply | Quote

woody

this came out on August 26:

https://blogs.windows.com/windowsexperience/2019/08/26/testing-the-throttled-delivery-approach-for-19h2/

new 19H2 build 18363.327, which now displays it as version 1909 instead of 1903

reaction from Neowin:
https://www.neowin.net/news/microsoft-is-putting-windows-10-19h2-on-build-18363-pushes-it-to-release-preview

and from Born’s blog:
https://borncity.com/win/2019/08/27/windows-10-insider-preview-build-18363-327-19h2/

1 user thanked author for this post.

woody

Reply | Quote

[woody]

I’m still trying to make sense of the hodge-podge of conflicting build numbers.

We’ve always needed a scorecard to keep track of Win10 builds. Now we need a decoder ring, too.

I think I figured it out.

• This reply was modified 5 years, 9 months ago by woody.

1 user thanked author for this post.

wavy

Reply | Quote