There are many symptoms a PC may exhibit if something is not right with the system files or configurations.
In order to address and correct the problem, a system administrator needs to troubleshoot and identify the root of the problem before corrective actions can be taken. Fortunately, there are many system tools and features that will aid in system troubleshooting and commonplaces to begin examining on a system. The BIOS, which stands for Basic Input output system,
is responsible for ensuring hardware is in working condition
prior to loading the operating system.
If a system is having issues and it is suspected to be hardware related, booting into the systems bios can help troubleshoot those issues by confirming settings are correct, such as drives being properly identified and configured,
secure boot running to ensure only trusted software's loaded
making sure memory is recognized and that the boot sequence is correct.
Safe mode can be used to troubleshoot system startup issues. Safe mode options are access by pressing the shift key while the system is restarting,
this will very depending on the operating system version.
Once in safe mode, select troubleshooting advanced options and then start up settings
within the startup options page. There are several choices to help diagnose the cause of the problem. Enabling and disabling of features, such as what service is to run while in safe mode or initiating boot logs will help pinpoint where to focus corrective efforts.
Another option for diagnosing a problem is the Windows System Recovery options, also known as the Windows Recovery environment, or when Ari
it is a group of Windows repair, restore and diagnostic tools.
The recovery options can be accessed by the Advanced Boot Options Menu or from the window set up or repair disc,
depending on the version of Windows. Recovery Tool options include tools for auto repair, restoring the system to a known good working state, checking memory for heirs or launching a command prompt for running advanced diagnostic tools.
In addition to running the window recovery environment from the system itself, a Windows repair disc will provide the same utilities, but from a bootable CD or DVD. The Bootable disc can run the Windows recovery environment by booting to a disk at startup Windows Distribution media can also be used to repair an installation and includes additional options
such as refresh and reset
using command line tools at the command prompt can help resolve many Windows system issues.
Command line tools can perform repairs to the boot configuration data store and several other repair and recovery tasks.
Tow. Launch a command, prompt either type CMD in the start Menu Search field or choose the application icon from under system Tools and applications. Start menu Shortcut.
Some command line tools will need to be run with elevated privileges if a user has an admin account, right, clicking on the command prompt application and choosing runners. Administrator will launch and run the command tools with admin permissions after the appropriate credentials are interred. Of course,
the following are just a few diagnostic or troubleshooting tools that can be run from the command line.
SFC or System File Checker is best run with admin privileges to enable full capabilities.
It's a utility designed to check and perform needed repairs on system files such as dot dll or dot E X e files and font files used by the desktop
from the command line running as admin into the command SFC space ford slash Scan. Now, during the scan, any corrupted files will be repaired, and when the scan is finished results will be displayed. Another utility is defrag
Overtime. A system's performance may slow down due to the number of files on a hard drive that have been fragmented.
In turn, the system takes more time to locate file pieces. A D fragmentation tool will put file blocks back into sequential order, so it's easier for the device to locate. Newer computers may not need to be de fragmented or do it automatically,
but to manually run defrag, it can be found under the search menu or run from the command line.
Microsoft Register Server or Reg Server 32 is used for troubleshooting issues caused by new applications that are affecting the working state of pre existing applications. It can register an unregistered object linking and embedding controls such as dot dll or dot OS X files used by applications.
When the file components of an older application have been replaced or disabled by a new application, they sometimes need to be re registered
and, of course, rejected the tool to edit the system registry. It is not recommended to edit registry key information unless absolutely necessary and certain of actions
when uncertain of where to start or if more clues are needed for troubleshooting, the Windows event viewer is a useful resource for examining logs related to system events. Warnings were heirs from the window search bar. Enter event. Viewer administrative privileges may be required. The log categories are on the left side of the window.
The log entries are classified by level, with Ares,
identified by a white exclamation point in a red circle,
warnings air indicated by a black exclamation point and a yellow triangle, while general information logs are denoted with the blue exclamation point in a white circle.
Regular review of the event logs could also be a preventive measure for awareness of potential problems that had no observable symptoms.
When a system is having performance or other inhibiting behaviors, there are several. Resource is for troubleshooting, diagnosing and even repairing. These were just a few useful utilities, and the administrators, toolbox and administrator should always be familiar with the tools available to them specific to the operating system they're responsible for