Insider KB5017321 Windows 11 Insider Release Preview Build 22621.521 22H2 - Sept. 13

done and dusted - was very quick.

Very quick update, no problems at all

Very quick update. Wow, I actually was able to download and install using WINDOWS UPDATE. Maybe I'm back to regular, insider updates and builds. First time in several (3 or 4) builds that Windows Update actually allowed me the pleasure.

Took 5 min.

Still no fixes for these 2 problems.

Windows Insider

Windows Insider

I did an upgrade and still getting 1108, 6155, 360 errors. I can't seem to find what the issue is. I'll have to take a few hours and do a step by step. What a pain

Updated, all seems OK, no problems with SFC or DISM.

Hi all, this will only interest those with this issue.

Since the beginning of testing of 22H2, all versions (in my case and others that filed a similar response on insider) have generated Windows hello for business messages (event 360) accompanied by LSA errors (event 6155), Wininit (event 15) errors and multiple Event viewer errors (event 1108).

All of this is related to credential guard. I tried to disable credential guard, LSA service, Windows hello for business and so on to no avail.

This seems to be related to a prior install of Windows business (in my case on this system) or a professional account activation. I don't know how to remove all traces of previous accounts. I know that Win keys are not saved to TPM chip but rather bios chip which in any case can be changed with another license (tried that also, no go) (BTW, since a few bios versions ago you can't disable PTT on Asus Z690 boards)

I also tried to disable secure boot, deleted keys, re installed a clean version of Windows (PRO not Enterprise) and same issue appears. If I install a new version of Windows Pro on a new system, this error does not appear (which is why the problem is not widespread).

I tried to clear TPM (tpm.msc) to no avail either.

This just goes to show how deeply encrusted personal info can be tagged and hard to remove when these issues arise.
I'm thinking of dipping the board in bleach solution to sterilize it

Until then, I will have to sit on 22H1 which runs pretty good. I'm really keen on getting tabs in Explorer though.

Windows 11 22H2 apparently already shipping with build 22621.521 (KB5017321) ​

Hi folks

Getting confused here between builds 22621 and 22622 (22H2) Mine is 22622 (22H2).

my build (on a VM) is :


No issues on clean install - also no probs with the sometimes reported issue "Windows needs a new app to open .... when trying to access WD security dashboard.

No prob so far so "Alles in Ordnung" !!!. Fast install too.

Cheers
jimbo

Wolfzz said:

Windows 11 22H2 apparently already shipping with build 22621.521 (KB5017321)​

Windows 11 22H2 apparently already shipping with build 22621.521 (KB5017321)

There appears to be an early shipping of Windows 11 22H2. A user, who recently ordered a new laptop, says that their new system has Windows 11 22H2, build 22621.521 (KB5017321) in it.

www.neowin.net

Click to expand...

More likely it checked for updates on first startup and the 521 update installed then

I cleanly installed this into a new VM, and I built the .ISO (via UUPDump) so that it only had the Windows 11 Pro (no Home) on it, and did not build with the extra editions.

I've been cleanly installing new VMs across the board, for Windows 10 and Windows 11, as my A+ cert if coming up on renewal time, but that is a side story - the main thing is that this particular build, thus far, would not allow me to make a local account only - I was forced to sign in with an MS account, and then after installation completed could I revert it to a local account only.

Every other build installed thus far (Win 10 stable, 10 IP (19044.2xxx), Windows 11 (built from the MCT), and Windows 11IP 21H2 (22000.1041) all gave me the option to do local only when I clicked on sign in options. This build only had "connect or security", not local sign in option.

I though this was supposed to be limited to Home editions only?

johnlgalt said:

I cleanly installed this into a new VM, and I built the .ISO (via UUPDump) so that it only had the Windows 11 Pro (no Home) on it, and did not build with the extra editions.

I've been cleanly installing new VMs across the board, for Windows 10 and Windows 11, as my A+ cert if coming up on renewal time, but that is a side story - the main thing is that this particular build, thus far, would not allow me to make a local account only - I was forced to sign in with an MS account, and then after installation completed could I revert it to a local account only.

Every other build installed thus far (Win 10 stable, 10 IP (19044.2xxx), Windows 11 (built from the MCT), and Windows 11IP 21H2 (22000.1041) all gave me the option to do local only when I clicked on sign in options. This build only had "connect or security", not local sign in option.

I though this was supposed to be limited to Home editions only?

Click to expand...

MA needed on pro version now too but if you use rufus to make USB you can remove MA requirement on rufus and minimum requirements too

Dave44 said:

MA needed on pro version now too but if you use rufus to make USB you can remove MA requirement on rufus and minimum requirements too

Click to expand...

I have the minimum requirements perfectly met, not worried about that. And it was just as easy to sign in and then convert to local.

My point was that I thought it was Home specific, and yet it happened to me installing Windows 11 Pro.

johnlgalt said:

I cleanly installed this into a new VM, and I built the .ISO (via UUPDump) so that it only had the Windows 11 Pro (no Home) on it, and did not build with the extra editions.

I've been cleanly installing new VMs across the board, for Windows 10 and Windows 11, as my A+ cert if coming up on renewal time, but that is a side story - the main thing is that this particular build, thus far, would not allow me to make a local account only - I was forced to sign in with an MS account, and then after installation completed could I revert it to a local account only.

Every other build installed thus far (Win 10 stable, 10 IP (19044.2xxx), Windows 11 (built from the MCT), and Windows 11IP 21H2 (22000.1041) all gave me the option to do local only when I clicked on sign in options. This build only had "connect or security", not local sign in option.

I though this was supposed to be limited to Home editions only?

Click to expand...

It is not limited just to Home edition, MS started requiring MSA on any edition.
There are still ways of bypassing that requirement, but it needs some little tricks that you can find on the web.


Or you can use oobe\bypassnro to install without internet connection:

jimbo45 said:

Hi folks

Getting confused here between builds 22621 and 22622 (22H2) Mine is 22622 (22H2).


No issues on clean install - also no probs with the sometimes reported issue "Windows needs a new app to open .... when trying to access WD security dashboard.

No prob so far so "Alles in Ordnung" !!!. Fast install too.

Cheers
jimbo

Click to expand...

22622.598 is on the Beta channel and has the experimental features enabled.
22621.521 is on the Release Preview channel and the features disabled by default.

fg2001gf11F said:

22622.598 is on the Beta channel and has the experimental features enabled.
22621.521 is on the Release Preview channel and the features disabled by default.

Click to expand...

This is rather inaccurate - there are two versions of Beta 22622.598 and 22621.598 and an RP version 22621.521.

The 22622 version contains experimental features that may or may not get into final RTM. The same is potentially true to a lesser degree for 22621/598 but very unlikely. MS categorically ste features in Beta may not make it into RTM.

Features in 22621.521 RP will make it into RTM unless MS need to pull a feature e.g. if problems are identified that would delay release of RTM in order to fix the issues.

You can could at one time revert from 22622.290 to 22621.290 by uninstalling the enablement package update but I am not sure if this works for 22622.598 - anybody know?

So in pecking order

22621.521 RP - all features will make it to RTM unless serious issues identified

22621.598 Beta - most if not all features should make it to RTM but not absolutely guaranteed (pretty much same as RP but slightly less certain)

2262.598 - whilst most features should make it to RTM, no guarantees that any of new experimental features will make it to RTM.

For clarity DEV builds are only ever test beds, and any features MS decide to add to next but one RTM (beyond next RTM release) will cascade into Beta/RP versions in due course.