Insider KB5028247 Windows 11 Insider Beta 22621.2048 and 22631.2048 - July 13


UPDATE 7/21:


 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 22631.2048 = New features rolling out.
  • Build 22621.2048 = 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.xxxx) can check for updates and choose to install the update that will have features rolling out (Build 22631.xxxx).

What’s new in Build 22631.2048

Gallery in File Explorer

We are introducing Gallery, a new feature in File Explorer designed to make it easy to access your photo collection. The set of content shown in Gallery is the same as what you’ll see in the All Photos view in the Photos app.


Gallery in File Explorer.
Gallery in File Explorer.

Gallery is optimized for accessing your most recently taken photos. If you have OneDrive Camera Roll Backup set up on your phone, photos you take will show up automatically at the top of the view. You can choose which folders are shown in Gallery through the Collection dropdown. You can also add subfolders of existing sources to filter to a subset of your content, such as desktop backgrounds and SD card/camera imports.

Gallery also works from the file picking dialog, bringing that same ease of use to situations such as inserting attachments, building a PowerPoint deck, or crafting social media posts.

Gallery in the file picking dialog.
Gallery in the file picking dialog.

There is also a new button in the Command Bar titled “Add Phone Photos” that will help with setting up your PC to be ready to show these photos in Gallery. Clicking this button today will open a URL with a QR code that you can scan with your phone to get started.

Add Phone Photos option on the command bar in File Explorer.
Add Phone Photos option on the command bar in File Explorer.

FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Files, Folders, and Online Storage > File Explorer.

Changes and Improvements in Build 22631.2048

[General]

  • Windows Insiders on Build 22631 will see the versioning updated under Settings > System > About (and winver) to version 23H2. This denotes that Windows 11, version 23H2 will be this year’s annual feature update which will be delivered to customers similar to the most recent Windows 10 feature updates. As mentioned here, Windows 11 will have an annual feature update cadence that releases in the second half of the calendar year. For more information, see this blog post here.

[Taskbar & System Tray]

  • After updating to this build, the ability to end task when right-clicking an app on the taskbar may appear, however this feature currently does not work correctly and will be fixed in a future flight in the Beta Channel. The setting for it under Settings > System > For developers also currently does not show.

[File Explorer]

  • We have added the ability to tear out and merge tabs in File Explorer.

[For Developers]

  • We are moving the “For Developers” settings page from Settings > Privacy & security to now be under Settings > System.

Fixes in Build 22631.2048

[Taskbar]

  • Fixed an issue which could cause the taskbar to hang during initialization and not complete loading.

[File Explorer]

  • Fixed an issue which could lead to explorer.exe crashes when opening a folder containing .WEBP files.
  • Did some work to help address an issue where File Explorer might hang when browsing network shares.

[Notification]

  • Fixed an issue where you might unexpectedly see a suggestion to turn off notifications that you regularly interacted with.

Microsoft Store Update

Windows Insiders in all channels running version 22306.1401.x.x of the Microsoft Store and higher will see the following improvements rolling out:

More pricing information: To help you with your purchase decisions, you’ll now see information about the lowest price products have dropped to in the past 30 days.

Introducing AI Hub: Explore a new curated section in the Microsoft Store where we will promote the best AI experiences built by the developer community and Microsoft. This is a space where we will educate customers on how to start and expand their AI journey, inspiring them to use AI in everyday ways to boost productivity, spark creativity and so much more.

AI Hub in the Microsoft Store.
AI Hub in the Microsoft Store.

FEEDBACK: Please file feedback in Feedback Hub (WIN + F) under Microsoft Store.

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:



Check Windows Updates


UUP Dump:

64-bit ISO download:

ARM64 ISO download:

 
Last edited:
Good to know. I've been blithely ignoring them as well -- mostly because I've not been able to *do* anything about them. LOL! Thanks for confirming my philosophy of "If it doesn't hurt, it's probably not too serious." =Ed=
I'm sure it's not doing any harm, but I got fed up with seeing a dozen (un)reclaimable packages in my Beta VM. I thought I'd try an in-place repair upgrade with an ISO for 22621.2262 that I had to hand. Seems to have worked.....

1693532428771.png

...though it looks like I'll now have to apply the enablement package to bump it back up to 22631 again.

.........

Edit: darn it, after applying the enablement package they're back again!
 
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.
The MR trick worked to complete a component store cleanup BUT ... my install of this version still shows 13 spurious reclaimable packages, to wit:
View attachment 66550
Anybody ever seen anything like this before? Totally bizarre! I'm thinking it may be time to visit UUPdump.net, grab an ISO for Build 2115 and do an in-place repair install. Thoughts?
--Ed--
Yes, I've seen this on all my Beta builds. It's been like that for a long time. My working assumption is that they were packages that were part of the flurry of 22621/22622/22623/22624 enablement builds my machine has been through, now removed but somehow still listed as being in the component store.

They appear to do no harm
Good to know. I've been blithely ignoring them as well -- mostly because I've not been able to *do* anything about them. LOL! Thanks for confirming my philosophy of "If it doesn't hurt, it's probably not too serious." =Ed=
I finally got fed up with seeing these '13 (un)reclaimable packages' in Dism and decided to try and do something about them. Now that Beta has the option to Repair Install Windows 11 via Windows Update I thought I'd try that. Seems to have done the trick....

Before....

Screenshot 2024-01-15 172142.png

After....

Screenshot 2024-01-15 190102.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.
Back
Top Bottom