From browser issues to full disks, find your next troubleshooting step.

Help us with file backup inspection according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the location, recency, and possibility of restoration of the original and copy. [Results to be created this time] First, check the operating system, occurrence time, and reproduction conditions. Rather than determining multiple causes all at once, suggest confirmation methods for each possibility in order. If the results of one step change your next decision, please wait for my answer. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Distinguish between actual observations that have reduced the candidate causes and the remaining possibilities. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help with tasks beyond keyboard input according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between language, input method, accessibility settings, and specific key issues. [Results to be created this time] Establish a resolution order starting with confirmations that have less impact and are easier to reverse. At each step, let us know the expected impact, data to be preserved, how to return, and results to be checked. Depending on the operating system version, use only the menus or commands you have confirmed. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each step of the plan has execution conditions and stopping criteria. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us organize our login items according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the role and use of the autorun item and change it. [Results to be created this time] Create a symptom description to send to customer support or repair personnel. Organize device, version, occurrence time, reproduction steps, attempted actions, and error phrases, and hide account information or secret values. Separate causal speculation from actual observations. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure the recipient can understand the same symptoms and that there is no unnecessary personal information. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us organize our login items according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the role and use of the autorun item and change it. [Results to be created this time] Compare the normal time/environment and the current state with the same items. Select a hypothesis related to the symptom among installation, settings, account, connection, and file location changes. Don't confirm it as a cause just because it's related, but suggest an experiment to distinguish it. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Compare one condition at a time to distinguish between cause and accidental change. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us with file backup inspection according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the location, recency, and possibility of restoration of the original and copy. [Results to be created this time] Compare the normal time/environment and the current state with the same items. Select a hypothesis related to the symptom among installation, settings, account, connection, and file location changes. Don't confirm it as a cause just because it's related, but suggest an experiment to distinguish it. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Compare one condition at a time to distinguish between cause and accidental change. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us organize our login items according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check the role and use of the autorun item and change it. [Results to be created this time] Establish a resolution order starting with confirmations that have less impact and are easier to reverse. At each step, let us know the expected impact, data to be preserved, how to return, and results to be checked. Depending on the operating system version, use only the menus or commands you have confirmed. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each step of the plan has execution conditions and stopping criteria. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us find duplicate photos according to the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Rather than judging the file name to be the same, check the content, resolution, and original preservation. [Results to be created this time] Please guide me through one first step I can take with the current data. Please explain the impact and recovery method before execution and select the next action after receiving my confirmation results. Don't change multiple settings at the same time, but keep track of which changes worked. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Check whether symptoms change under the same conditions before and after taking action. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help increase memory usage by aligning with the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Distinguish between real memory pressure and simple cache and check usage by app. [Results to be created this time] Create a symptom description to send to customer support or repair personnel. Organize device, version, occurrence time, reproduction steps, attempted actions, and error phrases, and hide account information or secret values. Separate causal speculation from actual observations. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure the recipient can understand the same symptoms and that there is no unnecessary personal information. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help you with your deleted file recovery possibility task according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] It does not guarantee successful recovery after checking the recycle bin, version history, and backup. [Results to be created this time] Establish a resolution order starting with confirmations that have less impact and are easier to reverse. At each step, let us know the expected impact, data to be preserved, how to return, and results to be checked. Depending on the operating system version, use only the menus or commands you have confirmed. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure each step of the plan has execution conditions and stopping criteria. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Please help me with the Bluetooth connection task according to the goals and materials below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check pairing, power, distance, and multi-connection status. [Results to be created this time] Please first check the changes made and the data before the changes. Classifies recoverable settings, files, and account states and suggests the order in which they can be restored. Don't promise a successful restore without verifying that you actually have a recovery point or backup. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Make sure that data and existing normal functions are preserved after restoration. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

My computer repeats {{symptoms}}. The operating system is {{os}}. Start by asking the questions you need to narrow down the cause, then show you how to check in order of likelihood. Proceed one step at a time and wait for my confirmation results.

Help us organize old apps according to the goals and resources below. [input] Goals and usage situations: {{goal}} Resources to review: {{source}} Conditions and Constraints: {{constraints}} Previous attempts and records: {{history}} [Key points to check in this topic] Check whether it is used, data location, and normal removal method. [Results to be created this time] Extract only verifiable information from the provided screen, list, and error text. Indicate the meaning of each clue and additional items to check. Do not conclude that an item is malicious or unnecessary based solely on the file name or program name. [Working Principle] After checking the operating system and version, provide guidance on the relevant environment. Before changing files, accounts, or settings, explain the implications and recovery methods, and don't tell anyone you've actually deleted a deletion candidate. Do not arbitrarily disable business management policies or security protections. If there is no input that will change the results, ask only the necessary questions first and proceed with the parts that can be confirmed with data. [Completion criteria] Please check whether there is a specific basis for each judgment in the screen or data. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.