PC Health Check Script in Batch Scripting | Monitor Your Windows System

Monitoring your computer's health is an important task for every IT Support Engineer and System Administrator. Instead of checking system details manually, you can automate the process using a simple Batch Script.

In this tutorial, we'll create a PC Health Check Script that displays useful system information such as the computer name, current user, operating system details, CPU information, and installed memory.

Batch Script

  @echo off

echo ===== PC HEALTH REPORT =====

echo

hostname

echo

whoami

echo

systeminfo

echo

wmic cpu get name

echo.

wmic memorychip get capacity

pause

  

How the Script Works

Step 1: Display the Report Title

echo ===== PC HEALTH REPORT =====

This displays a heading so the output is easy to identify.



Step 2: Display the Computer Name

• hostname

This command shows the name of the computer.

Example Output

DESKTOP-ABCD123




Step 3: Display the Current Logged-in User

• whoami

Example Output

• systeminfo

• * Windows Version
• * OS Build
• * System Manufacturer
• * BIOS Version
• * Total Physical Memory
• * System Boot Time
• * Installed Hotfixes

Step 5: Display CPU Information

wmic cpu get name

This command displays the processor model.

Example Output

Intel(R) Core(TM) i5-1135G7 CPU



Step 6: Display Installed RAM

wmic memorychip get capacity
This command shows the capacity of each installed RAM module in bytes.



Example Output

• 8589934592
• 8589934592

Sample Output

• Computer Name
• Current User
• Windows Information
• CPU Information
• Memory Information
• Press any key to continue...

Real-World Uses

• * Verify computer specifications
• * Collect diagnostic information
• * Troubleshoot user issues
• * Prepare systems before upgrades
• * Generate system reports during maintenance

Commands Used

Interview Questions

What does the hostname command do?

• It displays the computer name.

What information does systeminfo provide?

• It displays operating system, hardware, memory, BIOS, and other system details.

What is the purpose of whoami?

• It shows the currently logged-in user.

Which command displays CPU information?

• wmic cpu get name

Why is a PC Health Check Script useful?

• It automates system diagnostics and quickly gathers important information for troubleshooting.

Note

The wmic command is deprecated on newer versions of Windows and may not be available on future releases. On modern Windows systems, PowerShell is the recommended tool for retrieving hardware information. However, wmic is still commonly found on many Windows 10 and Windows 11 installations, making it useful for learning Batch Scripting.

Conclusion

A PC Health Check Script is a practical Batch Scripting project that combines several built-in Windows commands into a single diagnostic tool. It helps IT professionals quickly collect system information and simplifies troubleshooting.

If you're preparing for a career in IT Support, System Administration, or System Engineering, this project is a great addition to your Batch Scripting portfolio and demonstrates your ability to automate routine system checks.
 

Windows Backup Script in Batch Scripting | Automatically Backup Your Files

Creating regular backups is one of the best ways to protect important files from accidental deletion, hardware failure, or system issues. Instead of manually copying files every time, you can automate the process using a simple Batch Script.

In this tutorial, we'll create a Windows Backup Script that automatically copies the Documents folder to a backup location.

Batch Script

@echo off

set BackupFolder=C:\

Backup if not exist "%BackupFolder%" (

mkdir "%BackupFolder%"

)

xcopy "%USERPROFILE%\Documents" "%BackupFolder%\Documents" /E /I /Y

echo Backup Completed Successfully.
pause

How the Script Works

Step 1: Turn Off Command Display

@echo off

This hides the commands while the script is running, making the output easier to read.


Step 2: Set the Backup Folder

set BackupFolder=C:\Backup

This creates a variable named BackupFolder and stores the destination path where the backup will be saved.


Step 3: Check Whether the Folder Exists

The script checks if the backup folder already exists.

• If it exists, the script continues.
• If it doesn't exist, a new folder named Backup is created automatically.

Step 4: Copy the Documents Folder

