Settings app not available after 25099
I installed vNext 25099 over Windows Server 2022 in a VMWare virtual machine (no other programs installed). As soon as it's installed, the Settings app is unable to launch - clicking it in the\ Start menu will bring a progress bar underneath as though the app is not installed. Tried to run this in PowerShell (like in Windows 10) to reset the Settings app: Get-AppxPackage windows.immersivecontrolpanel | Reset-AppxPackage Also tried this as recommended by some other website: Get-AppXPackage | foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"} Neither of these helped. Settings still will not open.Where can I download older Server Insider builds?
Since 25083 doesn't seem to work (and I can't perform an in-place upgrade, it goes through the wizard and then fails straight away - tried it on a bare metal server as well as a VM) I'd like to try an older build. Is there a place where I can download an older build?
In-place upgrade versus optional features
The second build of Windows Server vNext (based on Windows 11) came with an iso with installable optional features, via Dism. I plan to use in-place upgrade from build to build, not perform fresh installs on my test machine every time. I wonder if in-place upgrade shall be, practicly, blocked, if any of the optional features is installed, due to incompatibility between the installed optional features, on file/feature version number. Perhaps upgrade is possible, but optional features shall be uninstalled then, or kept, but needed to be reinstalled via Dism from new sources?Issue to build 20344
After downloading the build 20344: 1) The iso could be burned into a DVD, it was slightly too long. This may not be a bug. 2) Thet datacenter key, used in previous build, does not work. 3) In-place upgrade from one build to the other refuses. Perhaps we should wait for the next week build.In-place build upgrade failure and workaround
I have noticed that, since the first build the new Microsoft Edge was bundled with Windows Server vNext, I could not upgrade from one weekly build to the next without re-installing from scratch. I could upgrade from an older build that did not include Edge to a newer one that did, but not from one with Edge to anther with Edge. I tought that Edge was the culprit, but I could not uninstall it through the regular means, for I have wound a guide to forcly uninstall it via command line. It was uninstalled, but Windows upgrade to the new build failed again. Then, I tought that enabling Network Sharing was the culprit. So, did a fresh install once again, but kept it disabled, as out of the box. The latest build came, it failed in-place upgrade, but at an earlier stage. Yet, Edge was updated after the fresh installation a few days ago and it was removable through Control Panel or Settings. So I did uninstall it, then tried an in-place upgrade and it worked. It had reinstalled Edge. So, I guess the update/upgrade system for the Chromium Edge between Windows builds (that upgrade like previous redstones, through a Windows re-install mechanism with documents, settings and programs being kept) it is not fully developed. Edge updates on a different way then the OS itself, in a way enherited from the Chromium browser, it is not fully integrated into Windows yet, altough I have looked via 7zip and the Windows Install.wim file contains it. Probably, due to that, especially when the installed version of the Chromium Edge browser is updated beyong what is in the install.wim, issues can appear. I guess that, if the update/upgrade mechanism for Edge in Windows it is not solved, that Edge should not be bundled with Windows until that, while still being available for users via the Microsoft Edge msi installer for Enterprise. A workaround, so far, seems to be uninstalling it before an in-place build upgrade..
