Free Microsoft Windows settings practice questions

The Pop-up Blocker is a strong suspect whenever a user clicks something and 'nothing happens.' Payment screens, sign-in windows, and report generators often open as pop-up windows, and the blocker silently prevents them from appearing. Adding the site as an exception or relaxing the blocker for that page restores the missing window. An incorrect proxy server address would typically break the entire browsing session with errors like 'cannot display the webpage' or repeated timeouts, not just a single button, and here the site loads fine. A disabled SSL/TLS protocol would prevent the secure page from loading at all, producing connection or certificate failures across the whole site rather than a non-responsive button. An incorrect system clock causes certificate warnings that make valid certificates appear expired or not yet valid, which again would block the page from loading rather than suppress a single pop-up window. Because the page renders normally and only the click does nothing, the blocked pop-up is the correct diagnosis.

Windows can automatically change the default printer to the most recently used device, which is exactly what happens when a laptop moves between networks. Turning off 'Let Windows manage my default printer' stops this behavior, so the printer the user manually sets as default stays selected. Reinstalling the printer driver does not stop Windows from reassigning the default, and a reinstall can actually create a new queue that steals the default role, making the problem worse. Restarting the Print Spooler service clears stuck jobs and resolves 'offline' or frozen queue conditions, but it has no effect on which printer Windows chooses as the default. Clearing the print queue and canceling jobs addresses stuck output, not the automatic default-switching behavior. Because the root cause is Windows managing the default based on recent use, disabling that option is the correct, stable fix.

Ports and connection settings are device-level configurations, so they live in Printer properties. When a network printer's IP address changes due to DHCP, the existing port silently points to the wrong address and jobs stop arriving. Updating or adding the correct port in Printer properties reconnects Windows to the printer. Printing preferences controls user-level defaults such as paper size, orientation, and color versus grayscale, not the port or connection, so it cannot fix an address mismatch. Network and Sharing Center reports the PC's own network status and adapter settings; it does not manage a specific printer's port assignment. Device Manager is used to manage hardware drivers and status for local devices, not to reconfigure the TCP/IP port of a networked printer. Because the failure is a device-level port pointing to a stale address, Printer properties is the correct location for the fix.

When a device can reach an IP address directly but cannot resolve names, the problem is name resolution, which points squarely to DNS. Verifying the DNS server entries in IPv4 settings, or setting them back to automatic and renewing the lease, is the correct fix. The default gateway is working correctly here, because the successful ping to 8.8.8.8 proves the PC can route traffic beyond the local network; a broken gateway would cause the PC to reach nothing at all. The subnet mask identifies the device on the local LAN, and if it were wrong the PC would struggle with basic local connectivity, not selectively fail name lookups while IP pings succeed. Wireless signal strength only proves the PC can hear the access point; strong bars do not guarantee name resolution, and the successful IP ping already shows the wireless path is functional. Because IP reachability works while name resolution fails, DNS is the correct first thing to check.

Repair attempts to restore missing or corrupted program files and registry entries while typically keeping the user's settings intact. Because the app opens but then crashes, and the user's configuration must be preserved, Repair is the least disruptive and most appropriate first choice. Uninstall removes the app and its installed files and may strip shared components, which is the right move only when an app won't load at all or is no longer needed; it is too aggressive when a repair could resolve the crash while keeping settings. Change launches the installer in maintenance mode to add or remove optional modules and features, which fits adding a missing component rather than repairing corrupted files causing crashes. Turn Windows features on or off enables or disables built-in optional components like .NET or Hyper-V, not third-party application files, so it does not address a crashing installed program. Because the app opens but behaves badly and settings must be retained, Repair is the correct starting option.

Windows Defender Firewall applies different rule sets depending on the active network profile. If the app is allowed only on Private but the PC has switched to a Public profile, the allow rule no longer applies and the connection is blocked. Many 'it worked yesterday' tickets trace back to a profile change like this, so confirming the active profile is the correct first step. Outbound rules are generally permitted by default, and blocking outbound traffic is uncommon in typical setups, so this is unlikely to be the sudden cause. If the firewall were turned off entirely for all profiles, traffic would flow more freely, not be blocked, so a disabled firewall would not explain the failure. The scenario states the app is still allowed for Private, meaning the executable is still in the allowed list, so it was not removed. Because the allow rule is profile-specific and only covers Private, a switch to Public is the most likely reason the app now fails.

Windows uses a separate default communications device for calls in apps like Teams and Zoom, distinct from the default output device used for normal audio. If system sounds and browser videos work but call audio does not, the default communications device is likely pointed at the wrong output, so the call audio is routing to a device the user is not listening to. If the Windows Audio service had stopped, all audio would fail, including system sounds and browser videos, which is not what is happening here. A corrupt audio driver in Device Manager would typically break all playback and often show a warning symbol, not selectively affect only call audio. A muted master output volume would silence everything the user hears, including browser videos, so it cannot explain audio that works everywhere except calls. Because only the communications path is affected, the default communications device selection is the correct place to check.

Roll Back Driver returns the device to the last working driver version without removing the device, which makes it one of the safest options when a device breaks specifically after a driver update. It is especially valuable for display adapters and network cards, where a bad update can cause corruption or loss of connectivity. Uninstall device removes the driver installation and forces Windows to re-detect and rebuild it, which is riskier and may reinstall the same problematic driver or leave the display without a proper driver during the process. Disable device only stops Windows from using the hardware, which would leave the user without display output rather than restoring the previous working driver. Scan for hardware changes triggers re-detection of hardware but does not revert to an earlier driver version, so it would not undo the problematic update. Because the failure occurred immediately after an update and the goal is to return to the known-good version, Roll Back Driver is the correct and safest choice.

Before removing an account, especially one with administrator rights, you should verify that at least one other reliable admin account exists on the device. Removing the last administrator can lock everyone out of system-wide management tasks, so keeping a working admin path is essential for recovery and ongoing support. Converting all remaining accounts to standard users would actually strip administrative access from the device, creating the very lockout risk you are trying to avoid. Disabling User Account Control weakens a core security protection that prompts for approval on high-impact changes; it has nothing to do with safely removing an account and would increase risk. Switching to a Public network profile only affects firewall and discovery behavior on the network and does not protect against losing administrative access when deleting an account. Because the greatest danger is losing the only admin path, confirming another admin account exists is the correct precaution before removal.

The most likely cause is scope. Windows indexes common user areas by default, but a custom folder stored outside the user profile is often excluded. Using Modify in Indexing Options to add that location is the least disruptive fix and directly addresses the problem. Rebuilding the entire index is a strong remedy reserved for corruption or stale results, and it can take minutes to hours while increasing CPU and disk activity, so it should not be the first step. Restarting the Windows Search (WSearch) service helps when indexing appears hung, but there is no indication the service is stalled here. Changing the index location is intended for storage planning, not for including new folders in search results, so it would not make the missing file appear. Always begin with the least disruptive check, confirming scope, before moving to service restarts or a full rebuild.