Validate configuration and reload it safely#

When to use this procedure#

Use for parsing, missing-object, unsupported-option, and reload events.

Applies to#

This procedure applies to EventReporter.

Prerequisites#

  • Use an account that can read the product configuration and Windows diagnostic state.

  • Replace angle-bracket placeholders with values from the affected system.

Safety#

  • Run diagnostic checks before changing configuration.

  • Remove passwords, private keys, license data, and other secrets from evidence.

Configuration path#

Configuration Client > the service, rule, or action named on the Event ID page.

Procedure#

  1. Export the pre-change configuration, then open only the exact service, ruleset, filter, or action named in the event.

    Expected result: The event detail and Configuration Client identify the same object and a readable pre-change export exists.

    If it fails: Do not infer the object from its type alone; collect the complete event and configuration export first.

  2. Verify the backup metadata, then check required references, product availability, paths, addresses, ports, and credentials for that object only.

    Get-Item -LiteralPath '<CONFIG_EXPORT>' | Format-List FullName,Length,LastWriteTime

    Expected result: Every required reference resolves to an existing object and every selected feature is available in this product and edition.

    If it fails: Restore the export if the edited configuration cannot load; do not copy unsupported objects from another product or edition.

  3. Save the smallest correction, reload the configuration using the Configuration Client’s normal apply path, and run one identifiable test through the edited object.

    Expected result: The intended destination records the test exactly once.

    If it fails: Restore the pre-change export if loading fails, then collect the first new product event and bounded debug output without changing unrelated objects.

Rollback#

  1. Restore the configuration export created before the change.

  2. Reload the restored configuration and verify the previous behavior.

Verify the result#

Confirm that the corrected object loads, the intended destination records one identifiable test, and neighboring rules and services continue normally.

Evidence to collect#

  • The complete Event Log entry and neighboring product events with timestamps.

  • The command output, relevant configuration export, and bounded debug log from the same interval.