Insider KB5027295 Windows 11 Insider Beta 22621.1972 and 22631.1972 - June 29


UPDATE 7/13:
www.elevenforum.com

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 www.elevenforum.com


 Windows Blogs:

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.1972 and Build 22631.1972 (KB5027295) to the Beta Channel.
  • Build 22631.1972 = New features rolling out.
  • Build 22621.1972 = New features off by default.

KB5027397 Enablement Package for Windows 11 22H2 build 22621.xxx to build 22631.xxx


REMINDER: Insiders who were previously on Build 22624 will automatically get moved to Build 22631 via an enablement package. The enablement package artificially increments the build number for the update with new features getting rolled out and turned on to make it easier to differentiate from devices with the update with features off by default. This approach is being used for the Beta Channel only and is not indicative of any changes or plans for final feature rollouts.

Insiders who landed in the group with new features turned off by default (Build 22621.1972) can check for updates and choose to install the update that will have features rolling out (Build 22631.1972).

Changes and Improvements in Build 22631.1972

[File Explorer]
  • Windows Insiders in the Beta Channel on Build 22631 are now previewing the Windows App SDK version of File Explorer. Functionality in File Explorer remains unchanged, it just switches from using WinUI 2 to using WinUI 3.
Fixes in Build 22631.1972

[Settings]
  • The option to “Hide date and time in the System tray” from the last flight should no longer be backwards (on being off, off being on).

    www.elevenforum.com

    Show or Hide Time and Date on Taskbar System Tray in Windows 11

    This tutorial will show you how to hide the time and date on the taskbar system tray for your account in Windows 11. The clock on the taskbar system tray shows the system time and date by default. Starting with Windows 11 version 22H2 KB5030310 Build 22621.2361, you can now hide the time and...
    www.elevenforum.com www.elevenforum.com
Fixes for BOTH Build 22621.1972 & Build 22631.1972
  • New! This update improves several simplified Chinese fonts and the Microsoft Pinyin Input Method Editor (IME) to support GB18030-2022. You can enter and display characters from conformance level 1 or 2 using the additions to Microsoft Yahei, Simsun, and Dengxian. This update now supports Unicode Extensions E and F in the Simsun Ext-B font. This meets the requirements for level 3.
  • New! With this update, you can now authenticate across Microsoft clouds. This feature also satisfies Conditional Access checks if they are needed.
  • New! This update improves the sharing of a local file in File Explorer with Microsoft Outlook contacts. You now have the option to quickly email the file to yourself. In addition, loading your contacts from Outlook is better. This feature is not available for files stored in Microsoft OneDrive folders. OneDrive has its own sharing functionality.
  • New! This update expands the roll out of notification badging for Microsoft accounts on the Start menu. A Microsoft account is what connects Windows to your Microsoft apps. The account backs up all your data and helps you to manage your subscriptions. You can also add extra security steps to keep you from being locked out of your account. This feature gives you quick access to important account-related notifications.

    www.elevenforum.com

    Enable or Disable Notification Badging for Microsoft Accounts on Start menu in Windows 11

    This tutorial will show you how to enable or disable showing notification badging for Microsoft accounts on the Start menu and Settings for your account in Windows 10 and Windows 11. Starting with Windows 11 build 25290, Microsoft started a new exploration of badging on the Start menu with two...
    www.elevenforum.com www.elevenforum.com
  • New! This update adds many new features and improvements to Microsoft Defender for Endpoint. For more information, see Microsoft Defender for Endpoint.
  • This update addresses an issue that affects TextInputHost.exe. It stops working.
  • This update addresses an issue that affects HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders. You can now set and maintain the correct default permissions for this directory path. When the permissions are wrong, Start menu, search, and Azure Active Directory (Azure AD) authentication fails.
  • This update addresses an issue that affects devices that use the Network Protector for BitLocker. The device will not resume after it has been suspended.
  • This update addresses an issue that affects certain applications that use IDBObjectStore. They do not work in Microsoft Edge and IE mode.
  • This update addresses an issue that affects a scheduled monthly task. It might not run on time if the next occurrence happens when daylight savings time occurs.
  • This update addresses an issue that affects Narrator. It reads the wrong state when you cancel the selection of an option button you have selected.
  • This update gives user accounts the ability to open an elevated Windows Terminal. This only works if they use an admin account that has not signed in before.
  • This update addresses an issue that affects File Explorer (explorer.exe). It stops working.
  • This update addresses an issue that affects Narrator. The issue stops Narrator from retaining your scan mode when you switch between browsers.
  • This update addresses an issue that affects certain apps. It stops working when it tries to scan a barcode.
  • This update addresses an issue that affects Microsoft Intune push notifications. The issue stops devices that have less than 3.5 GB of RAM from getting them.
  • This update addresses an issue that affects Teams. The issue stops Teams from alerting you about missed calls or messages.
  • This update addresses an issue that affects File Explorer windows. They unexpectedly appear in the foreground.
  • This update affects Active Directory event ID 1644 processing. It now accepts events of greater than 64 KB in length. This change truncates Lightweight Directory Access Protocol (LDAP) queries contained within event 1644 to 20000 characters by default. You can configure the 20K value using the registry key “DEFAULT_DB_EXPENSIVE_SEARCH_FILTER_MAX_LOGGING_LENGTH_IN_CHARS.”
  • This update addresses an issue that affects Azure Virtual Desktop and Windows 365 users. You might not see the right location for a Remote Desktop session in your virtual machine or Cloud PC.
  • This update affects the reliability of Windows. It improves after you update the OS.
  • This update addresses an issue that affects some earbuds. They stop streaming music.
  • This update addresses an issue that affects .msi files. A minor update is not installed. This occurs when you use the EnterpriseDesktopAppManagement configuration service provider (CSP) to distribute the .msi file.
  • This update addresses an issue that affects a tib.sys driver. It does not load. This occurs when HyperVisor-protected Code Integrity (HVCI) is enabled.
  • This update addresses an issue that affects the on-screen keyboard. The issue stops it from opening after you lock the machine.
  • This update addresses an issue that affects msftconnecttext.net. It gets excessive HTTP traffic.
  • This update addresses an issue that might affect your computer when you are playing a game. Timeout Detection and Recovery (TDR) errors might occur.
  • This update addresses an issue that affects those who enable the “Smart Card is Required for Interactive Logon” account option. When RC4 is disabled, you cannot authenticate to Remote Desktop Services farms. The error message is, “An authentication error has occurred. The requested encryption type is not supported by the KDC.”
  • This update addresses an issue that affects the Recommended section of the Start menu. When you right-click a local file, it does not behave as expected.
  • This update affects the Desktop Window Manager (DWM). It improves its reliability.
  • This update addresses an issue that affects all the registry settings under the Policies paths. They might be deleted. This occurs when you do not rename the local temporary user policy file during Group Policy processing.
  • This update addresses an issue that affects the Spooler service. It stops working. This issue occurs when you print using a certain workspace.
  • This update addresses an issue that affects certain apps. In some instances, video flickering occurs.
  • This update addresses an issue that affects File Explorer. It might stop responding indefinitely. This occurs after you try to view the effective access permissions for files in File Explorer.
