Insider KB5029336 Windows 11 Insider Beta 22621.2191 and 22631.2191 - Aug. 10

JGToy · Aug 13, 2023

Almighty1 said:
I think the thing is Intel's Bluetooth drivers don't come with their own app so it relies on what Windows provides while some Bluetooth stacks like Widcomm and Toshiba comes with their own apps so you can think of what you have as an advantage as you didn't have the issue when everyone else did as your BT settings has it's own app and not relying on the one built into Windows but ofcourse should the one you have stop working for any reason and there are no updates to fix it, then you will run into a problem without a solution. Just curious, but does your Windows Settings app actually have a Bluetooth and devices section and if it does, what does it actually look like when you open it?

then you will run into a problem without a solution.

On that, probably you are 100% right but, until now it never happened.

Like this in settings:-

And sometimes with more devices... But only when I have connected them.

Almighty1 · Aug 13, 2023

JGToy said:
On that, probably you are 100% right but, until now it never happened.

Like this in settings:-

View attachment 67744

And sometimes with more devices... But only when I have connected them.

It's obvious it hasn't happened yet since it's still working.

Interesting so it seems like even Windows Settings is basically sending that part to the app. Did you actually have to install the bluetooth drivers and software or did Windows just automatically worked? Trying to phrase this correctly, is the Bluetooth acually part of the motherboard, a expansion card, a dongle you plug in by USB?

JGToy · Aug 13, 2023

Almighty1 said:
It's obvious it hasn't happened yet since it's still working.

Interesting so it seems like even Windows Settings is basically sending that part to the app. Did you actually have to install the bluetooth drivers and software or did Windows just automatically worked? Trying to phrase this correctly, is the Bluetooth acually part of the motherboard, a expansion card, a dongle you plug in by USB?

Nope! No driver installation at all, it just worked.
It have two: Expansion Card and I had to install drivers for the USB one (it is 5.1 + Wireless Network).

waltc · Aug 14, 2023

Almighty1 said:
That advice might be good or bad because on my Dell XPS 15 9570 for example, the latest Intel video driver is in the 27.x.x.x which means it's WDDM 2.7, while Windows 11 would prefer WDDM 3.0/3.1 drivers. So it depends. Also, the 27.x.x.x drivers has a well known issue where dwm.exe had a major resource leak that wasn't fixed until in the newer 30 or 31 series drivers as can be seen here:

BUG: dwm.exe uses memory leakage with Intel HD Graphics 630

Hi, dwm.exe (Desktop-Window Manager) uses high memory with Intel Intel HD Graphics 630. This problem has been reported before: https://answers.microsoft.com/en-us/windows/forum/all/desktop-windows-manager-dwm-memory-leakage-in/c2968fb0-ee26-4483-9f08-dfa19149cd24...

community.intel.com

I am a moderator for laptopvideo2go.com and in the old days like in the early 2000s, mods were needed to get video drivers to work but in the recent times, the drivers from the GPU manufacturers work fine without any issues. Besides, remember the Intel GPU is part of the CPU and not a actual separate GPU and I am sure Intel knows their CPU and what's in it better than Dell would.

Yes, while the group policy would work, there are sometimes where I want Windows to replace the drivers as a lot of times, I get newer than available drivers for both GPU, WiFi and Bluetooth than what's publicly available. So in my case, the only complaint I have is not for Windows to replace my Intel GPU drivers with a version # older than what's installed which in this case, it puts 27.x.x.x when I am already on drivers that are 31.x.x.x, the real problem is Windows should just check if the version they want to install has a number that is greater than what they want to install before they install it an don't install if the version is the same or equal to what's already on the system. So until I actually have problems, I'll just let Windows replace drivers as there is Windows Update history I can check regularly to see if anything has been replaced.

I think the best way to ensure that you are running the latest drivers is to manually download them and install them yourself, direct from the manufacturer. That way, there are no worries about having the wrong drivers installed by Win11 because of a bug/error. It's definitely my preference--a long-time habit. It's not as if doing so is "hard," or anything.

