Share via

Volume change journal

Anonymous
2023-08-16T23:07:38+00:00

Event viewer has posted the following:

Volume change journal is not active (0x8008049b), event id 3079.

Have run sfc, DISM, chkdsk, and all ok. No problems.

Am I being unduly concerned?

Windows for home | Windows 10 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

3 answers

Sort by: Most helpful
  1. Anonymous
    2023-08-20T12:31:53+00:00

    Hi KennethStarick

    Feel free to post again in the future if you run into problems with Microsoft products.

    Best Regards,

    LucyW-MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2023-08-18T19:39:02+00:00

    Thanks Lucy for your advice.

    Much appreciated.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2023-08-18T05:41:17+00:00

    Dear KennethStarick

    Welcome to Microsoft Community.

    Based on the information you have provided, this issue appears to be related to the Volume Change Journal. The Volume Change Journal is a mechanism for tracking changes to the file system and is typically used by operating systems to monitor operations such as file creation, modification, and deletion. Seeing an error message in the Event Viewer that the Volume Change Journal is not active may cause some concern, but it may also be part of a normal scenario. The message does not point directly to an error.

    You have performed some diagnostic steps, such as running sfc, DISM, and chkdsk, and found no problems. This is good practice because these steps can help you troubleshoot file system and system component problems.

    If there are no obvious problems with your computer, such as missing files, performance degradation, etc., and other features and applications are working normally, then you don't need to worry about this warning.

    Thanks for your patience and understanding!

    Best Regards,

    LucyW-MSFT | Microsoft Community Support Specialist

    Was this answer helpful?

    0 comments No comments