About the Beta Channel

The Beta Channel is the place we preview experiences that are closer to what we will ship to our general customers. Because the Dev and Beta Channels represent parallel development paths from our engineers, there may be cases where features and experiences show up in the Beta Channel first. However, this does not mean every feature we try out in the Beta Channel will ship. We encourage Insiders to read this blog post that outlines the ways we’ll try things out with Insiders in both the Dev and Beta Channels.

Important Insider Links
Thanks,
Amanda & Brandon


 Source:

blogs.windows.com

Announcing Windows 11 Insider Preview Build 22621.1972 and 22631.1972

Hello Windows Insiders, today we are releasing Windows 11 Insider Preview Build 22621.1972 and Build 22631.1972 (KB5027295) to the Beta Channel.
blogs.windows.com blogs.windows.com


Check Windows Updates


UUP Dump:

64-bit ISO download:
uupdump.net

Select language for Windows 11 Insider Preview 10.0.22621.1972 (ni_release) amd64

Select language for Windows 11 Insider Preview 10.0.22621.1972 (ni_release) amd64 on UUP dump. UUP dump lets you download Unified Update Platform files, like Windows Insider updates, directly from Windows Update.
uupdump.net
uupdump.net

Select language for Windows 11 Insider Preview 10.0.22631.1972 (ni_release) amd64

Select language for Windows 11 Insider Preview 10.0.22631.1972 (ni_release) amd64 on UUP dump. UUP dump lets you download Unified Update Platform files, like Windows Insider updates, directly from Windows Update.
uupdump.net

ARM64 ISO download:
uupdump.net

Select language for Windows 11 Insider Preview 10.0.22621.1972 (ni_release) arm64

Select language for Windows 11 Insider Preview 10.0.22621.1972 (ni_release) arm64 on UUP dump. UUP dump lets you download Unified Update Platform files, like Windows Insider updates, directly from Windows Update.
uupdump.net
uupdump.net

Select language for Windows 11 Insider Preview 10.0.22631.1972 (ni_release) arm64

Select language for Windows 11 Insider Preview 10.0.22631.1972 (ni_release) arm64 on UUP dump. UUP dump lets you download Unified Update Platform files, like Windows Insider updates, directly from Windows Update.
uupdump.net

www.elevenforum.com

UUP Dump - Download Windows Insider ISO

UUP Dump is the most practical and easy way to get ISO images of any Insider Windows 10 or Windows 11 version, as soon as Microsoft has released a new build. UUP Dump creates a download configuration file according to your choices, downloads necessary files directly from Microsoft servers, and...
www.elevenforum.com www.elevenforum.com
 
Last edited:
Click to expand...
Anyone know what is the process that handles this search box as mines stop allowing input which I am sure a reboot will fix and it did, the start menu also didn't show when clicking on it.

1688235036572.png
 
Last edited:

My Computer

System One

  • OS
    Windows XP/7/8/8.1/10/11, Linux, Android, FreeBSD Unix
    Computer type
    Laptop
    Manufacturer/Model
    Dell XPS 15 9570
    CPU
    Intel® Core™ i7-8750H 8th Gen Processor 2.2Ghz up to 4.1Ghz
    Motherboard
    Dell XPS 15 9570
    Memory
    32GB using 2x16GB modules
    Graphics Card(s)
    Intel UHD 630 & NVIDIA GeForce GTX 1050 Ti with 4GB DDR5
    Sound Card
    Realtek ALC3266-CG
    Monitor(s) Displays
    15.6" 4K Touch UltraHD 3840x2160 made by Sharp
    Screen Resolution
    3840x2160
    Hard Drives
    Toshiba KXG60ZNV1T02 NVMe 1024GB/1TB SSD
    PSU
    Dell XPS 15 9570
    Case
    Dell XPS 15 9570
    Cooling
    Stock
    Keyboard
    Stock
    Mouse
    SwitftPoint ProPoint
    Internet Speed
    Comcast/XFinity 1.44Gbps/42.5Mbps
    Browser
    Microsoft EDGE (Chromium based) & Google Chrome
    Antivirus
    Windows Defender that came with Windows