Bree · Aug 14, 2023

As @Ed Tittel and others are aware, there was a long-standing bug introduced in build .1972 that caused DISM to fail with error 6824 on cleaning up the component store. An offline cleanup was the only fix I could find.

Bree said:
For some of us build .1972 introduced a bug when attempting to clean up the component store.
dism /online /cleanup-image /startcomponentcleanup failed with:
Error: 6824
The operation cannot be performed because another transaction is depending on the fact that this property will not change.
This bug was not addressed by build .2050, or in .2048, as I demonstrated in post #22 here:

KB5028247 Windows 11 Insider Beta 22621.2048 and 22631.2048 - July 13

UPDATE 7/21: https://www.elevenforum.com/t/kb5028256-windows-11-insider-beta-22621-2050-and-22631-2050-july-21.16534/ Windows Blogs: Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.2048 22H2 and Build 22631.2048 23H3 (KB5028247) to the Beta Channel. Build...

www.elevenforum.com

There is a fix, you have to use DISM to perform an off line clean up, links to the details of how to do that are in that post above. As I said in that post, I deliberately left one of my VMs unfixed to see if MS would ever address this issue. Apparently they still haven't fixed this (or even acknowledged it, as far as I'm aware).

KB5028251 Windows 11 Insider Beta 22621.2115 and 22631.2115 - July 26 - post #7

I'm pleased to report that Microsoft have finally fixed this. Whether by accident or design we'll never know, Microsoft seem to have fixed it quietly without ever saying anything about it.

I confirmed that the VM I deliberately left unfixed still had the error before updating.....

...then updated it.

After updating to 22631.2191 the error 6824 no longer occurs, DISM now runs to completion successfully.

Almighty1 · Aug 14, 2023

waltc said:
I think the best way to ensure that you are running the latest drivers is to manually download them and install them yourself, direct from the manufacturer. That way, there are no worries about having the wrong drivers installed by Win11 because of a bug/error. It's definitely my preference--a long-time habit. It's not as if doing so is "hard," or anything.

Not always as you do know that for the Intel WiFi/Bluetooth, the manufacturers site being Intel in this case is atleast 1 month behind. Even for the GPU drivers, if you looked at the Intel GPU thread, you will see that there are drivers that are newer that come in via the Windows Update only tha are newer and still won't show up atleast a month later from the GPU manufacturers site which is Intel in this case and literally never on the actual notebook manufacturers site because their latest drivers are a few years old. So like I said, it depends on the scenario as you really want up to date drivers that meets Windows 11 specifications which is WDDM 3.0 or 3.1 which in the case with Intel GPU drivers are v30.x.x.x and v31.x.x.x drivers and not WDDM v2.7 drivers which are really meant for Windows 10 and not 11 which is why I said, it depends as things can always have good sides and bad sides. Similar to one shouldn't be in Beta Insiders either since it also forces you to use that version and it's not like you can uninstall it like you can with drivers should something go wrong, without talking about using backups but you will still lose any changes since the last backup, you will be stuck with it until the next version comes out. So it depends on the user really since if no one tests out the drivers before it's on the manufacturers website or otherwise and reports issues on forums, it will be released with the same issues and a bigger population will have the issues as the manufacturer can have the chance to fix it first. It's similar to the Calculator app in Windows 11 that was released a few days ago, try entering a . or , using the keyboard which does not work, if some people had those apps and tested it, the problem would likely effect less people so as with anything, there are always benefits and risks as like the saying goes, there is no guarantee or certainty in anything except death and taxes. But anyways, if the person(s) keeps complaining about bad drivers because of Windows replacing them automatically, then they should do what you mentioned as it would technically be their own fault if they didn't but if they don't mind like I do since there is always a risk in everything as while it may downgrade most of the time, there is also the benefit of seeing newer drivers ahead of the general public, then it should be up to them to do it as there was only one instance of one bad Intel GPU driver version from Windows Update that caused black screens randomly that was actually newer than released versions but also replaced newer versions later that caused problems until that was no longer than the default version Windows Update installs automatically and then at that point, one would have to uninstall until it says Microsoft Basic Driver, install the newest released version so Windows Update will update it and then install the version one wants again as Windows will only install each version it wants to once as as long as the system has installed that version, it will never replace it again.

