Software Installation Checker in Batch Scripting | Check if a Program is Installed

As an IT Support Engineer or System Administrator, you may need to verify whether a particular application is installed on a computer. Instead of searching manually, you can automate this task using a simple Batch Script.

In this tutorial, we'll create a **Software Installation Checker** that checks whether **Google Chrome** is installed on a Windows computer.

Batch Script

  
@echo off

where chrome

if %errorlevel%==0 (

echo Google Chrome Installed

) else (

echo Google Chrome Not Installed

)

pause
  

How the Script Works

#Step 1: Turn Off Command Display
@echo off


This hides the commands while the script runs, making the output cleaner.


#Step 2: Search for the Software

• where chrome

The `where` command searches for the executable file (`chrome.exe`) in the system's PATH.

• * If found, Windows displays the file location.
• * If not found, the command reports that it could not find the file.

#Step 3: Check the Result Using ERRORLEVEL

• if %errorlevel%==0 (

If the `where` command successfully finds Chrome, `ERRORLEVEL` is set to **0**.

Output:

• Google Chrome Installed
• Otherwise, the script displays:
• Google Chrome Not Installed

#Step 4: Pause the Script

• pause

This keeps the Command Prompt window open so you can read the result.

Sample Output (Installed)

• C:\Program Files\Google\Chrome\Application\chrome.exe

Google Chrome Installed
Press any key to continue . . .




Sample Output (Not Installed)

INFO: Could not find files for the given pattern(s).

Google Chrome Not Installed

Press any key to continue . . .

Why Use a Software Installation Checker?

This script helps you:

• * Quickly verify software installation
• * Save troubleshooting time
• * Avoid manual searching
• * Automate routine IT tasks
• * Simplify software audits

Checking Other Applications

You can replace `chrome` with the name of another executable.

Examples:

• where notepad
• where python
• where java
• where git
• where code

This makes the script reusable for checking different software.

Real-World Uses

IT Support Engineers use similar scripts to:

* Verify required software during system setup
* Troubleshoot missing applications
* Check developer tools
* Validate software before deployment
* Perform inventory checks

Commands Used

Interview Questions

#What does the `where` command do?

• It searches for an executable file in the directories listed in the system PATH.

#What does `ERRORLEVEL` indicate?

• It stores the result of the previously executed command.

#What does `ERRORLEVEL = 0` mean?

• The command executed successfully.

#Can this script check software other than Chrome?

• Yes. Replace `chrome` with the executable name of the software you want to check.

#Why is automation useful for software verification?

• It speeds up repetitive tasks and reduces manual effort during troubleshooting and system maintenance.

Limitations

The `where` command only finds programs whose executable files are available in the system PATH. Some installed applications may not appear if their installation directory isn't included in PATH. For those cases, more advanced methods such as checking the Windows Registry or using PowerShell are often used.

Conclusion

A Software Installation Checker is a simple yet practical Batch Scripting project that automates software verification on Windows systems. By combining the `where` command with `ERRORLEVEL`, you can quickly determine whether an application is available.

This project is an excellent addition to your Batch Scripting portfolio and demonstrates a real-world automation task that is useful for IT Support Engineers, Desktop Support Engineers, and System Administrators.

IT Support Toolkit in Batch Scripting | Build Your Own Windows Troubleshooting Tool

IT Support Engineers perform many repetitive tasks every day, such as checking system information, troubleshooting network issues, opening Windows tools, and cleaning temporary files. Instead of running each command manually, you can automate these tasks using a single Batch Script.

In this tutorial, we'll build a simple **IT Support Toolkit** in Batch Scripting that displays a menu and lets you choose common troubleshooting tasks.

Batch Script

@echo off
title IT Support Toolkit
color 0A

:menu
cls
echo =====================================
echo         IT SUPPORT TOOLKIT
echo =====================================
echo.
echo 1. System Information
echo 2. Network Information
echo 3. Ping Test
echo 4. Flush DNS Cache
echo 5. Open Device Manager
echo 6. Open Task Manager
echo 7. Open Event Viewer
echo 8. Clean Temp Files
echo 9. Exit
echo.

set /p choice=Select an option (1-9): 

if "%choice%"=="1" goto systeminfo
if "%choice%"=="2" goto network
if "%choice%"=="3" goto pingtest
if "%choice%"=="4" goto flushdns
if "%choice%"=="5" goto devicemanager
if "%choice%"=="6" goto taskmanager
if "%choice%"=="7" goto eventviewer
if "%choice%"=="8" goto cleantemp
if "%choice%"=="9" exit

echo Invalid choice!
pause
goto menu

:systeminfo
systeminfo
pause
goto menu

:network
ipconfig
pause
goto menu

:pingtest
ping google.com
pause
goto menu

:flushdns
ipconfig /flushdns
pause
goto menu

:devicemanager
start devmgmt.msc
goto menu

:taskmanager
start taskmgr
goto menu

:eventviewer
start eventvwr.msc
goto menu

:cleantemp
del /q /f /s "%temp%\*.*"
echo Temporary files cleaned successfully.
pause
goto menu

How the Script Works

Step 1: Display the Main Menu

The script starts by displaying a menu with different troubleshooting options.

• 1. System Information
• 2. Network Information
• 3. Ping Test
• 4. Flush DNS Cache
• 5. Open Device Manager
• 6. Open Task Manager
• 7. Open Event Viewer
• 8. Clean Temp Files
• 9. Exit

The user enters a number to choose the required task.


Step 2: Read User Input

• set /p choice=Select an option (1-9):

The selected option is stored in the variable `choice`.


Step 3: Execute the Selected Task

The script uses IF statements to jump to the appropriate section.

Example:

if "%choice%"=="1" goto systeminfo
If the user enters **1**, the script displays detailed system information.

Features Included

1. System Information

• systeminfo

Displays:

• * Windows version
• * Computer name
• * BIOS information
• * Installed memory
• * System boot time

2. Network Information

• ipconfig

Shows:

• * IP Address
• * Default Gateway
• * Subnet Mask
• * Network Adapter Details

3. Internet Connectivity Test

• ping google.com

Checks whether the computer can reach the internet.


4. Flush DNS Cache

• ipconfig /flushdns

Clears the local DNS cache, which can help resolve certain website or name resolution issues.



5. Open Device Manager

• start devmgmt.msc

Launches Windows Device Manager.


6. Open Task Manager

• start taskmgr

Opens Task Manager to view running processes and system performance.



7. Open Event Viewer

• start eventvwr.msc

Launches Event Viewer to review Windows logs and errors.


8. Clean Temporary Files

• del /q /f /s "%temp%\*.*"

Deletes temporary files from the current user's Temp folder.

Why Build an IT Support Toolkit?

Creating a toolkit provides several benefits:

• * Saves time during troubleshooting
• * Combines multiple utilities into one script
• * Reduces repetitive work
• * Improves productivity
• * Makes common administrative tasks easily accessible

Real-World Uses

IT Support Engineers and System Administrators use similar toolkits to:

• * Diagnose user issues
• * Collect system information
• * Check network connectivity
• * Troubleshoot Windows problems
• * Perform routine maintenance
• * Speed up daily support tasks

Interview Questions

What is an IT Support Toolkit?

• It is a collection of scripts or tools that automate common troubleshooting and administrative tasks.

Which command displays system information?

• systeminfo

Which command checks internet connectivity?

• ping

What does `ipconfig /flushdns` do?

• It clears the DNS resolver cache stored on the local computer.

Why should IT professionals automate repetitive tasks?

• Automation improves efficiency, reduces manual effort, and minimizes the chance of human error.

Conclusion

An IT Support Toolkit is one of the most practical Batch Scripting projects for beginners. It combines multiple Windows commands into a single, menu-driven application that simplifies troubleshooting and routine maintenance.

If you're preparing for roles such as **IT Support Engineer**, **Desktop Support Engineer**, **Help Desk Engineer**, or **System Engineer**, this project demonstrates your understanding of Windows administration and automation. It's also an excellent addition to your GitHub repository and technical portfolio.

Auto Temp File Cleaner in Batch Scripting | Delete Temporary Files Automatically

Over time, Windows stores temporary files that can consume disk space and sometimes affect system performance. While these files are generally safe to remove, deleting them manually can be time-consuming.

With Batch Scripting, you can automate this task using just a few commands. In this tutorial, we'll create a simple Auto Temp File Cleaner that deletes files from the current user's temporary folder.

  
@echo off

echo Cleaning Temp folder...

del /q /f /s "%temp%\*.*"

echo.

echo Temp folder cleaned successfully.

pause
  

Login Timestamp Error or Bad Timestamp Error (40105) on a Company Laptop 

One of our users reported that their company laptop displayed a Login Timestamp Error (also known as Bad Timestamp Error 40105) while attempting to sign in.

In most enterprise environments, this error occurs because the laptop's date and time are not synchronized with the organization's authentication server.


This commonly happens when:

• The laptop has been disconnected from the company network for several days.
• The device has not connected to the corporate VPN.
• The BIOS date and time are incorrect.
• Windows Time service is not running.

Fortunately, this issue can usually be resolved within a few minutes.

Table of Contents

1. What is Login Timestamp Error (40105)?
2. Why Does This Error Occur?
3. Solution 1: Restart Windows Time Service
4. Solution 2: Correct Date & Time from BIOS
5. How Windows Time Synchronization Works
6. Additional Troubleshooting
7. Frequently Asked Questions
8. Conclusion

What is Login Timestamp Error (40105)?

The Login Timestamp Error (40105) is an authentication error that occurs when the system time on your laptop differs significantly from the company's authentication server. Error 40105

Most organizations use technologies such as Active Directory, Kerberos Authentication, or Single Sign-On (SSO), which rely on accurate timestamps to validate login requests.

If the time difference exceeds the allowed limit, authentication fails.

Why Does This Error Occur?

The company's authentication server verifies your computer's system time before allowing access.

If your laptop clock is incorrect, Windows sends an invalid timestamp during authentication, causing the login request to fail. Windows Time Service


Common causes include:

• Incorrect BIOS date and time
• Windows Time service stopped
• Laptop disconnected from VPN for a long period
• CMOS battery issue
• Failed time synchronization with the domain controller

Quick Fix 1: Restart Windows Time Service

If you're able to sign in to Windows, restart the Windows Time service.

Steps

• Press Win + R
• Type services.msc
• Press Enter
• Locate Windows Time
• Right-click it
• Select Restart

If the service is stopped, click Start.
This forces Windows to begin time synchronization again.
Tip: You can also restart the service from Command Prompt (Run as Administrator):

• net stop w32time
• net start w32time

Quick Fix 2: Correct the Date and Time from BIOS (UEFI)

If Windows displays an incorrect time before connecting to the network, verify the BIOS clock. Login Timestamp Error 40105

Steps

Restart the laptop.
Enter BIOS/UEFI (usually F2, F10, F12, Delete, or Esc).
Navigate to Date & Time.
Update the correct date and time.
Press F10 to save.
Restart Windows.

Note: BIOS only stores the hardware clock. It does not synchronize with internet time servers.

How Windows Time Synchronization Works

After Windows starts and the device has network connectivity, it synchronizes the system clock using Network Time Protocol (NTP). Bad Timestamp Error

Key Information:

If the device cannot communicate with the domain controller or NTP server, the system time may become inaccurate.Login Timestamp Error Domain Login Error

Additional Troubleshooting

If the issue still exists, try the following:

• ✅ Connect the laptop to the company VPN.
• ✅ Restart the computer.
• ✅ Ensure Windows Time service is running.
• ✅ Verify the correct Time Zone.
• ✅ Check if the CMOS battery is weak (time resets after every shutdown).
• ✅ Run Windows Update.
• ✅ Contact your IT administrator if the device belongs to a corporate domain.

Frequently Asked Questions (FAQ)

What causes Login Timestamp Error (40105)?
The most common cause is an incorrect system date and time.

Can a VPN connection fix this issue?
Yes. Once connected to the corporate VPN, Windows may synchronize the system time with the company's domain controller.

Does changing BIOS time permanently fix the issue?
It fixes the hardware clock, but Windows still synchronizes time using the Windows Time service after startup.

Which protocol is used for Windows time synchronization?
Windows uses Network Time Protocol (NTP) over UDP Port 123.

Can a dead CMOS battery cause this error?
Yes. If the CMOS battery is weak, the BIOS clock may reset after every shutdown, causing repeated timestamp errors.

Conclusion

The Login Timestamp Error (40105) is usually caused by an incorrect system clock rather than a problem with your user account.

In most cases, restarting the Windows Time service or correcting the BIOS date and time resolves the issue. Once the laptop synchronizes with the company's authentication server, users should be able to sign in successfully.

If the problem continues, connect the laptop to the corporate VPN or contact your organization's IT support team for further assistance.

Related Articles

• How to Fix "A Trust Relationship Between This Workstation and the Primary Domain Failed"
• Common RDP Connection Issues and Their Solutions
• Windows Time Service Not Running – Complete Fix Guide
• Active Directory Authentication Troubleshooting
• How to Join a Windows Computer to a Domain
• How to Fix Windows Time Synchronization Failed