Insider KB5052080 Windows 11 Insider Beta and Dev build 26120.3291 (24H2) - Feb. 21

HRPuffnstuff said:

I was seeing errors trying to run sfc in powershell preview 7.6 but once I used the release version the errors stopped.

Click to expand...

Without showing the CBS.log when it failed the 1st time you ran it, you cannot tell if the sfc errors were already repaired on the 1st pass.

fg2001gf11F said:

Without showing the CBS.log when it failed the 1st time you ran it, you cannot tell if the sfc errors were already repaired on the 1st pass.

Click to expand...

7.6 was having issues with multiple program files that prevented it from running but when the regular version ran it did not produce any errors and could complete the scan without issue.

HRPuffnstuff said:

7.6 was having issues with multiple program files that prevented it from running but when the regular version ran it did not produce any errors and could complete the scan without issue.

Click to expand...

What are the errors? Can you show the error message?

It runs fine here with P.S. 7.6.0-preview.3.

@fg2001gf11F - No idea but here is what's interesting.... /checkhealth and /scanhealth has the error 87 in Command Prompt but works fine in Powershell.
/restorehealth finally worked in command prompt but was stuck at 62.3% for close to an hour. So it seems to be adding a space or something to the first two. So either the problem is with command prompt or windows terminal as windows terminal was updated yesterday to v1.22.10352.0. These are done after the /restorehealth






Not sure if that is really a H or some ctrl character since you can see after the Error: 87, it seems to indicate it's a space as it's "scanhealth "option but why it does that only to /CheckHealth and /ScanHealth and not /RestoreHealth is a mystery.
Maybe the first /RestoreHealth really went out to rebuild the component store. I will try /SdanHealth and /CheckHealth after my next reboot to see if it makes a difference.

Looks like I got the reclaimable packages down to 2 from the previous low of 3 for 24H2 Beta builds...

Updated without issues unless mentioned below:


Windows Recovery Environment (WinRE) not updated as it's v26100.3180 updated by v26120.3281 Beta which is the case with both Windows Updated from v26120.3281 and a in-place repair install of v26120.3291.

The following all passed without any complaints unless noted:
Dism /Online /Cleanup-Image /CheckHealth
Dism /Online /Cleanup-Image /ScanHealth
Both of the above has an error 87 as noted in previous posts while using Command Prompt but worked fine with PowerShell
Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow
Dism /online /cleanup-image /analyzecomponentstore
Dism /online /cleanup-image /startcomponentcleanup

As noted previously, for Windows 11 24H2 Build 26120.3073 Beta, 26120.3281 Beta, 26120.3291 Beta - the DISM for for /ScanHealth and /RestoreHealth seems to be faster compared to 23H2, /CheckHealth is always instant.
As @asturias7 mentioned that 24H2 Build 26120.3073 Beta broke Intel Bluetooth and Realtek Audio, my Intel Bluetooth is working fine as I just tried my Bluetooth Wireless Cambridge Audio Melomania Touch True Wireless Headphones and they worked fine. This is on an Intel AX210 WiFi 6E/Bluetooth v5.3 on WiFi Drivers v23.120.0.3 and Bluetooth Drivers v23.120.0.4.

For the Realtek Audio,
The following configuration worked fine in Windows 11 23H2 Build 22635.4870 Beta:
Realtek UAD Audio Driver v6.0.9768.1
Realtek ASIO Component v1.0.13.1
Realtek Audio Effects Component (APO1) v13.0.6000.1505 for Hardware ID: SWC\VEN_10EC&AID_0001 - Windows 11
Realtek Audio Universal Service v1.0.821.8
Realtek Hardware Support Application v11.0.6000.355
Realtek Audio Console v1.52.354.0

but there is no sound on Windows 11 24H2 Build 26120.3073 Beta

I had to downgrade to:
Realtek Audio Effects Component (APO1) v13.1.6000.1076 for Hardware ID: SWC\VEN_10EC&AID_0001 - Windows 11 before sound was working again.

Same issue even if I used a older Realtek UAD Audio Driver.

I did uninstall and removed all drivers and used Dell's Realtek UAD Audio Driver v6.0.8991 which worked and then updated all the components to the versions above. The Realtek Audio Effects Component was already on v13.1.6000.1076
which worked until it was replaced with the newer v13.0.6000.1505 when the sound stopped working, then rolling back to v13.1.6000.1076 worked again. This is on a Dell XPS 15 9570 notebook computer.

