Quality grade: defaultApp execution delay, check again to see if it is resolvedHelp with app launch delay tasks in line 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] Distinguishes between app starting, file opening, network waiting, and plug-in loading. [Results to be created this time] Read the record of actions already performed and create a resolution verification table. Decide what to check when restarting, using it normally, or repeating the same task, and distinguish between success and recurrence. Leave verifications that have not been performed as unverified. [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 confirm with actual records whether the original symptoms do not recur under the same conditions. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.
Quality grade: defaultManage app launch delays to prevent them from happening againHelp with app launch delay tasks in line 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] Distinguishes between app starting, file opening, network waiting, and plug-in loading. [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.Copy prompt
Quality grade: defaultChrome sync crash, collect support request dataHelp 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] 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.Copy prompt
Quality grade: defaultChrome start page, narrow down the cause by symptomsHelp us work on the Chrome start page 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 startup settings, session restoration, and shortcut execution arguments. [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.Copy prompt
Quality grade: defaultPrinter connection error, look for clues on screen and in listsHelp 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] 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.Copy prompt
Quality grade: defaultFind duplicate photos, find clues on screen and in listsHelp 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] 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.Copy prompt
Quality grade: defaultCheck and remove suspicious programsI suspect {{program}} is related to this problem. Help me check the publisher, installation path, and installation time, and give me the basis for judging whether it can be removed. If you need to remove it, I'll walk you through the official removal process and how to see what's left.Copy prompt
Quality grade: defaultPrinter connection error, check again to see if it is resolvedHelp 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] Read the record of actions already performed and create a resolution verification table. Decide what to check when restarting, using it normally, or repeating the same task, and distinguish between success and recurrence. Leave verifications that have not been performed as unverified. [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 confirm with actual records whether the original symptoms do not recur under the same conditions. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultInsufficient storage space, check again to see if it is resolvedHelp with storage space shortage 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 purpose and cleanup impact of large items and avoid guessing deleting system files. [Results to be created this time] Read the record of actions already performed and create a resolution verification table. Decide what to check when restarting, using it normally, or repeating the same task, and distinguish between success and recurrence. Leave verifications that have not been performed as unverified. [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 confirm with actual records whether the original symptoms do not recur under the same conditions. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultMissing cloud synchronization, gathering support request dataHelp with missing cloud synchronization 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 synchronization status, account, exclusion rules, and file name restrictions. [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.Copy prompt
Quality grade: defaultUpdate failed, look for clues in screens and listsPlease help me with the update failure 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 the error code, storage space, restart, and supported version first. [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.Copy prompt
Quality grade: defaultOrganizing large amounts of video, establishing a resolution order before making changesHelp us organize large amounts of video 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 original, edited project, and export files and check the impact of linked files. [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.Copy prompt
Quality grade: defaultCheck file backup, establish resolution order before making changesHelp 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] 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.Copy prompt
Quality grade: defaultApp crashes repeatedly, check management status at onceHelp with repetitive app crash tasks based on 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 occurring tasks, recent changes, plugins, and logs to narrow down the cause. [Results to be created this time] Select only the items that are meaningful in the current environment and classify them as normal, needs confirmation, or needs action. Write down the confirmation location and judgment criteria for each item and do not make assumptions about areas without data. For organizing or deleting, provide candidates and impact review first. [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 each state classification is supported by actual observations. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultPossibility of recovering deleted files, take action step by stepHelp 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] 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.Copy prompt
Quality grade: defaultMicrophone input error, gathering support request dataHelp me work on microphone input 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] Separate settings for each selected device, app permission, input level, and 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.Copy prompt
Quality grade: defaultFind duplicate photos, collect support request dataHelp 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] 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.Copy prompt
Quality grade: defaultIncreased CPU usage, gathering support request dataHelp us work on increasing CPU usage according to the goals and data 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 duration, execution process, and task type, and do not conclude that the process is malicious based on the name alone. [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.Copy prompt
Quality grade: defaultOrganize file names, establish resolution order before changingHelp organize file names 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 impact of rules, conflicts, extensions, and connection programs and create a list before and after changes. [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.Copy prompt
Quality grade: defaultCheck file backups, look for clues on screens and listsHelp 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] 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.Copy prompt
Quality grade: defaultExternal monitor issues, reversing incorrect actionsHelp us work on external monitor issues 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 input source, cable, resolution, refresh rate, and display settings. [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.Copy prompt
Quality grade: defaultClean up old apps, check again to see if it's resolved.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] Read the record of actions already performed and create a resolution verification table. Decide what to check when restarting, using it normally, or repeating the same task, and distinguish between success and recurrence. Leave verifications that have not been performed as unverified. [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 confirm with actual records whether the original symptoms do not recur under the same conditions. Distinguish between the basis for the outcome, remaining uncertainties, and next actions, and mark only what has actually been confirmed as complete.Copy prompt
Quality grade: defaultAutomatically add bookmarks, find clues on screen and in listsHelp us automatically add bookmarks 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 timing of changes in synchronization, extensions, and installed apps. [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.Copy prompt
Quality grade: defaultKeyboard input abnormalities, comparing changed environmentsHelp 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] 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.Copy prompt