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

Help me fix Chrome sync conflicts with 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 device, account, synchronization scope, and time of change and preserve the original data. [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 the trash can storage inspection 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] First identify the items you want to restore and explain the implications of permanent deletion. [Results to be created this time] Change only the parts where the cause has been identified into preventive rules. Present items to be checked regularly and abnormal signals/check cycles according to the usage environment. Please do not recommend installing general optimization programs or disabling unnecessary security features. [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] Ensure that causes and preventative actions are linked and maintenance burdens are realistic. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.

Help us work on Chrome notification ads 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 website notifications and pop-up/program notifications. [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 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] Change only the parts where the cause has been identified into preventive rules. Present items to be checked regularly and abnormal signals/check cycles according to the usage environment. Please do not recommend installing general optimization programs or disabling unnecessary security features. [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] Ensure that causes and preventative actions are linked and maintenance burdens are realistic. 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] 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 file open error tasks 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 extension, actual format, app version, and possibility of damage. [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.

Help organize the folder structure 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 categorizes by purpose of use, search method, and storage cycle and shows a plan before moving. [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 with Wi-Fi disconnection tasks 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] Narrow the scope by comparing single device, router, and line problems. [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.

Help me work on camera recognition errors 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 for device recognition, permissions, occupation by other apps, and connection 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.

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] 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 with laptop heating tasks 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] Compare the workload, ventilation, power status, and occurrence conditions and do not recommend excessive disassembly. [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 with printer connection error tasks 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 power, connection path, queue, and driver status. [Results to be created this time] Change only the parts where the cause has been identified into preventive rules. Present items to be checked regularly and abnormal signals/check cycles according to the usage environment. Please do not recommend installing general optimization programs or disabling unnecessary security features. [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] Ensure that causes and preventative actions are linked and maintenance burdens are realistic. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.