New
#1
Can you setup DoH in this version? I am using Dev at the moment, but I need to reinstall.
UPDATE 5/18: How to get the Windows 10 May 2021 Update version 21H1
Windows 10, version 21H1, is now available for commercial customers to begin feature exploration and validation prior to being released for general availability.
As previously announced, version 21H1 will be delivered to devices currently running Windows 10, version 2004 or version 20H2 using an enablement package. This is the same technology we used to update devices from Windows 10, version 2004 to version 20H2. Do you want to see how quickly devices update from version 2004 or 20H2 to version 21H1, and how little downtime is involved? Now you can!
You can access Windows 10, version 21H1 through all standard channels, including Windows Update, Windows Server Update Services (WSUS), and Azure Marketplace, or you can download an ISO file. If you manage updates directly from Windows Update and have devices enrolled in the Release Preview Channel for validation purposes, you can go to the Windows Update Settings page of the device to download and install Windows 10, version 21H1 and experience the remarkably fast update that comes with updating via enablement package.
Note: We consider a device a commercial device if it is not running the Home edition of Windows 10, is being managed by an IT administrator (whether via Microsoft Endpoint Manager or a third-party MDM tool), or if the device has a volume license key, a CommercialID, or is joined to a domain.
As with Windows 10, versions 2004 and 20H2, version 21H1 also shares a common core operating system with an identical set of system files. New features are included in monthly quality updates for version 2004 in an inactive and dormant state. These new 21H1 features remain dormant until they are turned on through the “enablement package,” a small, quick-to-install “master switch” that activates the Windows 10, version 21H1 features.
If you are managing updates with WSUS, you have the option of taking a full feature update to 21H1 or testing out the enablement package path if your devices are currently running 2004 or 20H2. As with any other validation done on pre-release updates published to WSUS, you will need to first ensure that you have synced the “Windows Insider Preview” category. Once you have synced this category, you should see the following updates show up in your console as shown below:
To test out this experience on a virtual machine, check out the Windows 10 Preview on Azure Marketplace or, if you would prefer, you can download the Windows 10, version 20H2 ISO.
We not only want to ensure that you have access to the upcoming Windows 10 feature update payload via any channel you may use today, we also want to enable you to validate with confidence. Therefore, customers in the Windows Insider Program for Business can once again receive Microsoft Support for the Windows 10, version 21H1 build available through WSUS, ISO download, Azure Marketplace, and directly from Windows Update in the Release Preview Channels.
If you run into a severe issue that prevents you or other users in your organization from using a device, or compromises security or personal data, use the online form to request assistance directly from Microsoft Support—at no cost to you.
For more information, check out these useful links for exploring and validating pre-release Windows feature updates:
- Learn how to manage pre-release using the Windows Insider Program
- Manage Insider Preview builds across your organization
- Get support for 21H1 in Release Preview
- The Windows Insider Program for Business
- Publishing pre-release Windows 10 feature updates to WSUS
Source: https://techcommunity.microsoft.com/...n/ba-p/2220577
Tweet
— Twitter API (@user) View on Twitter
Apparently not. According to the How-To Geek... "...all of the features that looked like they were coming in Windows 10’s 21H1 update have been delayed" and are now pencilled in for 21H2.
How-To Geek | What’s New in Windows 10’s 21H1 Update, Coming Spring 2021
that's because of the current pandemic situation.
MS decided to make 21H1 for normal Win10 systems as build 19043 (a minor feature update) and 21H2 a big feature update with a major build number change
---
I'm beta testing 21H1 build 19043.899 (though did an in-place upgrade install of 21H1 build 19043.867 from 20H2 with the 21H1 preview ISO, then installed KB5000842 from the cab file using dism.exe) on one of my PCs - so far so good. another good thing about 21H1 is Adobe Flash is no longer included (the KB4580325 & KB4577586 updates would refuse to install on these machines as these updates are "not applicable" to 21H1 - yes)
From the first post: "As with Windows 10, versions 2004 and 20H2, version 21H1 also shares a common core operating system with an identical set of system files."
So I'm guessing my little HP spectre x2 with conexant audio drivers, still stuck on 1909 (2004 is blocked in WU), won't get 21H1 either? Was hoping since neither Synaptics/MS/HP appear to be doing anything about this for my particular machine that I may just be able to jump ship from 1909 straight to 21H1. I know some newer HP business machines received an updated conexant audio driver, but not so for my 2016 consumer model. HP have not provided any driver updates or a new BIOS for this machine since Dec 2019. I keep checking via device manager but repeatedly told I have the best drivers for my system. *sigh*
I'll be angry to retire this machine, as although a little on the slow side (unsurprisingly - it's running an m7-6Y75 chip and has only 8gb ram), it's an awesome wee machine and I have several use cases for it still. It also has a 1080p webcam - the only laptop we have that I'm not embarrassed to use the webcam on.
Last edited by catspyjamas; 09 Apr 2021 at 01:08.
Yep, Conexant is really not that great. I remember a rollout on Win 10 2 years ago all HP machines with the Conexant audio lost sound.
Now I have the latest and greatest 4080 sound chip on my Z590 and Realtek is sounding more and more like Conexant. USB now instead of processor managed. It's just apples and oranges. The only problem is that Realtek is dead silent on the specs of the chip and most board companies offer little to no information. The chip has a driver issue which slows boot on driver load. I flagged the problem with Asus but more often than none you almost need to talk engineer for the support to take you seriously, otherwise they'll give you replies like re install the driver. Do you have the right driver? There's only one driver so far! Go figure![]()
I haven't used on-board audio since early 2010s, but I dislike the idea that their drivers can still become a problem. My current (not very current) motherboard has Realtek ALC 1150 that stopped getting standard drivers in 2016. The latest (standard) driver is installed since it's easier to just allow Windows to install drivers for obsolete on-board hardware than trying to prevent it for specific devices, especially if your Windows build doesn't support GPE. Perhaps if it was disabled in BIOS it wouldn't be detectable by Windows, without that interfering with Windows' own software HD audio services.
That business with Conexant is infuriating because almost any sound device will work with native Windows drivers, just without most extra features. With laptops it's even simpler, any driver that lets them make their system alert tooting sounds is good enough, for me anyway. There would much less bloat too, believe me.