It has been RTM for a while. From here on, marketing will take over, but technically you should not expect anything spectacular to arrive. The upgrade from 2019 to 2022 is very smooth. I even tested it on Domain Controllers and works perfectly.
I had some horrors after installing it. First I couldn't DDA my intel NIC to a free-bsd vm anymore or at least the vm couldn't find the NIC. Second a vNIC set as trunk wouldn't connect to an external vSwitch. But when I set trunk-modet to all the NICs in the VM it did work. Later it worked anyways. And importing older VMs from 2019 which had something with DDA wouldn't boot at all, although the devices where assigned again.
I will give it another try at one point. The main reason I wanted to update was WSL 2, which doesn't seem to be there, so there's not much of a reason for me anymore.
@mrbbq what does wsl2 do 4u that a vm doesn't ? i understand that loadsa peeps love the integration services but thats hardly a showstopper isit ?
there are many differences, for example, wsl2 is on-demand virtual machine, it starts when needed and stops when don't needed automatically, it supports running multiple different linux distros under single running vm, also in recent insider builds it supports openGL hardware acceleration inside vm. You cannot replicate any of this in hyper-v
Hi All, I am new to this forum. Using Win Server 2022 LTSC as my daily driver on my laptop. I updated Windows Server 2022 using the Win10 x64 update given on Page 17 by Enthousiast (am NOT able to paste his post here as the forum doesnt allow it). The update was successful. But the version number is still 20348.51 and did NOT change to 20348.75 in winver. Kindly reply.
same thing happened 2 me @taylorcole next winupdate it went 2 .75 though so i wouldnt worry bout it 2 much edit: mayb try teh Update(s): in the op ?
Hi bear_aussie, Thx for the reply. I tried what you suggested, but those updates in op were shown as already installed on my laptop. Anyways, no worries. Enjoying the Server 2022.
How do windows updates get affected if we remove components from Windows Server 2022 using powershell?? I install Windows Server and do the following removals after adding the necessary roles and features (WLAN, Media Foundation and .net 3.5) 1. dism /online /get-features /format:table 2. Disable following features dism /online /disable-feature:RSAT dism /online /disable-feature:WindowsServerBackupSnapin dism /online /disable-featurerinting-XPSServices-Features dism /online /disable-feature:Microsoft-Windows-MultiPoint-Connector dism /online /disable-feature:SmbDirect dism /online /disable-feature:Xps-Foundation-Xps-Viewer dism /online /disable-feature:Windows-Defender 3. Remove all disabled features by : powershell commands Get-WindowsFeature | Where-Object {$_.Installed -match "False"} Get-WindowsFeature | Where-Object {$_.Installed -match "False"} | Uninstall-WindowsFeature -Remove -IncludeManagementTools 4.Run this in cmd for /f %a in ('dism /online /get-features /format:table ^|find "| Disabled"') do (dism /online /disable-feature:%a /remove) These commands remove the Unused/Not Installed features along with their payloads (i.e clean up the disk space used by them) So my question is will Windows Update go well after doing the above modifications for those features that are already installed and working fine??.. Has anyone tried this??
windows has always stashed away updates even 4 packages u dont have installed its why winsxs grows 2 such epic sizes after awhile
Ok I cleanup WinSxS folder REGULARLY too using the analyzecomponent and startcomponentcleanup /resetbase command after doing the above mentioned modifications. Actually I used to Ameliorate Windows (even server) and run many powershell tweaks and reduce the RAM consumption to about 700MB on Idle and reduce disk space to 12GB install including all req software. But then update capability used to go away with amelioration. So decided NOT to do any tweaks with Server 2022 except disabling (not removing) Windows Defender.
/resetbase on windows 10 by default has always avoided deletin stuff if at all possible iirc its for if a update brix ur computer & "reset this pc" (winpe-rejuv) - both of which need original files 2 roll back 2 link above shows which registryvalue 2 change 2 zero if u wanna live dangerosly
Thx soo much, I changed the registry setting and it allowed me to shave of at least 1 GB of WinSxS using resetbase.