JGToy · Aug 14, 2023

Bree said:
As @Ed Tittel and others are aware, there was a long-standing bug introduced in build .1972 that caused DISM to fail with error 6824 on cleaning up the component store. An offline cleanup was the only fix I could find.

KB5028251 Windows 11 Insider Beta 22621.2115 and 22631.2115 - July 26 - post #7

I'm pleased to report that Microsoft have finally fixed this. Whether by accident or design we'll never know, Microsoft seem to have fixed it quietly without ever saying anything about it.

I confirmed that the VM I deliberately left unfixed still had the error before updating.....

View attachment 67807

...then updated it.

View attachment 67810

After updating to 22631.2191 the error 6824 no longer occurs, DISM now runs to completion successfully.

View attachment 67809

Mine still crooked (I guess), it stop at 99.5% but still report everything as image below:-

Running the cleanup :-

Seems okay!

But running the check again :-

Everything still there. :what:

Bree · Aug 14, 2023

JGToy said:
Mine still crooked (I guess), it stop at 99.5% but still report everything.....

I occasionally see a 'bit-less-than-100%' run of DISM, analysis or clean up, even on the retail builds of Windows 10 or on Windows 11. It doen't seem to be anything to worry about. 'The operation completed succesfully' is the important bit.

But running the check again :- Everything still there.

Your 2nd run of analysis shows your clean up had reduced the actual size of the component store from 5.00GB to 4.30GB, so not everything is still there. :wink:

JGToy · Aug 15, 2023

Bree said:
I occasionally see a 'bit-less-than-100%' run of DISM, analysis or clean up, even on the retail builds of Windows 10 or on Windows 11. It doen't seem to be anything to worry about. 'The operation completed succesfully' is the important bit.

Your 2nd run of analysis shows your clean up had reduced the actual size of the component store from 5.00GB to 4.30GB, so not everything is still there.

Got it! I was looking at this:

That's why thought it didn't worked well because they are the same on both before and after.

Bree · Aug 15, 2023

JGToy said:
That's why thought it didn't worked well because they are the same on both before and after.

Yes, all of us who have had the Beta build for a long time and seen many updates seem to have those (un)reclaimable packages. They appear to just be 'ghosts' in the manifest and not actually present in the component store. They certainly don't stop DISM from cleaning up the store.

BTW, regarding the missing 0.5% in the successfully completed operation. This seems to be down to the way that cmd.exe handles the competing processes that are sending it the text to write to the window. The results process seems to start writing before the progress text has finished, preventing it from writing the final '100%'. Try exactly the same command in powershell and you will see 100%.

HRPuffnstuff · Aug 15, 2023

I ended up rolling back to 2115 on my desktop along with freezing updates until MS figures this out. Laptop seems to be okay with it though.

krzysiek · Aug 16, 2023

hello, I wanted to say that in this version 22631.2191 there are errors open windows overlap as you can see in the picture

jvickers · Aug 16, 2023

And just like that, my Bluetooth icon returned. I didn't even do anything...

HRPuffnstuff · Aug 16, 2023

After rolling back to before the last two updates my system will now play World of Warships without crashing. Not putting all the blame on MS as I also had to rollback my Nvidia driver to 536.09.

Almighty1 · Aug 16, 2023

jvickers said:
And just like that, my Bluetooth icon returned. I didn't even do anything...

Microsoft can change things even without sending builds as I remember a few years ago, Microsoft sent something that basically wouldn't allow even the taskbar to load so even the desktop won't load and everyone had broken machines until someone found a way to fix it which had something to do with changing the clock's date or time.

MiguelAngel11 · Aug 18, 2023

jvickers said:
And just like that, my Bluetooth icon returned. I didn't even do anything...

Mine still not showing, but toggling the Bluetooth option it appears. But I´m not connecting Bluetooth devices in the machine

