I have been running build 20348.51 om my 2 main rigs for 2 weeks, and it's running perfectly. It's going to stay there
Sorry to disagree to some extent. First and most important, the line discussed here is part of the NT family which has its origins in VMS, which was not a Microsoft product, but developed by the same person who started the NT line at Microsoft. XP and 2003 are very closely related regardless, although at some point they diverged slightly and were released separately. The big technology changes happened from NT4 to 2000 (Active Directory), XP to Vista (CBS), 7 to 8 (less major change than previously which is a sign of maturity for the OS line, but still changed significantly enough). All intermediate versions are more like second and further editions of the previous versions. Windows 10 is Windows 8 enhanced. There was no major structural technological change from Windows 8 to Windows 8.1, 10 and their server equivalent versions. In fact to me it looks like there is more significant change from Windows 8 to Windows 8.1 than from Windows 8.1 to 10, but I don't insist because this may be personal bias. Microsoft has the focus elsewhere now, although Windows platform is still central to the new technologies.
no prob dude infact theres only 1 part dat i disagree with ur disagreement (!) not really they look teh same cos the svr2k3 team synced the userland 2 xp frequently during dev but the 2k3 kernel is pretty diffrent from xps due 2 18 mths more dev than xp - ms needed 2 make BIG changes 4 amd64 support etc (which is y xp64 is based on svr2k3: xp couldnt target amd64) its trivialy ez 2 write a driver that runs on 2k3 but not xp (prlly even ez-er than writing an xp drver that doesnt run on 2000) it was teh only time that ms made an nt kernel specificaly 4 svr use - evry ntsvr kernel (b4 & since) has been bit4bit identical 2 the client
I installed it on a vps with QEMU and RDP is awful, loosing the connection all the time or only getting a black screen. RDP is broken in this instance.
the msi yeah but it loks like @max1/xsr1 madea custom instaler on teh github wsee was 4 ws2016 neway it just (aparently) runs on 19 & 22 aswell
Anyone managed to upgrade 2016 to 2022 with desktop environment? I keep getting a message that I can't keep my files/settings/etc.
ur not booting teh installer from iso/usb/dvd or anything silly like that ? upgrades can only b done online - mount the iso and run setup.exe
does a 2019 installer do the same thing ? if it does u probably have something wrong (but often easyily fixed) with ur 2016 install if it doesnt it mite not like big jumps & u might need 2 go 2016->2019->2022 edit: & check theyre both exact same edition - u cant upgrade server standard core 2 datacentre with destop experiece 4 example
Sorry, I typed it wrong in the previous message, I'm on 2019. I guess I'll await proper RTM and try again then.