As some of you may know, I muti-boot using native boot vhdx, mostly various Insider builds. but I also have vhdx for Win10 and RTM Win11. I have three machine set up for this, my (unsupported) System Two with 24H2 as its conventional OS, System Four (unsupported) with Windows 10, and my supported System Five on 23H2 (see My Computers > Other Info for the last two). All of them got their respective cumulative updates on Patch Tuesday. Two out of the three work normally after the updates. My 23H2 system has major issues when booting to a vhdx after the update to 22631.4602.
When booted to any one of the available vhdx I have no keyboard, no touchpad, and no sound. The only way I can interact with Windows is through the touchscreen. That on its own is a major inconvenience, but not insurmountable. What is worse is that I am locked out of using anything but the built in Microsoft apps, nor am I allowed to open Windows Security. This is the case regardless of which OS I choose to boot. The only one that works normally is the conventional install of 23H2.
Attempting to open a non-Microsoft app like Firefox, or to open Windows Security is greeted with the statement that "Your organisation used App Control for Business to block this app". I repeat, this applies whichever vhdx I boot.

That is apparently part of Intune. As I only ever use a local account I cannot see how it possibly applies to me.
I must emphasise, none of this is in any way a problem in any of the vhdx OS's, they are all affected the same way. It is the main Windows 11 23H2 22631.4602 that seems to be applying the policies to any and all of the vhdx when it boots them. To confirm that I have restored a system image of its previous 22631.4460 (KB5046633) and all the vhdx are back to working normally again. In fact, I'm typing this in Firefox on the Canary build vhdx, passing the time while it installs the 27764.1000 feature update. Windows update says it's 95% installed, so I'll have to stop typing and reboot shortly....
When booted to any one of the available vhdx I have no keyboard, no touchpad, and no sound. The only way I can interact with Windows is through the touchscreen. That on its own is a major inconvenience, but not insurmountable. What is worse is that I am locked out of using anything but the built in Microsoft apps, nor am I allowed to open Windows Security. This is the case regardless of which OS I choose to boot. The only one that works normally is the conventional install of 23H2.
Attempting to open a non-Microsoft app like Firefox, or to open Windows Security is greeted with the statement that "Your organisation used App Control for Business to block this app". I repeat, this applies whichever vhdx I boot.

That is apparently part of Intune. As I only ever use a local account I cannot see how it possibly applies to me.
Intune's App Control for Business policies are part of endpoint security and use the Windows ApplicationControl CSP to manage allowed apps on Windows devices.

Manage approved apps for Windows devices with App Control for Business policy and Managed Installers in Microsoft Intune
Use App Control for Business policies and a managed installer to manage which apps are approved to run on Windows devices that you manage with Microsoft Intune.
learn.microsoft.com
I must emphasise, none of this is in any way a problem in any of the vhdx OS's, they are all affected the same way. It is the main Windows 11 23H2 22631.4602 that seems to be applying the policies to any and all of the vhdx when it boots them. To confirm that I have restored a system image of its previous 22631.4460 (KB5046633) and all the vhdx are back to working normally again. In fact, I'm typing this in Firefox on the Canary build vhdx, passing the time while it installs the 27764.1000 feature update. Windows update says it's 95% installed, so I'll have to stop typing and reboot shortly....
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.