I cannot clean up the component store after updating to 22631.1972. This has happened on two independent machines, one a VM, the other a laptop. For many builds now dism /online /cleanup-image /analyzecomponentstore has reported multiple reclaimable packages but dism /online /cleanup-image /startcomponentcleanup has been unable to remove them. That I assumed was a legacy of having been through the gamut of the 22621/22622/22623/22624/22631 enablement packages, but at least dism /online /cleanup-image /startcomponentcleanup had been able to shrink the component store after each CU, so I ignored them.

But after the 22631.1972 CU dism /online /cleanup-image /startcomponentcleanup fails with:

Error: 6824
The operation cannot be performed because another transaction is depending on the fact that this property will not change.

1688248750767.png

This error has been seen before in Windows 10 and reported by @Ed Tittel. Apparently a second reboot fixed it that time, but not in this case.

Second Reboot Fixes DISM StartComponentCleanup Error 6824 - Windows Enterprise Desktop

Second reboot fixes DISM StartComponentCleanup error 6824, so if you see this you can make it work that way, too.
www.techtarget.com www.techtarget.com

I fixed the issue on the laptop, but could only do that because it was running both Beta and Dev builds as native boot .vhdx. I booted to DEV, mounted the .vhdx for Beta as the D: drive, then ran DISM.exe /Image:D:\ /cleanup-image /startcomponentcleanup to clean up the component store while offline.


Edit: I have just successfully done the same offline fix on the .vhdx for my Hyper-V Win11 Beta VM.

1688252081897.png

On restarting the VM it briefly showed the 'installing updates' message. A few of the (un)reclaimable packages had been removed and dism /online /cleanup-image /startcomponentcleanup now runs successfully (stopping at 20% as it always does when run on a clean component store).

1688252373774.png
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Just for the record...

sfc /scannow

Beginning system scan. This process will take some time.

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

Windows Resource Protection did not find any integrity violations.
 

My Computer

System One

  • OS
    Windows XP/7/8/8.1/10/11, Linux, Android, FreeBSD Unix
    Computer type
    Laptop
    Manufacturer/Model
    Dell XPS 15 9570
    CPU
    Intel® Core™ i7-8750H 8th Gen Processor 2.2Ghz up to 4.1Ghz
    Motherboard
    Dell XPS 15 9570
    Memory
    32GB using 2x16GB modules
    Graphics Card(s)
    Intel UHD 630 & NVIDIA GeForce GTX 1050 Ti with 4GB DDR5
    Sound Card
    Realtek ALC3266-CG
    Monitor(s) Displays
    15.6" 4K Touch UltraHD 3840x2160 made by Sharp
    Screen Resolution
    3840x2160
    Hard Drives
    Toshiba KXG60ZNV1T02 NVMe 1024GB/1TB SSD
    PSU
    Dell XPS 15 9570
    Case
    Dell XPS 15 9570
    Cooling
    Stock
    Keyboard
    Stock
    Mouse
    SwitftPoint ProPoint
    Internet Speed
    Comcast/XFinity 1.44Gbps/42.5Mbps
    Browser
    Microsoft EDGE (Chromium based) & Google Chrome
    Antivirus
    Windows Defender that came with Windows
Bree said:
I cannot clean up the component store after updating to 22631.1972. This has happened on two independent machines, one a VM, the other a laptop. For many builds now dism /online /cleanup-image /analyzecomponentstore has reported multiple reclaimable packages but dism /online /cleanup-image /startcomponentcleanup has been unable to remove them. That I assumed was a legacy of having been through the gamut of the 22621/22622/22623/22624/22631 enablement packages, but at least dism /online /cleanup-image /startcomponentcleanup had been able to shrink the component store after each CU, so I ignored them.

But after the 22631.1972 CU dism /online /cleanup-image /startcomponentcleanup fails with:

Error: 6824
The operation cannot be performed because another transaction is depending on the fact that this property will not change.

View attachment 63800

This error has been seen before in Windows 10 and reported by @Ed Tittel. Apparently a second reboot fixed it that time, but not in this case.

Second Reboot Fixes DISM StartComponentCleanup Error 6824 - Windows Enterprise Desktop

Second reboot fixes DISM StartComponentCleanup error 6824, so if you see this you can make it work that way, too.
www.techtarget.com www.techtarget.com

I fixed the issue on the laptop, but could only do that because it was running both Beta and Dev builds as native boot .vhdx. I booted to DEV, mounted the .vhdx for Beta as the D: drive, then ran DISM.exe /Image:D:\ /cleanup-image /startcomponentcleanup to clean up the component store while offline.


Edit: I have just successfully done the same offline fix on the .vhdx for my Hyper-V Win11 Beta VM.

View attachment 63807