DavidM · Aug 18, 2023

No Beta this week?

OAT · Aug 18, 2023

DavidM said:
No Beta this week?

Hi and welcome to the forum.
Please take the time to fill out your system's specs. It would be truly appreciated.
Release time is usually 10:00AM PST, 1:00PM EST and 18h00 in London, 19:00 in Paris, Madrid...

Bree · Aug 18, 2023

DavidM said:
No Beta this week?

Welcome to Eleven Forum.

With Insider builds there's no set day of the week for release, it's when MS think they have a new one ready. Wednesday or Thursday releases are typical, but 22621.2050/22631.2050 was released on 21st July, a Friday, so there may be one today.

KB5028256 Windows 11 Insider Beta 22621.2050 and 22631.2050 - July 21

UPDATE 7/26: https://www.elevenforum.com/t/kb5028251-windows-11-insider-beta-22621-2115-and-22631-2115-july-26.16657/ Windows Blogs: Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.2050 and Build 22631.2050 (KB5028256) to the Beta Channel. Build 22631.2050...

www.elevenforum.com

As OAT says, it's usually released at a set time of day. If that's your correct 'local time' beneath your avatar then you'll find out at 7:00pm today.

I wouldn't hold your breath though. There was expected to be a Dev build released yesterday, but apparently at the last minute it was pulled.

Windows 11 Insider Dev Build 23526.1000 (22H2) - Aug. 18

UPDATE 8/25: https://www.elevenforum.com/t/windows-11-insider-dev-build-23531-1001-22h2-aug-25.17436/ Windows Blogs: Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 23526 to the Dev Channel. We are releasing ISOs for this build – they can be downloaded here...

www.elevenforum.com

Bree · Aug 18, 2023

DavidM said:
No Beta this week?

Yes there is, and here it is.....

KB5029352 Windows 11 Insider Beta 22621.2199 and 22631.2199 - Aug. 18

UPDATE 8/24: https://www.elevenforum.com/t/kb5029339-windows-11-insider-beta-22621-2262-and-22631-2262-aug-24.17402/ Windows Blogs: Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.2191 and Build 22631.2191 (KB5029352) to the Beta Channel. Build 22631.2199...

www.elevenforum.com

Insider KB5029336 Windows 11 Insider Beta 22621.2191 and 22631.2191 - Aug. 10

What’s new in Build 22631.2191​

HDR Background Support ​

Narrator Natural Voices in French, Portuguese, English (India), German and Korea​

Changes and Improvements in Build 22631.2191​

[Windows 365]​

[Taskbar & System Tray]​

[File Explorer]​

[Windows Spotlight]​

Fixes in Build 22631.2191​

[File Explorer]​

[Dynamic Lighting]​

Known issues​

[General]​

[File Explorer]​

[Taskbar]​

[Input]​

[Narrator]​

About the Beta Channel​

Important Insider Links​

Attachments

Too young to know

My Computer

Well-known member

My Computer

Too young to know

My Computer

Well-known member

My Computer

Well-known member

My Computers

Well-known member

My Computer

Too young to know

My Computer

Well-known member

My Computers

Too young to know

My Computer

Well-known member

My Computers

Well-known member

My Computers

Well-known member

Attachments

My Computer

The lunatics have taken over the asylum

My Computers

Well-known member

My Computers

Well-known member

My Computer

Well-known member

My Computers

New member

My Computer

Pragmatic Member

My Computers

Well-known member

My Computers

Well-known member

My Computers

Similar threads

What’s new in Build 22631.2191

HDR Background Support

Narrator Natural Voices in French, Portuguese, English (India), German and Korea

Changes and Improvements in Build 22631.2191

[Windows 365]

[Taskbar & System Tray]

[File Explorer]

[Windows Spotlight]

Fixes in Build 22631.2191

[File Explorer]

[Dynamic Lighting]

Known issues

[General]

[File Explorer]

[Taskbar]

[Input]

[Narrator]

About the Beta Channel

Important Insider Links