Logging-bailout errors in "Application" section of Windows Event Viewer

Product: ProfileUnity

Product Version: 5.7

Expires on: 365 days from publish date

Updated: October 21, 2014


Problem:Logging-bailout errors in the Event Viewer logs.



Windows Event Viewer "Application" Logs can show the following error.

  • Log Name:      Application
  • Source:        logging-bailout
  • Date:          4/25/2014 3:29:13 PM
  • Event ID:      1000
  • Task Category: None
  • Level:         Error
  • Keywords:      Classic
  • User:          N/A
  • Computer:     XYZ.pc


The description for Event ID 1000 from source logging-bailout cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
failed to write message to log file

Possible Resolution(s):

These errors can be generated, because a location for logging (usually located in Local AppData) is not available.

Please check the registry 

HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders


Local AppData

Verify that both locations are accessible (no typos in the path)

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Article is closed for comments.