On restarting the VM it briefly showed the 'installing updates' message. A few of the (un)reclaimable packages had been removed and dism /online /cleanup-image /startcomponentcleanup now runs successfully (stopping at 20% as it always does when run on a clean component store).

View attachment 63808
Click to expand...
Getting the same error. So, how do I get a vhdx file of the windows build to use? Can I do this using UUPDUMP?
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom built
    CPU
    Ryzen 5600X
    Motherboard
    ASRock Steel Legend
    Memory
    16GB
    Graphics Card(s)
    EVGA GT 710
    Sound Card
    None
    Monitor(s) Displays
    23",24", 19" - flat panels
    Screen Resolution
    1920x1200
    Hard Drives
    None - only M.2 SATA and NVMe drives
    PSU
    750W
    Case
    Antec
    Cooling
    stock Wraith cooler
    Keyboard
    Corsair gaming
    Mouse
    Logitech M720
    Internet Speed
    1Gb
Bree said:
The operation cannot be performed because another transaction is depending on the fact that this property will not change
Click to expand...


Just a thought. Have you tried the DISM "reset base" option.
I'm wondering if that might be like... taking the component store, temporarily, offline?

Sort of like running chkdsk on the C: drive?

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase



The message you're getting, sounds like it's saying... the component store is in use by another transaction.
It could of course, be some not well thought out MS change, also?

If you have a good backup, it might be something to try.
Might also try it from a command prompt in the Recovery environment, aka, outside of Windows.
 

My Computers

