Forum Replies Created
-
Posts
-
P.S.
If you in-place update from one weekly build to another, in order to avoid doing all the steps again, re-installing the software etc or whatever reason, instead of a clean install, you need to make again some steps. The Windows Audio and Windows Audio Endpoint need to be re-set on Automatic startup, DEP needs to be re-set on essential components, instead of the whole Windows, Memory Compression and the rest of the MM Agents regarding Superfetch need to be re-enabled, and disk performance in Task Manager needs to be re-enabled in Command Prompt via diskperf -y, on the build-in Administrator account. This issue was present, more or less, even on the current Windows Server 2019, when it was in beta (insider) stage and you could update one build to the next in the same way.The primary OS I use for several years on my desktop it is not a Windows one. Windows Server is installed on a laptop, that is my secondary machine. WS 2019 it is still worth it, W 10 October 2018 update (Redstone 5) does not. I use W 10 Redstone 4 at work, Firefox and Edge. I do not like this combination. I prefer WS in general because it resembles the old Windows, from before Windows 8, that I was used to and had for years. In this way, I keep the progress on Windows, but staying in the good old days. LTSC editions of Windows 10 and especially Windows Server 2016 and Windows Server 2019 are keeping alive, more or less, thoose good old days. For me, only Windows Server for personal use, as long as I shall still keep Windows, standard Windows is dumped for good for some time. I would like to be like it almost did not exist anymore.
Regarding DirectX, something I need to mention. Deactivation of DirectX 12 when installing video and/or audio drivers happens only older machines, thoose that are one year old, or two, probably it will not happen. It is not a bug, it is a feature from Microsoft, they consider older machines not being able to handle efficiently DirectX software. So, consumers/users have a choice, either to have a better performance, giving up the newer software written in DirectX 12 by installing the drivers, or they can have less performance, but remain capable of running the latest software. Indeed, if a hardware manufacturer releases updated drivers for W10 RS5, deactivation of DirectX 12 might be avoided, but I have not got the chance to test this. If someone has a machine that it is not very new, but that has W 10 recent drivers, he or she can give it a try. Just type dxdiag into Run or into Command Prompt and check the DirextX status.
Anyway, I suggest enabling all APIs available, even the lagacy ones, all the lagacy .Net Framework, not just the lagacy DirectX (via DirectPlay role). Some software may not work. Even Windows Identity Foundation and all ASP and ASP Net features. As I said, it is vital to enable them via Server Manager, before any attempt to get the rest of DirectX. Otherwise, issues may appear, software may not work, crash, and even Windows Update can, in some extreme cases, make the OS unbootable. Older DirectX installers, either official from Microsoft or not, they do not „know” out Windows 10 exists and its differences from the Windows versions they know and that is the source for the potential issues.
Oh, another issue. Media Foundation, part of Desktop Experience in previous builds, it is a separate role and it is not enabled by default. In order to get multimedia (music and video) to work properly, you need to enable it.
WSL (Windows Subsystems for Linux) is available as a role in Server Manager. As I said, I have not tested it yet. Documentation from Microsoft seems scarce for now on it.Audio works on the latest builds. Audio services needs to be re-enabled if upgrade from one build to another, not clean install. A certain build had an issue with audio service, but it was fixed.
I have found a way to force file associations. I use MuPDF for pdf, that needs manual file association. I have chosen „Open with”, then browsed to the MuPDF exe and selected „always open with”.
Regarding Edge; I do not know. I do not plan to get Edge or Windows Store.
I have an Atheros network adapter, works fine. Broadcom Wifi as well.
DirectX can be partially enabled via enabling DirectPlay. Probably the rest of legacy DirectX can be installed via DirectX WebInstaller, after enabling DirectPlay (not the offline installer, that shall overwrite newer DirectX). Important note about DirectX 12 in any type of Windows 10, including WS 2016 and WS 2019: Installing the graphics and/or audio drivers can lead to disabling DirextX 12 and being replaced with an older DirectX. This can cause issues with new software.
WSL is instalable, I have not tested it yet.
It is, for now, less stable then previous betas of Windows Server. We shall see the RTM, I hope it would be more stable and less buggy.Language features fail to install. File associations can not be made manualy, only via Settings (Immersive Control Panel). Settings itself crashes. I can not say for sure that WS 2019 is less bloated then WS 2016. It seems, very much, an updated WS 2016. Like W10 RS5 is an update to W10 RS1.
WS 2019 seems less bloated and less stuffed with spyware then W10 RS 5, as WS 2016 was less bloated and less stuffed with spyware then W10 RS1. Desktop Experience, although enabled by default on Server a GUI, has some components moved out into other places. The requirement of enabling Fax Server to get printing to work properly (this was the case in WS 2016 as well) and not including this into Desktop Experience causes some issues.
What audio editing software do you use? Pro Tools? Fruity Loops?
