21H1 is getting close

Topic

New Reply

Windowslatest reports that 21H1 is getting close to release. Remember these days it’s a bit nicer behaved and will offer itself up and not be forced.
[See the full post at: 21H1 is getting close]

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Replies

21H1 available not only to “seekers” but also available thru Update Assistant and MCT
21H1 ISO downloads are also available

ISOs & ESDs are build 19043.928

those using windows update may get the 19043.985 build instead of 19043.928

Reply | Quote

and "here it is"..... they gave me    19043.985

OK, I’ve got sound, I’ve got picture, even a printer!
Device manager says nothing is missing,  who could ask for more

This is a HP 6300 i3-3240 @3.4g

Reply | Quote

I just used TRV = 21H1 to upgrade my 20H2. Build is 19043.985 The only thing I changed was the TRV designation.
It was a 10 minute operation.
I had removed the tile Apps and ChrEdge from the VM I was testing and apparently the install respected the removal.
Have not had time to check it out to see if any of the settings were changed – more later on that.

See #2365600 for more information.

3 users thanked author for this post.

Coldheart9020, Microfix, Alex5723

Reply | Quote

yup, painless and quick. See this Topic so we can collectively gather a checklist

Windows - commercial by definition and now function...

Reply | Quote

I am not a seeker and did not press check for updates; but I was offered 21H1 on my 7th Gen. Intel Core i7 HP Omen laptop that was already on 19042.985 tonight and accepted the download and install (Windows 10 Home). As far as I can tell, the only thing that changed was 19042 became 19043. Can’t identify any other changes. Upgrade took less time than an ordinary monthly cumulative update and downloaded only about eight megabytes (about the same as a virus definition update).

 

Reply | Quote

Did you open up the Windows update interface? Microsoft considers that “seeking”

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

Although anonymous says he/she wasn’t performing the normal actions of a seeker by clicking the “Check for Updates” button, perhaps when WU went to check on its own, like it does every 22 hours or so, it was then offered by the WU servers anyway.

Reply | Quote

Replying to both Susan and Bob, every time I turn on and boot up this laptop, which is only three times a week (I have rapid boot and hibernation disabled) Windows Update checks for updates on its own and downloads and updates Windows Security (defender), while also displaying or listing all other updates that are available. If I open Windows Update immediately after boot up it will be already in the process of searching for updates before I even get there. If I don’t open Windows Update but stay on the desktop, I’ll get a pop up notification from the task bar if there are updates available that weren’t already automatically downloaded and installed like the virus definitions for defender are. I never click on Check for Updates for any reason. It will tell me if anything is available without doing that.

Reply | Quote

I “called” today’s availability nearly three weeks ago, back on April 28, in a post here on AskWoody.

A big thanks to @sheldon for the reminder here to hide the Feature Update with wumgr, wushowhide or wumt unless you plan to install it at this time!

Reply | Quote

Using WUmgr : Checked for updates, downloaded and installed KB5000736 21H1.
The process took 2 minutes.
Winver 19043.985

Reply | Quote

p.s Before the upgrade I has 8GB of Windows Update data (disk cleanup). After the upgrade 110MB.

Before the upgrade I ran dism /Online /Cleanup-Image /AnalyzeComponentStore
and dism /online /Cleanup-Image /StartComponentCleanup in order to reduce WinSxS size.
Gained 3GB.

Reply | Quote

Windows 10 Home 20H2 (build 19042.928) here: just spotted 21H1 waiting in the wings by way of a WuMgr scan and promptly hidden it for the time being.

Reply | Quote

Well i think my works laptop has installed it. After a few reboots and an apparent failed install its now showing “21H1 19043.985”

However the install date hasnt been updated and still showing as the date i installed the last feature update last year. Windows update history has nothing to suggests its installed either, but its not being offered again

So guess i have it?

Reply | Quote

Windows Update history will only show Feature Updates that were done via Windows Update. If the Feature Update is done through a different method (e.g. MCT, TRV, ISO) then it won’t show in Windows Update history.

I suppose the method you used this time was not the same as you used last year.

Reply | Quote

On an older HP laptop at 19042.985, I used Windows Update to seek 21H1 and it was not offered. Set TRV in Group Policy to 21H1 and scanned again. This time the download began immediately and within two minutes I was rebooting to the latest Feature Update. Windows Update history showed the update to 21H1. Therefore, I suppose only MCT and ISO are the methods that won’t show up in Windows Update history.

Reply | Quote

For those on the business end: The media creation tool has been updated as well, you can grab your ISOs there, and on WSUS I see both the full packages as well as the small activation packages…

Reply | Quote

Last night I used the MediaCreationTool21H1.exe to attempt to update an older laptop running 20H2 (19042.xxx, xxx<985). This morning the laptop was at 19042.985, not 19043.985, so it was still on 20H2.

This same media creation tool did download the correct, current 21H1 ISO file on another system.

I noticed that MCT21H1.exe is identical in size (19,463,448 bytes) and internal file version (10.0.19041.572) to MCT20H2.exe that I downloaded on 16-Mar-2021.