System One System Two

  • OS
    Win 11 Home ♦♦♦26100.3037 ♦♦♦♦♦♦♦24H2 ♦♦♦non-Insider
    Computer type
    PC/Desktop
    Manufacturer/Model
    Built by Ghot® [May 2020]
    CPU
    AMD Ryzen 7 3700X
    Motherboard
    Asus Pro WS X570-ACE (BIOS 4702)
    Memory
    G.Skill (F4-3200C14D-16GTZKW)
    Graphics Card(s)
    EVGA RTX 2070 (08G-P4-2171-KR)
    Sound Card
    Realtek ALC1220P / ALC S1220A
    Monitor(s) Displays
    Dell U3011 30"
    Screen Resolution
    2560 x 1600
    Hard Drives
    2x Samsung 860 EVO 500GB,
    WD 4TB Black FZBX - SATA III,
    WD 8TB Black FZBX - SATA III,
    DRW-24B1ST CD/DVD Burner
    PSU
    PC Power & Cooling 750W Quad EPS12V
    Case
    Cooler Master ATCS 840 Tower
    Cooling
    CM Hyper 212 EVO (push/pull)
    Keyboard
    Ducky DK9008 Shine II Blue LED
    Mouse
    Logitech Optical M-100
    Internet Speed
    300/300
    Browser
    Firefox (latest)
    Antivirus
    Bitdefender Internet Security
    Other Info
    Speakers: Klipsch Pro Media 2.1
  • Operating System
    Windows XP Pro 32bit w/SP3
    Computer type
    PC/Desktop
    Manufacturer/Model
    Built by Ghot® (not in use)
    CPU
    AMD Athlon 64 X2 5000+ (OC'd @ 3.2Ghz)
    Motherboard
    ASUS M2N32-SLI Deluxe Wireless Edition
    Memory
    TWIN2X2048-6400C4DHX (2 x 1GB, DDR2 800)
    Graphics card(s)
    EVGA 256-P2-N758-TR GeForce 8600GT SSC
    Sound Card
    Onboard
    Monitor(s) Displays
    ViewSonic G90FB Black 19" Professional (CRT)
    Screen Resolution
    up to 2048 x 1536
    Hard Drives
    WD 36GB 10,000rpm Raptor SATA
    Seagate 80GB 7200rpm SATA
    Lite-On LTR-52246S CD/RW
    Lite-On LH-18A1P CD/DVD Burner
    PSU
    PC Power & Cooling Silencer 750 Quad EPS12V
    Case
    Generic Beige case, 80mm fans
    Cooling
    ZALMAN 9500A 92mm CPU Cooler
    Mouse
    Logitech Optical M-BT96a
    Keyboard
    Logitech Classic Keybooard 200
    Internet Speed
    300/300
    Browser
    Firefox 3.x ??
    Antivirus
    Symantec (Norton)
    Other Info
    Still assembled, still runs. Haven't turned it on for 13 years?
Ghot said:
Just a thought. Have you tried the DISM "reset base" option.
I'm wondering if that might be like... taking the component store, temporarily, offline?

Sort of like running chkdsk on the C: drive?

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase



The message you're getting, sounds like it's saying... the component store is in use by another transaction.
It could of course, be some not well thought out MS change, also?

If you have a good backup, it might be something to try.
Might also try it from a command prompt in the Recovery environment.
Click to expand...
This does not fix the issue
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom Built
    CPU
    Intel i9 14900KF
    Motherboard
    Asus z790 ProArt Creator WiFi
    Memory
    64GB Corsair Vengeance RGB
    Graphics Card(s)
    MSI 4090 Suprim X
    Sound Card
    Onboard
    Monitor(s) Displays
    1 x Asus 24". 1 x Asus 32"
    Screen Resolution
    1920x1080 & 2560 x 1440
    Hard Drives
    Multiple
    PSU
    Corsair 1200HX
    Case
    Corsair 7000D RGB
    Cooling
    Corsair H150I Capellix XT
    Keyboard
    Corsair K70 RGB MK.2
    Mouse
    Corsair M55 RGB Pro
    Internet Speed
    1000Mb/s
    Browser
    Edge
    Antivirus
    Windows Default
Mark Phelps said:
Getting the same error. So, how do I get a vhdx file of the windows build to use? Can I do this using UUPDUMP?
Click to expand...
Both my machines had .vhdx files as their C: drive, one a VM, the other a native boot .vhdx install, so it was relatively easy for me.

If you have a standard install of Beta on a PC then there is no .vhdx file for you to work on. To be able to do an offline clean up of the component store you need to boot from something else so that the installed Windows isn't running, and from which you can run DISM. Booting to a Command prompt in Advanced Startup will fit the job.

When running DISM like this you'll need to provide a scratch directory for it to use, the default Temp directory in the recovery environment is too small. The directory must already exist.

1688260508506.png

So when booted to a Command Prompt the command you'd need to use would be be something like:
DISM /Image:C:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Ghot said:
Just a thought. Have you tried the DISM "reset base" option.
I'm wondering if that might be like... taking the component store, temporarily, offline?

Sort of like running chkdsk on the C: drive?

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase
Click to expand...
Yes, I had tried that. I had also tried running the Windows Update Troubleshooter. I also tried booting to Safe Mode, running Dism's /RestoreHealth and sfc /scannow before trying to clean up. Nothing worked.
Ghot said:
The message you're getting, sounds like it's saying... the component store is in use by another transaction.
It could of course, be some not well thought out MS change, also?

If you have a good backup, it might be something to try.
Might also try it from a command prompt in the Recovery environment, aka, outside of Windows.
Click to expand...
The only way I could find to clean up the component store was to do so while Windows is off line, ie: you have to do it from another OS. Running Dism from the recovery environment command prompt is one way to achieve that. Yes, the brief 'installing updates' message on the first boot after the repair strongly suggests there was an incomplete transaction stuck in the pipeline after installing this CU.
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Bree said:
Both my machines had .vhdx files as their C: drive, one a VM, the other a native boot .vhdx install, so it was relatively easy for me.

If you have a standard install of Beta on a PC then there is no .vhdx file for you to work on. To be able to do an offline clean up of the component store you need to boot from something else so that the installed Windows isn't running, and from which you can run DISM. Booting to a Command prompt in Advanced Startup will fit the job.

When running DISM like this you'll need to provide a scratch directory for it to use, the default Temp directory in the recovery environment is too small. The directory must already exist.

View attachment 63817

So when booted to a Command Prompt the command you'd need to use would be be something like:
DISM /Image:C:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
Click to expand...
Used a similar method:

I booted from a usb with the latest build on, selected repair, then command prompt and ran the above command. Only trick is then to find which drive is you drive with your Windows installed on. You can do this by selecting each drive (type in drive letter i.e. d:, press enter), and then typing in dir/w in my case my drive was F

So, I type in the following:

DISM /Image:F:\ /cleanup-image /startcomponentcleanup /ScratchDir:F:\Temp

Waited for it to complete, rebooted, and then ran

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase, no more errors

Now I just need to figure out why I no longer have the Windows Security tooltip
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom Built
    CPU
    Intel i9 14900KF
    Motherboard
    Asus z790 ProArt Creator WiFi
    Memory
    64GB Corsair Vengeance RGB
    Graphics Card(s)
    MSI 4090 Suprim X
    Sound Card
    Onboard
    Monitor(s) Displays
    1 x Asus 24". 1 x Asus 32"
    Screen Resolution
    1920x1080 & 2560 x 1440
    Hard Drives
    Multiple
    PSU
    Corsair 1200HX
    Case
    Corsair 7000D RGB
    Cooling
    Corsair H150I Capellix XT
    Keyboard
    Corsair K70 RGB MK.2
    Mouse
    Corsair M55 RGB Pro
    Internet Speed
    1000Mb/s
    Browser
    Edge
    Antivirus
    Windows Default
PurSpyk!! said:
... I type in the following:

DISM /Image:F:\ /cleanup-image /startcomponentcleanup /ScratchDir:F:\Temp

Waited for it to complete, rebooted, and then ran

Dism.exe /online /Cleanup-Image /StartComponentCleanup /ResetBase, no more errors

Now I just need to figure out why I no longer have the Windows Security tooltip
Click to expand...
Not sure the two are connected. I still have the tooltip in my VM after the offline cleanup.

1688263656754.png
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Bree said:
I cannot clean up the component store after updating to 22631.1972. This has happened on two independent machines, one a VM, the other a laptop. For many builds now dism /online /cleanup-image /analyzecomponentstore has reported multiple reclaimable packages but dism /online /cleanup-image /startcomponentcleanup has been unable to remove them. That I assumed was a legacy of having been through the gamut of the 22621/22622/22623/22624/22631 enablement packages, but at least dism /online /cleanup-image /startcomponentcleanup had been able to shrink the component store after each CU, so I ignored them.

But after the 22631.1972 CU dism /online /cleanup-image /startcomponentcleanup fails with:

Error: 6824
The operation cannot be performed because another transaction is depending on the fact that this property will not change.

View attachment 63800

This error has been seen before in Windows 10 and reported by @Ed Tittel. Apparently a second reboot fixed it that time, but not in this case.

Second Reboot Fixes DISM StartComponentCleanup Error 6824 - Windows Enterprise Desktop

Second reboot fixes DISM StartComponentCleanup error 6824, so if you see this you can make it work that way, too.
www.techtarget.com www.techtarget.com

I fixed the issue on the laptop, but could only do that because it was running both Beta and Dev builds as native boot .vhdx. I booted to DEV, mounted the .vhdx for Beta as the D: drive, then ran DISM.exe /Image:D:\ /cleanup-image /startcomponentcleanup to clean up the component store while offline.


Edit: I have just successfully done the same offline fix on the .vhdx for my Hyper-V Win11 Beta VM.

View attachment 63807

On restarting the VM it briefly showed the 'installing updates' message. A few of the (un)reclaimable packages had been removed and dism /online /cleanup-image /startcomponentcleanup now runs successfully (stopping at 20% as it always does when run on a clean component store).

View attachment 63808
Click to expand...
Sorry for your trouble!

I just tested and mine is working fine on both installation Computer & VM.

1688267871361.png

1688267905834.png
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Asus/Custom Build
    CPU
    Intel® Xeon® X5690 3.47GHz Six-Core
    Motherboard
    Asus P6T Deluxe v2
    Memory
    G.Skill PC3-12800 1600MHz 24GB
    Graphics Card(s)
    NVIDIA GeForce GTX 1050
    Sound Card
    SoundMAX ADI AD2000B HD Audio
    Monitor(s) Displays
    Acer T232HL Touch Screen
    Screen Resolution
    1920 x 1080 @ 60Hz
    Hard Drives
    6 Crucial MX500 SSD 1TB each.
    PSU
    Thermaltake Toughpower Gold 850W
    Case
    Thermaltake Armor VA8000SWA
    Cooling
    Thermaltake Air Cooling System
    Keyboard
    Illuminated Multimedia LED Keyboard
    Mouse
    M16 Dual Mode Illuminated Mouse - Bluetooth / 2.4 GHz Mode
    Internet Speed
    800 Mbps
    Browser
    Edge / Opera / Vivaldi / Chrome / Firefox / Brave
    Antivirus
    Windows Defender Security
JGToy said:
Sorry for your trouble!

I just tested and mine is working fine on both installation Computer & VM.
Click to expand...
Thanks for that, it's always interesting to learn that it's not affecting everyone. I wonder if it's a regional issue? Mine is an en-gb install.

I note that your /AnalyzeComponentStore is showing 16 reclaimable packages. I'm guessing they're still there, as mine are, after each clean up. This seems to be a seperate issue and has never been a problem for me, the clean up still seemed to be effective.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Bree said:
Thanks for that, it's always interesting to learn that it's not affecting everyone. I wonder if it's a regional issue? Mine is an en-gb install.

I note that your /AnalyzeComponentStore is showing 16 reclaimable packages. I'm guessing they're still there, as mine are, after each clean up. This seems to be a seperate issue and has never been a problem for me, the clean up still seemed to be effective.
Click to expand...
I thought about the regional problem.

And thanks for the feedback above, I will take a look on that!
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Asus/Custom Build
    CPU
    Intel® Xeon® X5690 3.47GHz Six-Core
    Motherboard
    Asus P6T Deluxe v2
    Memory
    G.Skill PC3-12800 1600MHz 24GB
    Graphics Card(s)
    NVIDIA GeForce GTX 1050
    Sound Card
    SoundMAX ADI AD2000B HD Audio
    Monitor(s) Displays
    Acer T232HL Touch Screen
    Screen Resolution
    1920 x 1080 @ 60Hz
    Hard Drives
    6 Crucial MX500 SSD 1TB each.
    PSU
    Thermaltake Toughpower Gold 850W
    Case
    Thermaltake Armor VA8000SWA
    Cooling
    Thermaltake Air Cooling System
    Keyboard
    Illuminated Multimedia LED Keyboard
    Mouse
    M16 Dual Mode Illuminated Mouse - Bluetooth / 2.4 GHz Mode
    Internet Speed
    800 Mbps
    Browser
    Edge / Opera / Vivaldi / Chrome / Firefox / Brave
    Antivirus
    Windows Defender Security
Bree said:
I cannot clean up the component store after updating to 22631.1972. This has happened on two independent machines, one a VM, the other a laptop. For many builds now dism /online /cleanup-image /analyzecomponentstore has reported multiple reclaimable packages but dism /online /cleanup-image /startcomponentcleanup has been unable to remove them. That I assumed was a legacy of having been through the gamut of the 22621/22622/22623/22624/22631 enablement packages, but at least dism /online /cleanup-image /startcomponentcleanup had been able to shrink the component store after each CU, so I ignored them.

But after the 22631.1972 CU dism /online /cleanup-image /startcomponentcleanup fails with:

Error: 6824
The operation cannot be performed because another transaction is depending on the fact that this property will not change.

View attachment 63800

This error has been seen before in Windows 10 and reported by @Ed Tittel. Apparently a second reboot fixed it that time, but not in this case.

Second Reboot Fixes DISM StartComponentCleanup Error 6824 - Windows Enterprise Desktop

Second reboot fixes DISM StartComponentCleanup error 6824, so if you see this you can make it work that way, too.
www.techtarget.com www.techtarget.com

I fixed the issue on the laptop, but could only do that because it was running both Beta and Dev builds as native boot .vhdx. I booted to DEV, mounted the .vhdx for Beta as the D: drive, then ran DISM.exe /Image:D:\ /cleanup-image /startcomponentcleanup to clean up the component store while offline.


Edit: I have just successfully done the same offline fix on the .vhdx for my Hyper-V Win11 Beta VM.

View attachment 63807

On restarting the VM it briefly showed the 'installing updates' message. A few of the (un)reclaimable packages had been removed and dism /online /cleanup-image /startcomponentcleanup now runs successfully (stopping at 20% as it always does when run on a clean component store).

View attachment 63808
Click to expand...
Hi Bree : What's the goal of Component Store cleaning?. Sorry for asking but I would like to know
 

My Computers

System One System Two

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkPad X1 3Gen Extreme
    CPU
    I7 10750H
    Motherboard
    Intel MW-490
    Memory
    32 GB
    Graphics Card(s)
    Intel UHD - NVIDIA 1650 Ti Max-Q
    Sound Card
    Realtek in-built
    Screen Resolution
    3840x2160 200% Scale
    Hard Drives
    C: WDC PC SN730 SDBQNTY-1T00-1001 (1 TB)
    D: KINGSTON SNV2S2000G (2 TB)
    Antivirus
    BitDefender Free
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Legion 7i 16IRX9
    CPU
    Intel Core i9-14900HX
    Motherboard
    LENOVO LNVNB161216 Chipset HM 770
    Memory
    32 GB
    Graphics card(s)
    Intel UHD Graphics, NVIDIA RTX 4070 Laptop
    Sound Card
    Realtek
    Screen Resolution
    3200x2000 (3.2K)
    Hard Drives
    C: HDD 1 TB SAMSUNG MZVL21T0HCLR-00BL2
    D: HDD 1 TB CRUCIAL CT1000P3PSSD8
    Antivirus
    BitDefender
Bree said:
Both my machines had .vhdx files as their C: drive, one a VM, the other a native boot .vhdx install, so it was relatively easy for me.

If you have a standard install of Beta on a PC then there is no .vhdx file for you to work on. To be able to do an offline clean up of the component store you need to boot from something else so that the installed Windows isn't running, and from which you can run DISM. Booting to a Command prompt in Advanced Startup will fit the job.

When running DISM like this you'll need to provide a scratch directory for it to use, the default Temp directory in the recovery environment is too small. The directory must already exist.

View attachment 63817

So when booted to a Command Prompt the command you'd need to use would be be something like:
DISM /Image:C:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
Click to expand...

OK, so I am running Win11Pro as C: and Win11 Insider Beta on my "G" drive -- and while these are both Pro, they are different releases.

So, if I create a Temp dir in C:, can I do the following from a command prompt in C:

Code: 
DISM /Image:G:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
 

My Computer

System One

  • OS
    Windows 11
    Computer type
    PC/Desktop
    Manufacturer/Model
    Custom built
    CPU
    Ryzen 5600X
    Motherboard
    ASRock Steel Legend
    Memory
    16GB
    Graphics Card(s)
    EVGA GT 710
    Sound Card
    None
    Monitor(s) Displays
    23",24", 19" - flat panels
    Screen Resolution
    1920x1200
    Hard Drives
    None - only M.2 SATA and NVMe drives
    PSU
    750W
    Case
    Antec
    Cooling
    stock Wraith cooler
    Keyboard
    Corsair gaming
    Mouse
    Logitech M720
    Internet Speed
    1Gb
dism /online /cleanup-image /startcomponentcleanup. Got the same error. Maybe it's a regional issue, myne is es-cl
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo ThinkPad X1 3Gen Extreme
    CPU
    I7 10750H
    Motherboard
    Intel MW-490
    Memory
    32 GB
    Graphics Card(s)
    Intel UHD - NVIDIA 1650 Ti Max-Q
    Sound Card
    Realtek in-built
    Screen Resolution
    3840x2160 200% Scale
    Hard Drives
    C: WDC PC SN730 SDBQNTY-1T00-1001 (1 TB)
    D: KINGSTON SNV2S2000G (2 TB)
    Antivirus
    BitDefender Free
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Lenovo Legion 7i 16IRX9
    CPU
    Intel Core i9-14900HX
    Motherboard
    LENOVO LNVNB161216 Chipset HM 770
    Memory
    32 GB
    Graphics card(s)
    Intel UHD Graphics, NVIDIA RTX 4070 Laptop
    Sound Card
    Realtek
    Screen Resolution
    3200x2000 (3.2K)
    Hard Drives
    C: HDD 1 TB SAMSUNG MZVL21T0HCLR-00BL2
    D: HDD 1 TB CRUCIAL CT1000P3PSSD8
    Antivirus
    BitDefender
MiguelAngel11 said:
Hi Bree : What's the goal of Component Store cleaning?. Sorry for asking but I would like to know
Click to expand...
Reducing the size of the installed Windows. There can be quite a few GB of superseded files left in the component store.

This is not just to keep the backup sizes down, on my PC with the two native boot .vhdx installs I am tight on space. A dynamically expanding .vhdx file needs enough free space to expand to its maximum allocated size while its copy of Windows is running. With my two 64GB dynamic .vhdx files on my PC's 128GB SSD, plus its own installed Win10, I need to keep the Windows in each .vhdx as clean as possible. If either one grows too large the other will BSOD at boot, saying 'VHD boot host volume not enough space'.

bsod-not-enough-space-png.25588
 
Last edited:

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Mark Phelps said:
OK, so I am running Win11Pro as C: and Win11 Insider Beta on my "G" drive -- and while these are both Pro, they are different releases.

So, if I create a Temp dir in C:, can I do the following from a command prompt in C:

Code: 
DISM /Image:G:\ /cleanup-image /startcomponentcleanup /ScratchDir:C:\Temp
Click to expand...
Yes, you can. But as you are using Dism within your running Win11 Pro on the C: drive to clean up the offline image of the Insider Beta build on your G: drive, then you don't need to provide it with a scratch directory. Windows own temp folder is more than large enough. It's only when you boot to the recovery environment that you need to provide the separate scratch directory, the virtual X: drive that WinRE runs from is too small.
 

My Computers

System One System Two

  • OS
    Windows 11 Home
    Computer type
    Laptop
    Manufacturer/Model
    Acer Aspire 3 A315-23
    CPU
    AMD Athlon Silver 3050U
    Memory
    8GB
    Graphics Card(s)
    Radeon Graphics
    Monitor(s) Displays
    laptop screen
    Screen Resolution
    1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
    Hard Drives
    1TB Samsung EVO 870 SSD
    Internet Speed
    50 Mbps
    Browser
    Edge, Firefox
    Antivirus
    Defender
    Other Info
    fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
  • Operating System
    Windows 11 Pro
    Computer type
    Laptop
    Manufacturer/Model
    Dell Latitude E4310
    CPU
    Intel® Core™ i5-520M
    Motherboard
    0T6M8G
    Memory
    8GB
    Graphics card(s)
    (integrated graphics) Intel HD Graphics
    Screen Resolution
    1366x768
    Hard Drives
    500GB Crucial MX500 SSD
    Browser
    Firefox, Edge
    Antivirus
    Defender
    Other Info
    unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.

    My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).

    My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.

    My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
