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?
Something happened and we could not install a feature.
For all preview build I have installed to date (on 20298 at the moment) I have pop ups that keep appearing. I will get one that says "We are adding new features to Windows."..... then another after that says "Something happened and we could not install a feature." I have no idea what it is trying to install so no way to diagnose the issue. Also I have it promoted to domain controller, in this mode it seems that the night light cannot be enabled. I also find that the screen saver /display turn off will not always function, even when nothing should be stopping it. If I use powercfg -requests in CMD then it shows nothing is stopping the display from turning off. I have turn off display after 1min, blank screen saver after 1 min with require logon to resume. Works most of the time then may not work for other times. Strange.
VBox: Remote Management / Add Roles & Features: The WS-Management service cannot process the request
Hello, I have installed Windows Server 2019 in a VirtualBox 6.1 machine. In the Server Manager I want to activate remote management and install roles like AD DS, but these error messages appear: Local Server \ Remote Management: "The WS-Management service cannot process the request because the XML is invalid." Add Roles and Features: "The WS-Management service cannot process the request. The service in configured to not accept any remote shell requests." I have created the VirtualBox virtual machine as "Windows 2016" and tried several options like EFI, I/O APIC, PAE/NX, nested VT-x, nested paging, NAT, bridged adapter. In the Local Group Policy Editor (Windows Server virtual machine), I have manually enabled "Allow Remote Shell Access" in Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > Remote Shell and run gpupdate /force. I have also installed Windows Server in VirtualBox on two other computers, but the same problem appears. I hope anyone can help me solve this problem. What has to be configured to make the WS-Management service work correctly?