The files are identical (fc /b) which doesn’t make much sense unless the MCT now only downloads the current ISO, not older ones as had been the case with all of the older MCT’s.

Reply | Quote

The MCT is simply a tool to download the current version and initiate the process of creating an ISO and/or converting that ISO to installation media either on the PC or on external media (USB drive or DVD).
What is available on the MS download site is the current version. A week ago the ISO created was 20H2. As of May 18, 2021, the available ISO is 21H1.
The MCT is not version selective in spite of the fact that the version number may be in the file name. It only downloads whatever current version is available on the MS download site. Once a new version is released, that is what you get.

1 user thanked author for this post.

Coldheart9020

Reply | Quote

For the curious, Windows Central has a fairly detailed run-down of features added, fixed and improvements in 21H1.

Windows - commercial by definition and now function...

Reply | Quote

News and Interest is missing in features added. Maybe because it is disabled by default and may be enabled automatically with the next monthly update, or some server side switch.

Reply | Quote

The News and Features/News and Interests feature might not be mentioned in the Windows Central article because it might have been incorporated into 21H1 after the article was written.

If you look carefully, under the sub-heading that begins “Here’s the ultimate changelog for…”, you’ll see the author’s name (Zac Bowden) followed by the date of the article (March 18th, 2021) in purple.

Reply | Quote

For everyone’s info, Susan says the News and Interests feature is in the May update for all currently supported versions of Windows 10 in a post here. That explains why it wasn’t mentioned in the 21H1 write-ups in Windows Central and Neowin.

That also makes me somewhat incorrect in my anonymous post above, where I thought the feature was only for 21H1. My sincerest apologies to all. 

1 user thanked author for this post.

Alex5723

Reply | Quote

Mind you it’s a feature that they are “dribbling” out.  I’ve seen it on two unmanaged computers (aka those that are consumers, not in a domain, WU left to do it’s thing) and have not seen it at all on computers where they are either on a domain or that group policy has been used to set update settings.

Susan Bradley Patch Lady/Prudent patcher

Reply | Quote

I went a seeking on my test machine and it provided the update. However, I got some funny results:

Funny it still shows 2009! So I did a little digging using PowerShell manually.

    Hive: HKLMSOFTWAREMicrosoftWindows NT


Name            Property                                            
----            --------                                            
CurrentVersion  SystemRoot                : C:WINDOWS          
                BaseBuildRevisionNumber   : 1  
                BuildBranch               : vb_release         
                BuildLab                  :    
                           19041.vb_release.191206-1406   
                BuildLabEx                :    
                19041.1.amd64fre.vb_release.191206-1406         
                CompositionEditionID      : Enterprise       
                CurrentBuild              : 19043                 
                CurrentBuildNumber        : 19043               
                CurrentMajorVersionNumber : 10 
                CurrentMinorVersionNumber : 0  
                CurrentType               : Multiprocessor Free 
                CurrentVersion            : 6.3
                EditionID                 : Professional        
                InstallationType          : Client                
                ProductName               : Windows 10 Pro      
    =====>      ReleaseId: 2009     <=====             
                SoftwareType              : System                
                UBR                       : 985
                PathName                  : C:Windows          
                DisplayVersion            : 21H1                  
                RegisteredOwner           : RetiredGeek

Looks like someone at MS missed a step?
HTH

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

Reply | Quote

Ok, so I’m on 20H2 build 19042.928 64 bit Pro and based upon your post above I went digging into my registry with regedit.

I found nearly the identical data that you posted above, including that the ReleaseId string is 2009! The only differences aside from the RegisteredOwner name is the CurrentBuild and CurrentBuild number are both 19042 in my case due to being on 20H2.

Reply | Quote

I have had very little problems with Windows 10 Update until this time. I had paused updates for 7 days then let it go. After being notified of a restart, it resulted in a bsod. After several of these, I sensed it was with the boot process. Paragon confirmed that Update had changed the system reserved to C drive & made it active. The main Windows partition was inactive & put to D drive. I was able to change the active/inactive around but never could get the drive letters to change. There didn’t seem to be a way to try to edit the boot/bcd file. I didn’t realize how difficult it is to make a file on usb greater than 4 G bootable. Easesus wouldn’t display any of the external usb drives, so I could not restore with an image. Finally used creator media to fresh install 21H1. Still doing all right. Don’t know if Fred Langa would have any other suggestions. Now reloading my apps. Probably needed it anyway.

Reply | Quote

Installed on a couple “test” machines and so far so good. If only every update was as quick and as smooth as this seems to be that would be a welcome change.

Noticing some coloration changes, especially on Start Menu.

Nothing else too big at this point.

Reply | Quote

According to CU Preview KB5003214 (19041.1023), version 21H2 will probably be another minor upgrade = 19044

Reply | Quote

Could you explain what “According to” means?

Reply | Quote

It contain:

1 user thanked author for this post.

b

Reply | Quote