-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Microsoft improvements for ARM64 in 24H2 #5
Comments
|
One funny thing I ran into was deploying the updated Windows Terminal stopped working. It turns out that DISM was erroring out because of the "arm" (not arm64) version of the Xaml dependency being included. I guess when they dropped support for 32-bit arm, they decided to error out instead of just ignoring an unneeded dependency package. Added a tweak to my script to delete the 32-bit arm package if on 24h2 or newer (if I knew off-hand which build dropped 32-bit arm support I could have specified a lower build number, but whatevs). |
Another "improvement" microsoft made is to updates: now a given update can list multiple msu files. When I first looked at KB5046617 on microsoft update catalog I got sticker shock at the size listed, but it turns out that was the size of both update files, and the prerequisite msu (KB5043080) was already included in the version of Windows 11 24H2 on the official iso download, so I could omit that one. |
There seems like there may be an issue with the hyperv drivers in 24H2 - the "Assigned Memory" of the VM is not going down after start like it does with 22H2/23H2. |
This isn't related to the virtual cpu. It seems to be intermittent, like there's a timing thing going on, but I've just discovered that removing |
Since winpe isn't supposed to be redistributable, I made a github workflow to demonstrate how to make a winpe iso with the virtio drivers, x64 support, and optionally lcu updates in https://github.com/jeremyd2019/winpebuilder/blob/main/.github/workflows/build.yml |
Started the process to get 24H2 virtual machines (Windows Update hasn't offered it to any of my host machines yet), and noticed a couple of improvements that should make life easier for me:
Will update as I get further along and see what happens.
The text was updated successfully, but these errors were encountered: