Event Viewer

@grits: There a lots of folks around here that can help. You needn't wait for me. I got the info from Hammerhead and tried it. If it's a Mr.Fixit, you can be fairly sure that it will work - sometimes you might have to read the KB to be sure it's what you want (I know, I know.... that means you have to understand what they're talking about in the first place - lol). You'll be a guru fairly soon if you hang around here - I can already tell the difference - more confidence and clarity in your posts.

I had to help someone install a CB in a truck. So I was busy yesterday afternoon. I am wondering where you stand now on your errors at boot. Have some of them went away? You have been busy.

If you haven't done it yet try this. Open a command prompt. Open it as administrator. (left click and select run as admin). Type in "SFC /Scannow". Wait for results if it finds problems. Run it again (at least 3 times) till it reports no problems. Also you can boot into safe mode and run it (might help).

@grits: Don't worry too much about the Events Log, it's most useful when you're experiencing some particular issue. Otherwise, it's just there collecting information on events. There's way too much information presented and you can filter out ones that you know are unimportant (starting xyz, stopping xyz), but I generally only use Event viewer to chase down a problem.

The Action Center (Control Panel => Action Center or the flag in the notification area) should alert you of any issues that you need to address - no need to go looking / deciphering events.

the 1014 error is probably just telling you that it can't connect at this time - perhaps it's a bit hasty launching DHCP services before dependent services are fully active. But yeah - you should check it out, for your own satisfaction.

grits,
I recommend clearing the Event Logs to get rid of all of the chaff.

A master explanation of all possible events would be nice. Does not exist. There are some commercial products which will cover many of them.

Your best bet is always to read the description inside EventViewer and to google the event.

CLEAR EVENT LOGS USING POWERSHELL


Step 1: Create a powershell script
Open NotePad.

Copy following into notepad:
Get-WinEvent -ListLog * -Force |
% { $_.logname;Wevtutil.exe cl $_.logname };
Wevtutil.exe cl system

Save as ClearEvents.ps1 in %userprofile%\desktop

Close Notepad

Step 2: Create a shortcut to have powershell run the script
Right-Click on an empty spot on your desktop
Choose NEW -> Shortcut

In the box,
Enter powershell.exe & %userprofile%\desktop\ClearEvents.ps1
NEXT button

Type CLEAR EVENTS (or any name of your choice)
FINISH button


Step 3: Run the script
The shortcut must be run as administrator.
RIGHT-CLICK on your CLEAR EVENTS shortcut
Choose Run as Administrator

If Powershell complains,then
Run PowerShell as administrator and set the script execution policy
START ORB | type PowerShell | do NOT hit Enter |
right-click on PowerShell (at top of list) |
choose Run as administrator

Enter following commands:
Set-ExecutionPolicy remotesigned
EXIT

You can now proudly declare yourself a PowerShell user and aficionado. Now all you need is a COMPUTER GEEK badge. Batch files are so blasé.

There is nothing magic about %userprofile%\desktop. If you already have a C:\Scripts folder, then you may prefer to store the ClearEvents.ps1 script there.

Want to stay in Powershell after running the script? Add -noexit to the shortcut’s target (right-click on the shortcut. Properties, Shortcut tab, Target field).
powershell.exe -noexit & %userprofile%\desktop\ClearEvents.ps1


=========================================================================

CLEAR EVENT LOGS USING A BATCH FILE


The number of events in the event logs can be overwhelming.
Purging the logs so that only fresh events are present can be helpful
in troubleshooting.


OPEN NOTEPAD
Start Orb | type NOTEPAD | ENTER

COPY AND PASTE FOLLOWING INTO NOTEPAD

@echo off
FOR /F "tokens=1,2*" %%V IN ('bcdedit') DO SET adminTest=%%V
IF (%adminTest%)==(Access) goto noAdmin
for /F "tokens=*" %%G in ('wevtutil.exe el') DO (call :do_clear "%%G")
echo.
goto theEnd
:do_clear
echo clearing %1
wevtutil.exe cl %1
goto :eof
:noAdmin
Exit
:theEnd
:ause

SAVE AS CLEARLOGS.BAT

CLOSE NOTEPAD

RUN CLEARLOGS.BAT AS ADMINISTRATOR
Right-click on ClrEventLogs.BAT
Click on Run as Administrator

The list of cleared logs will fly by on the screen.
If you would like to see the list, then remove the two double colons
in front of the pause statement at the very end of the BAT file.