I should also mention when there is no sound, it also made Fxsound unresponsive and when I restart the computer when the sound was not working, it also was stuck oņa endless restart on the screen so it seems like it was hanging all the processes on the computer as a whole.

With Realtek Audio UAD 6.0.9780.1 drivers, Realtek Audio Effects Component (APO1) v13.0.6000.1505 for Hardware ID: SWC\VEN_10EC&AID_0001 - Windows 11 works for sound output but the mic does not work while v13.1.6000.1076 works fine under Windows 11 24H2 Build 26120.3073 Beta. APO v13.1 did work fine with the mic under Windows 11 23H2 Beta Build 22635.4870. Same thing with Windows 11 24H2 Build 26120.3281 Beta. Realtek UAD Audio Driver v6.0.9785.1 drivers with Windows 11 24H2 Build 26120.3281 Beta has the exact same results as Realtek Audio UAD 6.0.9780.1 drivers. Realtek Audio Console v1.52.356.0 works fine with Windows 11 24H2 Build 26120.3281 Beta. Same exact results with Windows 11 24H2 Build 26120.3291 Beta.

Just like Windows 11 24H2 Build 26120.3073 Beta/26120.3281 Beta and 26120.3291 Beta compared to 23H2 Build 22635.4870 Beta as well as 23H2 Builds in general:
1) It takes a lot longer to load all the startup items
2) CPU % usage is higher

Almighty1 said:

@fg2001gf11F - No idea but here is what's interesting.... /checkhealth and /scanhealth has the error 87 in Command Prompt but works fine in Powershell.
/restorehealth finally worked in command prompt but was stuck at 62.3% for close to an hour. So it seems to be adding a space or something to the first two. So either the problem is with command prompt or windows terminal as windows terminal was updated yesterday to v1.22.10352.0. These are done after the /restorehealth


Not sure if that is really a H or some ctrl character since you can see after the Error: 87, it seems to indicate it's a space as it's "scanhealth "option but why it does that only to /CheckHealth and /ScanHealth and not /RestoreHealth is a mystery.
Maybe the first /RestoreHealth really went out to rebuild the component store. I will try /SdanHealth and /CheckHealth after my next reboot to see if it makes a difference.

Looks like I got the reclaimable packages down to 2 from the previous low of 3 for 24H2 Beta builds...

Click to expand...

@Almighty1 ,
There were several repairable components that were fixed by RESTOREHEALTH, but on my machines it was sitting at 62.3% not more than 10 minutes, I never had to wait an hour.
Also, I never had a problem running those DISM commands from command prompt or PowerShell. I rarely use Terminal, but I can give it a try.
That added "?" after the dism option seems to indicate that some unicode character was added to your line.
It shows in your dism.log as question mark after the letter H. It would be interesting to find what is causing that extra character.

fg2001gf11F said:

@Almighty1 ,
There were several repairable components that were fixed by RESTOREHEALTH, but on my machines it was sitting at 62.3% not more than 10 minutes, I never had to wait an hour.
Also, I never had a problem running those DISM commands from command prompt or PowerShell. I rarely use Terminal, but I can give it a try.
That added "?" after the dism option seems to indicate that some unicode character was added to your line.
It shows in your dism.log as question mark after the letter H. It would be interesting to find what is causing that extra character.

Click to expand...

I forgot to include another part, in the last and most recent entry here:
It's basically doing the offline fix for the 6824 Error. Replace /Online with /Image:C:\ but the guy didn't say it had to be done offline as it obviously didn't work while still online. Had to boot offline and command prompt where:
CHECKHEALTH and SCANHEALTH both completed successfully but with Component Store is repairable.
RESTOREHEALTH did not work as it said source file not found.
so the first restore health after rebooting was probably to fix the component store as remember the original restorehealth also was a error 87.
Well, Terminal loads PowerShell and also one can launch command prompt from there as it's usually right click on start menu and then Terminal (Admin) which will launch PS and then you can launch the other stuff like command prompt from there.
How are you actually launching powershell and command prompt if you don't use terminal? I didn't add any characters as it's from my text file that I copy and paste. Typing it works fine though. Maybe the copy is not 100% working as the clipboard will work and then stop working in the non 23H2 builds.
Actually, I always leave that txt file opened in notepad so when I login, I open notepad and the tab with that file is in it. So it appears that notepad either corrupted the line or something because if I copy the line except the last letter, h and type the h manually, copying it back to notepad first and then copy from notepad, it works. Thanks for the tip!

