220-1102 Question 589
Single answerSlow profile loadA help desk technician is troubleshooting a Windows 10 laptop used by a remote employee. The user reports that after entering credentials, the desktop takes several minutes to appear, but once loaded, applications run normally. Other users on the same network are not affected. The technician notices the delay occurs during the "Welcome" phase and recently the user began redirecting large folders to a cloud-synced location inside the profile. Which action is the MOST appropriate first step to reduce the slow profile load?
- A
Create a new local user profile for the employee and migrate only necessary user data
- B
Disable User Account Control so the profile can load without permission checks
- C
Increase the size of the page file to improve logon performance during the Welcome phase
- D
Run CHKDSK on the system drive because all slow logons are caused by file system corruption
Show answer and explanation
Correct answer: A
Explanation
When a slow logon happens only for one user and the delay is concentrated during the Welcome phase, CompTIA A+ objectives point technicians toward profile-related troubleshooting rather than hardware or system-wide tuning. A damaged or oversized user profile can significantly delay logon, especially if large amounts of data, sync activity, or redirected folders are involved. Best practice is to test with or create a new profile, then migrate only essential user data such as documents, desktop items, and browser data as appropriate, while avoiding corrupted settings files. Microsoft troubleshooting guidance for temporary or corrupted profiles and standard Windows support practice both support isolating the issue by testing with a fresh profile before making broader system changes.
- A. Correct.
Correct. A corrupted or excessively bloated user profile is a common cause of slow logon during the Welcome phase in Windows. Creating a new profile and migrating only needed user data is a standard troubleshooting step when the problem is isolated to one user and performance is normal after sign-in. This also avoids bringing over damaged profile settings or unnecessary cached content from cloud-synced folders.
- B. Incorrect.
Incorrect. User Account Control manages elevation prompts and administrative consent, not normal profile loading behavior. Disabling UAC is not a recommended troubleshooting step for slow profile load, and it weakens system security.
- C. Incorrect.
Incorrect. A page file supports virtual memory use, but the scenario points to a user-profile-specific logon issue rather than a system-wide memory bottleneck. Since applications perform normally after login and other users are unaffected, increasing the page file is unlikely to address the root cause.
- D. Incorrect.
Incorrect. CHKDSK can help when disk errors or file system corruption are suspected, but the statement that all slow logons are caused by corruption is false. In this scenario, the issue is isolated to one user's profile and aligns more closely with profile corruption or profile bloat than a general disk problem.