xcopy "%USERPROFILE%\Documents" "%BackupFolder%\Documents" /E /I /Y

The xcopy command copies the contents of the Documents folder to the backup location.

XCOPY Options

 The %USERPROFILE% environment variable automatically points to the current user's profile folder.

Step 5: Display Success Message

echo Backup Completed Successfully.
This lets the user know that the backup process has finished.


Step 6: Pause the Window

pause
Keeps the Command Prompt window open until a key is pressed.

Sample Output

Backup Completed Successfully.

Press any key to continue . . .

Why Use a Windows Backup Script?

Automating backups offers several benefits:

• Saves time
• Protects important files
• Reduces manual work
• Creates a consistent backup routine
• Improves data safety

Real-World Uses

System Engineers and IT Support Engineers often use backup scripts to:

• Backup user documents before system upgrades
• Protect important company files
• Create scheduled backups
• Prepare systems before maintenance
• Copy project files to a secure location

Tips

Change the backup location if needed. For example:

D:\Backup

or

E:\OfficeBackup

You can also replace the Documents folder with other folders such as:

• Desktop
• Downloads
• Pictures
• Project folders

Interview Questions

What is the purpose of the xcopy command?

• It copies files and folders from one location to another.

What does %USERPROFILE% represent?

• It is an environment variable that points to the current user's profile directory.

Why is if not exist used?

• It checks whether a folder exists before creating it.

What does the /Y option do in xcopy?

• It overwrites existing files without prompting for confirmation.

Why should System Engineers automate backups?

• Automation saves time, reduces human error, and ensures important files are backed up consistently.

Conclusion

A Windows Backup Script is a simple yet practical Batch Scripting project that automates one of the most important maintenance tasks—backing up files. By using commands like if not exist, mkdir, and xcopy, you can quickly create reliable backup scripts for personal or professional use.

If you're learning Batch Scripting for a career in IT Support or System Engineering, this is an excellent project to practice and include in your 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

Login Timestamp Error or Bad Timestamp Error on a Company Laptop

One user's company laptop was showing a Login Timestamp Error or Bad Timestamp Error (40105) while trying to log in.
This type of error usually occurs because your computer's date and time are out of sync with the company's security server.
It commonly happens when the laptop has been disconnected from the company network or VPN for a long time.

Why Does This Error Occur?

The company's authentication servers verify your system time before allowing access.

If your laptop's clock is incorrect, the authentication request may fail and display a Bad Timestamp or Timestamp Error (40105).

Quick Fix 1: Restart the Windows Time Service

If you're able to log in to Windows, follow these steps:

• Press Win + R, type services.msc, and press Enter.
• Locate Windows Time.
• Right-click it and select Start or Restart.

This will restart the Windows Time service and may synchronize the system clock.

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

If Windows time is incorrect and you cannot sync it, you can manually update the date and time from the BIOS.

Steps:

• Restart your computer and enter the BIOS/UEFI by pressing the manufacturer-specific key (usually F2, F10, F12, Esc, or Del).
• Navigate to the Main, System Configuration, or Miscellaneous Settings section.
• Locate Date & Time.
• Update the correct date and time.
• Press F10 to save the changes and restart the laptop.

Note: Most BIOS/UEFI firmware allows you to set the date and time manually, but it does not automatically synchronize with internet time servers.

How Time Synchronization Actually Works

The actual time synchronization happens inside the Windows operating system, not in the BIOS.

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

NTP uses UDP Port 123 for both client requests and server responses, making it the standard protocol for time synchronization across networks.

Conclusion

A Login Timestamp Error or Bad Timestamp Error (40105) is usually caused by an incorrect system clock rather than an account issue.

In most cases, restarting the Windows Time service or correcting the BIOS date and time resolves the problem. Once the system time matches the company's authentication server, the user should be able to log in successfully.

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 – Fix Guide
• Active Directory Authentication Troubleshooting