And maybe it was always that way, before I always copied the line with the space after the h at the end and it would give the 87 error so I always copied it with the space and pasted it but delete the space. This time as in earlier, I copied it to the h only so maybe there is some invisible character at the end.

@fg2001gf11F - Works fine now... the original dism lines were all copied and pasted from one of the older Beta Insiders posts into notepad which was probably 2 years ago... so probably there was some invisible character after the h which I didn't see as I usually copy with that blank space and then bacspace back to the h.

If you don't have the new trim feature for Snipping Tool screen recordings in Canary/Dev, make sure you have app version 11.2501.7.0 installed and enable this feature ID:

vivetool /enable /id:53250194

To enable the bugfix for an issue that prevents you from selecting multiple files in File Explorer's recommended files section by using Shift and clicking in 26120.3291 and 22635.4945+, run:

vivetool /enable /id:55910487

@fg2001gf11F

Decided to do a in-place repair upgrade of 26120.3291 with a UUPDump ISO and here are the results:





From: C:\Windows\Logs\CBS\CBS.log
2025-02-24 08:02:45, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\bthmodem.sys
2025-02-24 08:02:45, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\bthmodem.sys
One file this time, the max I have ever seen is 2.


Looks like it's back to 3 Reclaimable Packages, it was 2 when Windows Update took it to 26120.3291 from 26120.3281


Let's see what it says after the cleanup


So it's back to 2.

Windows Recovery Environment (WinRE) not updated as it's v26100.3180 updated by v26120.3281 Beta which is the case with both Windows Updated from v26120.3281 and a in-place repair install of v26120.3291.

Almighty1 said:

@fg2001gf11F

Decided to do a in-place repair upgrade of 26120.3291 with a UUPDump ISO and here are the results:

Code:

Dism /Online /Cleanup-Image /CheckHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.3291

No component store corruption detected.
The operation completed successfully.

Code:

Dism /Online /Cleanup-Image /ScanHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.3291

[==========================100.0%==========================] No component store corruption detected.
The operation completed successfully.

Code:

Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.3291

