220-1102 Question 583
Single answerServices not startingA technician is troubleshooting a Windows 10 workstation used by a small accounting team. Users report that shared printers mapped from a print server are unavailable after every reboot. In Services, the Print Spooler service is stopped. When the technician tries to start it, Windows displays a message indicating the service could not start because a dependency service or group failed to start. Which action should the technician take FIRST to resolve the issue?
- A
Open the Print Spooler service properties and verify that any required dependency services are running and set correctly
- B
Run chkdsk /f to repair the disk, because spooler failures are usually caused by file system corruption
- C
Disable Windows Defender Firewall so the Print Spooler can communicate with the print server
- D
Reinstall all mapped printers from the print server to recreate the spooler configuration
Show answer and explanation
Correct answer: A
Explanation
This question focuses on practical service troubleshooting in Windows, a common A+ Core 2 task. When a service fails to start and Windows reports that a dependency service or group failed to start, the technician should first inspect the service properties and review dependencies. In the Services console, the Dependencies tab identifies which underlying services must be running. Best practice is to investigate the exact error presented before making broader changes such as reinstalling devices, disabling security controls, or running disk repairs. Microsoft documentation for Windows services and the Services management console supports checking service dependencies and startup status as a primary troubleshooting step when resolving service startup failures.
- A. Correct.
Correct. If Windows reports that a service cannot start because a dependency service or group failed to start, the first troubleshooting step is to check the service's Dependencies tab and confirm those supporting services are started and configured properly. In Windows, many services rely on other services, and a failed dependency will prevent the main service from starting.
- B. Incorrect.
Incorrect. Disk corruption can cause a variety of problems, but the error message specifically points to a service dependency issue. Running chkdsk may be useful in some broader troubleshooting cases, but it is not the best first step when Windows explicitly identifies a dependency failure.
- C. Incorrect.
Incorrect. The Windows Defender Firewall can affect network communication, but it does not typically prevent the local Print Spooler service from starting. This option reflects a common misconception that any printer issue is network-related, even when the failure is clearly with a local Windows service.
- D. Incorrect.
Incorrect. Reinstalling printers may help if printer mappings or drivers are damaged, but if the Print Spooler service itself cannot start because of a dependency failure, printer reinstallation will not address the root cause. The service must be operational before printer objects can function normally.