After installing Windows Update KB5031419 on a Windows Server 2019 AD Controller, you are no longer able to log in remotely. To fix this, uninstall the Windows Update ..read more

If your computer has automatically rebooted and has this in the eventlog: The computer has rebooted from a bugcheck. The bugcheck was: (0x0000…). A dump was saved in: C:\Windows\MEMORY.DMP. Report Id: (GUID) Then it’s most likely caused by a BSOD from a driver issue. To troubleshoot this: Click the Start Menu and type verifier, right click the Verifier program and click Run as Administrator; Select Create custom settings (for code developers) and click Next; Select everything except Randomized low resources simulation and DDI compliance checking; Select Select driver names from a list and clic ..read more

When trying to update Windows Server 2019, I was getting this error: We couldn’t connect to the update service I’ll give you the steps I did to fix it. First I tried running the usual fix for Windows Update that you find on the internet, with no luck, which was to rename the SoftwareDistribution folder, thusly with this elevated command prompt command: net stop wuauserv net stop cryptSvc net stop bits net stop msiserver Ren C:\Windows\SoftwareDistribution SoftwareDistribution.old Ren C:\Windows\System32\catroot2 Catroot2.old net start wuauserv net start cryptSvc net start bits net start msi ..read more

When performing an inline upgrade to Windows Server 2019 on a VMware VM, the VM may hang, just showing a Windows icon in the center of the screen. This is because the VMware Hardware Version isn’t supported in Windows Server 2019. To fix this, shut down the VM, right click the VM and click Manage, then click Hardware Version and change the hardware version to the latest one (I know that 16.2 certainly supports Windows 2019, but don’t know what the minimum hardware version is for Windows Server 2019 – perhaps this can be found by creating a new VM and specifying the Win 2029 OS and seeing what ..read more

After installing KB5022733 & KB5022899, I am unable to remotely log on to my server running Server 2019 via RDP (Remote Desktop). Uninstalling KB5022733 & KB5022899 and rebooting fixes the problem ..read more

After installing KB5022352, I am unable to remotely log on to my server running Server 2019 via RDP (Remote Desktop). Uninstalling KB5022352 and rebooting fixes the problem ..read more

Beware: even though Microsoft says that WSUS needs a minimum of 2GB extra RAM, you won’t be able to use WSUS with just 2GB of extra RAM. Whilst WSUS may have only required 2GB of RAM when they developed it and with the database stored on a different server, you are going to have a practically unusable WSUS installation by the time it’s downloaded all the updates and has a few computers connecting to it, especially if it’s storing the database locally. So what are the real hardware requirements for WSUS? Well, I’m currently running a small computer network (less than 100 computers) and I’ve ins ..read more

When trying to mount (open) an ISO file you may get this error: Couldn’t Mount File Sorry, there was a problem mounting the file This is probably because the ISO file is stored on a network drive which isn’t mapped under the administrative login. When you try to mount the file, Windows elevates to the Administrator login, at which point it can’t find the file because the drive mapping isn’t there. In this case, to fix the error, copy the ISO file to a folder on the local drive and try to mount the file. You can also get a problem mounting the ISO file if: the file is corrupt, the file is alr ..read more

When trying to install KB5001638, I get this error: 2021-03 Cumulative Update for Windows Server 2019 (1809) for x64-based Systems (KB5001638) – Error 0x80070541 Does anyone know anything about that ..read more

When trying to activate Server 2019, you may get this error: The product key you entered didn’t work. Check the product key and try again, or enter a different one. (0x80070490) This isn’t Windows Server 2019 Activation problem, it’s just a bug entering the product key. To workaround this bug and activate windows, open a command prompt window in elevated mode (right click -> Run as Administrator) and enter the following command with your product key instead of the XXX’s: cscript c:\windows\system32\slmgr.vbs /ipk XXX-XXX-XXX-XXX You should then be able to activate Server 2019 without th ..read more