How to Fix Copy-Paste Not Working in Remote Desktop (RDP)

  
One user reported that while using Remote Desktop (RDP), they were unable to copy files or text from their local desktop to the remote desktop.

After investigating the issue, I identified that the most likely cause was clipboard redirection being disabled or the RDP clipboard process not responding.

Method 1: Restart the RDP Clipboard Process

The first troubleshooting step was to restart the rdpclip.exe process.

Steps:

Open Task Manager.
Locate rdpclip.exe (or RDP Clipboard Monitor).
Right-click the process and select End Task.
Press Win + R.
Type:
rdpclip.exe
Press Enter to restart the clipboard process.

Method 2: Verify Clipboard Redirection Is Enabled

Next, I verified that clipboard sharing was enabled in the Remote Desktop settings.

Steps:

• Open Remote Desktop Connection.
• Click Show Options.
• Go to the Local Resources tab.
• Under Local devices and resources, ensure that Clipboard is checked.
• Reconnect to the remote session.

Solution Provided

The copy-paste issue in the Remote Desktop session was resolved by:

Restarting the rdpclip.exe process.

Verifying that Clipboard Redirection was enabled in the Remote Desktop Connection settings.
After applying these steps, the user confirmed that copy and paste functionality was working normally again.

Conclusion

If copy-paste suddenly stops working in a Remote Desktop session, the issue is often caused by a stuck rdpclip.exe process or disabled clipboard redirection. Restarting the clipboard process and verifying the Remote Desktop settings usually resolves the problem within a few minutes.

Related Articles

• How to Fix "A Trust Relationship Between This Workstation and the Primary Domain Failed"
• Login Timestamp Error on Company Laptop – Quick Fix
• Common Remote Desktop (RDP) Connection Issues and Solutions
• How to Enable Clipboard Redirection in Remote Desktop

How to Fix "A Trust Relationship Between This Workstation and the Primary Domain Failed" in Windows (Complete Guide)

Learn how to fix "A Trust Relationship Between This Workstation and the Primary Domain Failed" using PowerShell, Active Directory, and domain rejoin methods.

This issue prevents domain users from logging into their computers even though their passwords are correct.

The good news is that the problem is usually not related to the user's password. Instead, it happens because the computer itself can no longer authenticate with the domain controller. 

In this guide, you'll learn:

• What this error means
• Why it happens
• What a secure channel is
• How computer passwords work in Active Directory
• Multiple ways to fix the problem
• Best practices to prevent it in the future

What Does This Error Mean?

That computer account behaves much like a user account.

Instead of logging in with a username and password, the computer authenticates itself using a secret machine password, also called the computer account password.

When Windows starts, the workstation silently proves its identity to the Domain Controller using this password.

If both passwords match, authentication succeeds.

If they don't match, Windows displays:

A Trust Relationship Between This Workstation and the Primary Domain Failed

Understanding the Computer's Local Secure Channel Password

Many people confuse this with the user's Windows password.

They are completely different.

Think of it like this:

Your user password identifies you.
The computer password identifies the PC.

The error occurs because the computer's identity cannot be verified anymore.

What Is a Secure Channel?

A Secure Channel is an encrypted communication path between a domain-joined computer and the Domain Controller.

This secure channel allows Windows to perform tasks such as:

• User authentication
• Kerberos ticket requests
• Group Policy processing
• Password changes
• Active Directory communication

The secure channel depends on the machine account password.

If that password becomes invalid, the secure channel breaks.

How Windows Automatically Changes the Computer Password

One interesting fact many administrators don't know is that Windows automatically changes the computer account password.

By default:

• Password changes every 30 days
• Managed by the Netlogon service
• The process happens automatically
• Users never notice it

The process is simple:

1. Windows generates a new random machine password.
2. The password is stored locally.
3. The workstation contacts the Domain Controller.
4. Active Directory updates the computer account password.
5. Secure communication continues normally.

No administrator intervention is required.

Why Does the Trust Relationship Fail?

There are several common reasons.

