Games

EpicInstaller on Windows Server 2022/2025 and Windows 10/11 (error 2738)

Since Microsoft deprecated vbscript.dll in October 2023, several installations, including the Epic Installer, have encountered significant issues. Users attempting to install the Epic Installer are frequently met with the error message: “The error code is 2738”. This error is particularly frustrating as the Windows Eventlog does not provide any helpful information, making troubleshooting more challenging. The root cause of error 2738 is the system’s inability to locate vbscript.dll.

This issue stems from the deprecation of vbscript.dll, a crucial component previously used by many applications and installers. Without this DLL, scripts that rely on VBScript cannot execute, leading to installation failures. Users have reported that this error not only affects the Epic Installer but also other software that depends on VBScript for its installation process. The resolution is relatively simple and shouldn’t take more than about 5 minutes:

Hyper-V

Windows NT4 / 2000 Server and Workstation on a 2019 Hyper-V Cluster

Sometimes it’s necessary to install an old Operating System, but you really cannot (or don’t want to) get the old hardware out, even if it would still work.
I was in such a position that I had to install Windows 2000 Server. After locating the installation media, I decided it was a good idea to get it running on the 2019 Hyper-V cluster. This actually can be done, but there are a few hoops to jump through.

Update: This was written with Windows 2000 Adv. Server in mind, but I’ve since discovered the same procedure works for Windows NT4 with SP6a slipstreamed.

Hyper-V

Force Remove Host from SCVMM 2016/2019 & Hyper-V Console

To remove from SCVMM:

Open PowerShell with administrative credentials:

PS C:\> $Credential = Get-Credential
PS C:\> $VMHost = Get-SCVMHost -ComputerName “<Hostname of Server here>”
PS C:\> Remove-SCVMHost -VMHost $VMHost -Credential $Credential

The Get-Credential cmd-let will open a prompt in which you have to supply credentials with the rights to remove the host. In the second line you specify the server. This doesn’t have to be the FQDN, the Netbios name will do.
The last line actually removes the server. This may take a few minutes, depending if the server responds or not. If the server does not respond, PowerShell waits for a time-out.

To remove from a Hyper-V console:

Open PowerShell with administrative credentials:

PS C:\> Get-VM
PS C:\> Remove-VM -name [“VM Name Here”] -force

Use this to remove VMs that are in the state of SavedCritical. The “Get-VM” command will show a list of VMs registered on this Hyper-V server. The Saved-Critical VMs will list there too. Make sure the -force is added or it won’t do the trick. If your machine name has spaces, use the quotes (without the square brackets of course].

This was tested on Server 2016 and Server 2019. It’s also expected to work on later server releases.

Microsoft Server

Report on BlueScreen (BSOD) events and stop codes with PowerShell

A PowerShell script to report on all BlueScreen events and stop codes from the Windows Event Log on a specific server can be a useful tool for system administrators to troubleshoot and prevent future system crashes. This script will query the System Event log for events related to bug checks (BlueScreens) on a local server or a remote server.
Note: I wrote this to check for one server at a time. If requested, or if I have a future need, I may adapt it to query a list of servers and have the output written to a log file.

Microsoft Generic

216.146.35.35 & 216.146.36.36 added as primary to your DNS settings

With the update to their client version 5.3.1 for Windows, DynDNS sets the first to entries in your local DNS to 216.146.35.35 and 216.146.36.36. Unfortunately this causes the machine the DynDNS client is installed on to fail to contact any other server within the local network up to giving login issues over RDP if this server is domain joined and requires NLA. The reason is happens is that this update sets the option “Use Dyn Recursive DNS servers on this machine” default.
This can be disabled by opening the client, click Settings, click Preferences and uncheck “Use Dyn Recursive DNS servers on this machine”

Dyn Updater Preferences (not real IP nor account)

Once this option is unchecked, the client will stop hijacking DNS on the machine it’s installed on.

Windows 2000 Professional

Slipstreaming Service Pack 4 into Windows 2000

When installing Windows 2000 (and also Windows NT4 or Windows XP/2003 or even MS Office versions), it’s usually easier and less error-prone to install the OS with the latest service-pack or SP already slipstreamed into the installation media. Quite often this will resolve driver issues which may cause Blue Screens of Death during installation.
This guide assumes you already have a copy of the installation media and SP handy and further assumes you’re working on the D-drive. The mounted image or DVD drive is assumed to be the E-Drive. You can substitute the drive letters with whichever you’re using.

What do we need:
1) At least 1GB free space on the hard disk you’re working on
2) A CDR/CDRW drive to burn the CD or a USB Pendrive with sufficient capacity already made bootable before copying the slipstreamed image
3) A Windows 2000 installation disc or .iso image
4) A copy of Windows 2000 SP4 in the same language as the install media

From here I find it easiest to work with the command prompt. This is just a habit however and there is no real difference between working with the prompt or working with the GUI.

Mount the installation media and create a work-in-progress folder:
mkdir D:\Windows2000\i386
cd D:\Windows2000\i386

Copy the contents of the i386 directory of the installation media to the folder you just created with:
xcopy e:\i386 d:\Windows2000\i386 /e

The servicepack you downloaded, is usually an executable. You can extract this with typing the filename.exe -x, so in my case that is:
D:\SP4\w2ksp4_en.exe -x

You’ll get a popup box asking for the destination of the extracted files. I normally put these in the same directory, so I enter: D:\SP4 and click Ok.
Once this is completed, CD to the directory with the extracted files:
cd D:\SP4\i386\update

Now run the following command to update the Windows 2000 installation folder:
D:\SP4\i386\Update\Update.exe -s:D:\Windows2000
Note: There is a space between Update.exe and the -s switch, but there is no space between the -s and the destination. You don’t need to specify the i386 folder in the path here.

Once this has completed, copy the contents of the Windows2000\i386 directory to your bootable pendrive or burn it to CD/DVD.