Changing several settings at once makes a problem harder to understand. A baseline gives you something to compare against.
Record the symptom
Write what you expected, what happened instead, and when it started. Preserve the exact error message, but remove sensitive information before sharing it.
Find the boundaries
Does it affect one app or several? One device or every device? Every attempt or only a specific action? Test one boundary at a time.
Identify recent changes
Updates, hardware changes, and configuration edits can suggest where to start. A recent change is a clue, not proof of the cause.
Choose a reversible test
Decide how to undo it before making the change. Use a test environment where possible, and back up important data. Avoid deleting information or disabling protections simply to see what happens.
Compare and record
Repeat the original action. If the symptom does not change, restore the setting before trying another idea. Record unsuccessful tests as well as successful ones.
Know when to stop
If you cannot explain the consequences of the next step, gather the evidence and ask for help. A concise record of observations is better than a list of random fixes.