I haven't been around for a bit (recovering from emergency surgery) but just started trying to check in on this stuff and when I opened Windows Update there was a Retry button, I don't recall seeing an error message or number at that time. I clicked retry and it downloaded the update and starting installing... it got somewhere past 69% (last number I saw) and it through the error below. I retried again, four times total and it claimed to download a fresh one each time, but I got the same error.

1688409905388.png

Any ideas? I haven't tested a reboot yet, I'm going to do that before I hit rety again.
 

My Computers

System One System Two

  • OS
    Windows 11 Pro β
    Computer type
    Laptop
    Manufacturer/Model
    HP Pavilion Laptop 15-eg0070wm
    CPU
    Intel® Core™ i7-1165G7
    Memory
    32 GB DDR4-3200 SDRAM
    Graphics Card(s)
    Intel® Iris® Xᵉ Graphics
    Screen Resolution
    1920x1080
    Hard Drives
    2TB PCIe® NVMe™ M.2 SSD
  • Operating System
    macOS Ventura
    Computer type
    PC/Desktop
    Manufacturer/Model
    Apple iMac 27" 5K (2017)
    CPU
    3.4 GHz Quad-Core Intel Core i5
    Memory
    40 GB 2400 MHz DDR4
    Graphics card(s)
    Radeon Pro 570 4 GB
    Monitor(s) Displays
    27" 5K, 34" UW
    Screen Resolution
    Mon 1: 5120 × 2880 Mon 2: 2560 x 1080
    Hard Drives
    32GB NVME, 1TB SSD
