15.01.2024 Views

CompTIA A+ Certification All-in-One Exam Guide

  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

into the same discussion as BSoDs and kernel panic, but the SPoD is not

nearly as bad.

Registry

The Registry files load every time the computer boots. Windows does a

pretty good job of protecting your Registry files from corruption, but from

time to time something may slip by Windows and it will attempt to load a bad

Registry. These errors may show up as BSoDs that say “Registry File

Failure” or text errors that say “Windows could not start.” Whatever the case,

when you run into these sorts of scenarios, you need to restore a good

Registry copy. Depending on your Windows version, the best way to do this

is the Last Known Good Configuration boot option (see the upcoming

section). If that fails, you can restore an earlier version of the Registry

through Windows RE.

Windows 8.1 and prior (and early versions of Windows 10) keep a regular

backup of the Registry handy in case you need to overwrite a corrupted

Registry. By default, the task runs every 10 days, so that’s as far back as you

would lose if you replaced the current Registry with the automatically

backed-up files. Of course, it would be better if you kept regular backups too,

but at least the damage would be limited. You can find the backed-up

Registry files in \Windows\System32\config\RegBack (see Figure 16-25).

Figure 16-25 The backed-up Registry files located in the RegBack folder

To replace the Registry, boot to the Windows media to access Windows

RE and get to the Command Prompt shell. Run the reg command to get to a

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

Saved successfully!

Ooh no, something went wrong!