[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

Code:

sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.

From: C:\Windows\Logs\CBS\CBS.log
2025-02-24 08:02:45, Info DEPLOY [Pnp] Corrupt file: C:\WINDOWS\System32\drivers\bthmodem.sys
2025-02-24 08:02:45, Info DEPLOY [Pnp] Repaired file: C:\WINDOWS\System32\drivers\bthmodem.sys
One file this time, the max I have ever seen is 2.

Code:

Dism /online /cleanup-image /analyzecomponentstore

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.3291

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 14.38 GB

Actual Size of Component Store : 13.58 GB

    Shared with Windows : 7.76 GB
    Backups and Disabled Features : 5.82 GB
    Cache and Temporary Data : 1.76 MB

Date of Last Cleanup : 2025-02-24 02:57:41

Number of Reclaimable Packages : 3
Component Store Cleanup Recommended : Yes

The operation completed successfully.

Looks like it's back to 3 Reclaimable Packages, it was 2 when Windows Update took it to 26120.3291 from 26120.3281

Code:

Dism /online /cleanup-image /startcomponentcleanup

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.3291

[==========================100.0%==========================]
The operation completed successfully.

Let's see what it says after the cleanup

Code:

Dism /online /cleanup-image /analyzecomponentstore

Deployment Image Servicing and Management tool
Version: 10.0.26100.1150

Image Version: 10.0.26120.3291

[==========================100.0%==========================]

Component Store (WinSxS) information:

Windows Explorer Reported Size of Component Store : 10.93 GB

Actual Size of Component Store : 10.56 GB

    Shared with Windows : 7.76 GB
    Backups and Disabled Features : 2.80 GB
    Cache and Temporary Data :  0 bytes

Date of Last Cleanup : 2025-02-24 08:22:02

Number of Reclaimable Packages : 2
Component Store Cleanup Recommended : Yes

The operation completed successfully.

So it's back to 2.

Windows Recovery Environment (WinRE) not updated as it's v26100.3180 updated by v26120.3281 Beta which is the case with both Windows Updated from v26120.3821 and a in-place repair install of v26120.3921.

Click to expand...

Thanks for posting this. I am about to do the same. Creating UUPISO now.

Almighty1 said:

Windows Recovery Environment (WinRE) not updated as it's v26100.3180 updated by v26120.3281 Beta which is the case with both Windows Updated from v26120.3821 and a in-place repair install of v26120.3921.

Click to expand...

Looks like you have a typo, should be 26120.3291. And 26120.3281.

On one of the machines that had problems updating I used the recovery option with W.U. repair version instead of using an ISO.
Pretty slow, but that worked, and after that the SCANHEALTH did not find any repairable component.
3 machines with this update had 3 different results. 2 of them had to use RESTOREHEALTH to repair the components found by SCANHEALTH.

fg2001gf11F said:

Looks like you have a typo, should be 26120.3291.

On one of the machines that had problems updating I used the recovery option with W.U. repair version instead of using an ISO.
Pretty slow, but that worked, and after that the SCANHEALTH did not find any repairable component.
3 machines with this update had 3 different results. 2 of them had to use RESTOREHEALTH to repair the components found by SCANHEALTH.

Click to expand...

I did the install using UUPDUMP iso and it worked. I now run dism without difficulty and no errors!

fg2001gf11F said:

Looks like you have a typo, should be 26120.3291. And 26120.3281.

On one of the machines that had problems updating I used the recovery option with W.U. repair version instead of using an ISO.
Pretty slow, but that worked, and after that the SCANHEALTH did not find any repairable component.
3 machines with this update had 3 different results. 2 of them had to use RESTOREHEALTH to repair the components found by SCANHEALTH.

Click to expand...

You are right... I typed without looking and the 2 was in the wrong place. I didn't have any problems updating, I just never did a in-place repair install since a few months ago with 23H2 Beta. How exactly do you do the recovery option with WU repair version?

fg2001gf11F said:

Looks like you have a typo, should be 26120.3291.

On one of the machines that had problems updating I used the recovery option with W.U. repair version instead of using an ISO.
Pretty slow, but that worked, and after that the SCANHEALTH did not find any repairable component.
3 machines with this update had 3 different results. 2 of them had to use RESTOREHEALTH to repair the components found by SCANHEALTH.

Click to expand...

You know. But there are people that never check these readings and their PC are running just fine. I never did this with Win 7 nor Win 10 and they always ran great. Are we being overly cautious? Are we exaggerating? I can't see doing this on every single Insider build. That's once or twice a week and that's a lot of time spent on checking and rechecking. Then if it's not perfect, reinstall, download iso, create UUP Dump ISO, installing and reinstalling... etc, etc. This is a lot of wasted time. Could be why a lot of people are switching to Linux.

magilla said:

I did the install using UUPDUMP iso and it worked. I now run dism without difficulty and no errors!

Click to expand...

My DISM never had errors as it seems it was my paste from the copy my notepad txt file that had some character after the h from the word Health in /ScanHealth, /CheckHealth, /RestoreHealth that was causing the Error 87 as @fg2001gf11F pointed out with many thanks to him.

mecanicogolf said:

You know. But there are people that never check these readings and their PC are running just fine. I never did this with Win 7 nor Win 10 and they always ran great. Are we being overly cautious? Are we exaggerating? I can't see doing this on every single Insider build. That's once or twice a week and that's a lot of time spent on checking and rechecking. Then if it's not perfect, reinstall, download iso, create UUP Dump ISO, installing and reinstalling... etc, etc. This is a lot of wasted time. Could be why a lot of people are switching to Linux.

Click to expand...

I think you are correct. I didn't do this until I joined the insider group and the TenForum and ElevenForum. The fact that as an Insider and we are dealing with experimental builds makes me think this is a good practice. Who knows??? BTW, when I am too busy to do these checks, they don't get done!

What's funny is I don't do the sfc /scannow and DISM stuff on the Canary build running as a VM under Hyper-V on Beta. I noticed something interesting with the VM too. Downloading and everything is fast but Microsoft Store and Windows Update seems to be way slower compared to the host.

Almighty1 said:

You are right... I typed without looking and the 2 was in the wrong place. I didn't have any problems updating, I just never did a in-place repair install since a few months ago with 23H2 Beta. How exactly do you do the recovery option with WU repair version?

Click to expand...

@Almighty1,

This is the recovery option that downloads the Repair version with W.U. and reinstalls, similar as an update/repair in place that you do with ISO.