Archigos said:
I haven't been around for a bit (recovering from emergency surgery) but just started trying to check in on this stuff and when I opened Windows Update there was a Retry button, I don't recall seeing an error message or number at that time. I clicked retry and it downloaded the update and starting installing... it got somewhere past 69% (last number I saw) and it through the error below. I retried again, four times total and it claimed to download a fresh one each time, but I got the same error.

View attachment 63949

Any ideas? I haven't tested a reboot yet, I'm going to do that before I hit rety again.
Click to expand...

Run the Troubleshooter, then Restart your PC and see if it's resolved:
System>Troubleshoot>Other troubleshooters and click Run beside Windows Update.
 

My Computer

System One

  • OS
    Windows 11 Pro (Beta Build 22635.4870)
    Computer type
    PC/Desktop
    Manufacturer/Model
    Alienware
You must log in or register to reply here.

Similar threads

  • Article Article
Insider KB5050105 Windows 11 Insider Beta build 22635.4805 (23H2) - Jan. 24
2 3
Replies
49
Views
2K
Almighty1
Almighty1
  • Article Article
Insider KB5050085 Windows 11 Insider Beta build 22635.4800 (23H2) - Jan. 17
2
Replies
29
Views
2K
Almighty1
Almighty1
  • Article Article
Insider KB5048808 Windows 11 Insider Beta build 22635.4660 (23H2) - Jan. 3
2 3
Replies
41
Views
3K
Brink
Brink
  • Sticky
  • Article Article
Insider KB5050090 Windows 11 Insider Beta and Dev build 26120.3073 (24H2) - Jan. 31
2 3 4
Replies
77
Views
6K
fg2001gf11F
F
  • Sticky
  • Article Article
Win Update KB5050092 Windows 11 Cumulative Update Preview build 22631.4830 (23H2) - Jan. 29
Replies
10
Views
2K
antspants
antspants

Latest Support Threads

Latest Tutorials

Back
Top Bottom