Windows 10: Registry value for ReleaseID not updated after Feature Update 21H1 installation

LVadai.PaH · May 26, 2021

Updated my device to FU 21H1.Registry values does not seem to be updated correctlyComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersionReleaseID 2009DisplayVersion 21H1BuildLab 19041.vb_release.191206-1406CurrentBuild 19043Our whole reporting system relies on ReleaseID variable that wasn't updatedanyone can confirm if this intended or a bug?

:)

evadernz · May 26, 2021

iCloud for Windows will not work with Windows 10 (October 2018 update)

Try this solution that worked in my case (Windows 10 Pro 64-bit v1809)

Open Registry Editor: Win+R | regedit

Navigate to the registry path: HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows NT\CurrentVersion

Temporarily modify these 3 registry keys:

CurrentBuild set value to 17134 (instead of 17763)

CurrentBuildNumber set value to 17134 (instead of 17763)

ReleaseId set value to 1803 (instead of 1809)

Install iCloud: iCloudSetup.exe | when finished, do not restart yet

Restore initial values of the 3 keys (step 3)

Restart PC and complete setup of iCloud

For Windows 10 in 32-bit version, the path is: HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion

W1zzard · May 26, 2021

GPU-Z update loop (Windows 10 64-bit)

Hmm .. need better steps to reproduce.

The installer adds a key with the install path to the registry, which is checked against and then that "Update GPU-Z" box is displayed.

Brink · May 26, 2021

Introducing the next feature update to Windows 10 version 21H1

Today, we are introducing the next feature update to Windows 10, version 21H1. As people continue to rely on Windows more than ever to work, learn and have fun, we understand the importance of providing the best possible update experience to help people and organizations stay protected and productive. It is a responsibility we do not take lightly and why for the first time an H1 (first half of the calendar year) feature update release will be delivered in an optimized way using servicing technology, while continuing our semi-annual feature update cadence. In today’s blog I will cover details on how we plan to service the release, its scope, and next steps.

Fast and focused

Based on feedback and learnings during the past year of extensive remote work, learning and play, version 21H1 will be delivered with servicing technology (like that used for the monthly update process and how 20H2 was delivered). Windows 10, version 21H1 will have a scoped set of features improving security, remote access and quality. The features we are releasing in this update are focused on the core experiences that customers have told us they’re relying on most right now. So, we optimized this release to support our customers’ most pressing needs.

New features include multicamera support for Windows Hello and security related performance improvements.

Windows Hello multicamera support to allow users to choose an external camera priority when using high end displays with integrated cameras.

Windows Defender Application Guard performance improvements including optimizing document opening scenario times.

Windows Management Instrumentation (WMI) Group Policy Service (GPSVC) updating performance improvement to support remote work scenarios.

Customers running either Windows 10, version 2004 or version 20H2 who choose to update to the new release will have a fast installation experience because the update will install like a monthly update. For consumer or commercial users coming from versions of Windows 10 earlier than the May 2020 Update (version 2004), the process of updating to the new release will be the same as it has been and will work in a similar manner to previous Windows 10 feature updates, using the same tools and processes. As this Windows 10 release is targeted for the first half of 2021, all Windows 10 editions of version 21H1 will receive 18 months of servicing.

Next steps

Our multilayered approach to the development and launch of feature updates continues and includes fully leveraging the Windows Insider Program to obtain user feedback and data insights on quality. We will begin releasing 21H1 builds to Windows Insiders in the Beta channel today to those Insiders who seek to opt in, and new features will be offered in future Windows Insider Preview Builds as they are ready. Broad availability of Windows 10, version 21H1 will begin later in the first half of this calendar year, and we will provide more information on the release and how to get it as we get closer to the launch of this next feature update. We look forward to hearing your feedback.
Click to expand...

Source: Introducing the next feature update to Windows 10, version 21H1 | Windows Experience Blog

See also: KB5000736 Windows 10 Insider Beta Channel Build 19043.844 (21H1)

Tweet

— Twitter API (@user) View on Twitter
Click to expand...

Windows 10: Registry value for ReleaseID not updated after Feature Update 21H1 installation

Registry value for ReleaseID not updated after Feature Update 21H1 installation

Registry value for ReleaseID not updated after Feature Update 21H1 installation

Registry value for ReleaseID not updated after Feature Update 21H1 installation

Registry value for ReleaseID not updated after Feature Update 21H1 installation - Similar Threads - Registry value ReleaseID

Registry value is not getting updated for the applied patch

Registry value is not getting updated for the applied patch

Windows 10 Feature Update version 21H1 is not updating

Windows 10 Feature Update version 21H1 is not updating

Windows 10 Feature Update version 21H1 is not updating

Feature update 21H1 went missing

An Update AFTER 21H1

Windows Insider Program feature update not updating to 21H1

Groove Music not working after 1809 Update, invalid value for registry.