1. Computer Stayed Offline Too Long

This is the most common cause.

Example:

A company laptop is stored for several months.

During this period:

• Active Directory expects newer machine passwords.
• The laptop still has the old password.
• Authentication fails.

Result:

Trust relationship failed.

Why Does the Trust Relationship Fail?

There are several common reasons.

1. Computer Stayed Offline Too Long

 
This is the most common cause.

Example:

A company laptop is stored for several months.

During this period:

• Active Directory expects newer machine passwords.
• The laptop still has the old password.
• Authentication fails.

Result:

Trust relationship failed.

4. Active Directory Restore

Restoring a Domain Controller from an older backup may restore an outdated computer password.

The workstation has the newer password.

Again, the passwords no longer match.

5. Virtual Machine Snapshot Rollback

This is common in virtual environments.

If a VM is reverted to an old snapshot, it also restores an old machine password.
The Domain Controller still expects the newer one.

Symptoms

You may notice:

• Trust relationship error during login
• Unable to log in using domain credentials
• Local Administrator login still works
• Group Policy not updating
• Authentication failures
• Domain resources inaccessible
• How to Verify the Problem

Login using a local administrator account.

Open PowerShell as Administrator and Run.

• Test-ComputerSecureChannel

Example output:

• False

This indicates the secure channel is broken.


 

Method 1 – Repair Using PowerShell (Recommended)

This is the fastest solution.

Open PowerShell as Administrator.


Run:

• Test-ComputerSecureChannel -Repair -Credential DOMAIN\DomainAdminUser -Verbose

Example:

• Test-ComputerSecureChannel -Repair -Credential CONTOSO\AdminUser -Verbose

If successful, PowerShell returns:

• True

Restart the computer.

The trust relationship should now be restored.

Method 2 – Reset the Computer Account

On the Domain Controller:

• Open Active Directory Users and Computers (ADUC).
• Locate the computer object.
• Right-click the computer.
• Select Reset Account.
• Confirm the action.

Now return to the workstation.

Repair the secure channel or rejoin the domain.

Method 3 – Remove and Rejoin the Domain

If PowerShell repair doesn't work:

Open:
System Properties


Go to:
Computer Name


Click:
Change


Choose:
Workgroup

Restart the computer.


Then:
Join the domain again.
Restart once more.


This creates a new secure relationship with Active Directory.

Method 4 – Using Netdom

If RSAT tools are installed:

• netdom resetpwd /server:DomainController /userd:Domain\AdminUser /passwordd:*

Restart afterward.

How the Authentication Process Works

Best Practices to Prevent This Error

Keep laptops online regularly
Long periods without connecting to the domain can increase the chance of machine password synchronization issues.


Avoid deleting computer accounts
Delete computer accounts only when the device has been permanently decommissioned.


Don't restore old VM snapshots
Rolling back a virtual machine may also roll back its machine password.


Verify before resetting
Before resetting a computer account, confirm that the issue is actually related to the secure channel.


Use PowerShell First
Instead of immediately removing and rejoining the domain, try repairing the secure channel. It is faster and preserves the existing computer account relationship.

Frequently Asked Questions (FAQ)

Does this error mean the user's password is wrong?
No.

The user's password is usually correct. The issue is with the computer's secure channel password.


Does Windows automatically change the computer password?
Yes.

By default, Windows changes the machine account password every 30 days using the Netlogon service.

Conclusion

The "A Trust Relationship Between This Workstation and the Primary Domain Failed" error is a common issue in Active Directory environments, but it is straightforward to resolve once you understand how machine account passwords and secure channels work.

For most situations, repairing the secure channel with PowerShell is the quickest and least disruptive solution. If that doesn't work, resetting the computer account or rejoining the domain will restore communication with the Domain Controller.

Whether you're an IT Support Engineer, System Administrator, or preparing for technical interviews, mastering this troubleshooting scenario is an essential skill that you'll likely encounter in enterprise Windows environments.