15.01.2024 Views

CompTIA A+ Certification All-in-One Exam Guide

  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

logs.

2. Identify the specific log file locations and descriptions.

3. Using Windows Explorer or File Explorer on your PC, navigate to

the specific log file locations and see if you can find your setup log

files.

Who knows, you may be on your way to becoming a Microsoft log file

reader!

Windows stores these log files in the Windows directory (the location in

which the OS is installed). These operating systems have powerful recovery

options, so the chances of ever actually having to read a log file, understand

it, and then get something fixed because of that understanding are pretty

small. What makes log files handy is when you call Microsoft or a hardware

manufacturer. They love to read these files, and they actually have people

who understand them. Don’t worry about trying to understand log files for

the CompTIA A+ exams; just make sure you know the names of the log files

and their location. Leave the details to the übergeeks.

EXAM TIP Expect a question or two about setup log files generated

during upgrades on the CompTIA 1001 or 1002 exam. You might expect

questions on the 1002 exam dealing with scenarios where Windows chokes

on a dated driver or network setting and fails to load. The log files will

readily show such problems, which you can correct by updating everything

before you try upgrading to Windows 10.

The question you might see on the 1001 exam relates to hardware,

specifically to system setup configuration problems. The CompTIA A+ 1001

5.3 objective tosses log entries and error messages under problems with

essential hardware, such as motherboards and RAM. If you get such an error

in the log file, try resetting the system setup to default settings. That has

worked for a lot of people.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!