Emergency Windows Update: Four Settings to Change Today
Archi4 min read
Contents
- The Emergency Patch Is Rolling Out
- Check for the update manually
- Disable the WebClient service
- Turn off automatic playback
- Replace admin accounts with standard accounts
- Keep one restore point
- Review the startup list
- What the patch does and what it does not do
- What to do on macOS and Linux
- The longer-term change
- When to install
The Emergency Patch Is Rolling Out#
A privilege escalation flaw in the Windows shortcut parser is under active exploitation. The attack uses a malicious .lnk file placed in a shared folder or on a removable drive. Opening the folder is enough to trigger it. No click on the file is needed.
Microsoft is pushing the fix through Windows Update in staged batches. A formal advisory is expected later today. The rollout order depends on hardware and region, so some machines will not show the patch for hours. Do not wait for the automatic prompt.
Check for the update manually#
Open Windows Update and click "Check for updates." Look for a KB entry with "out-of-band" or "emergency" in its title. If the update fails to install, the most common cause is low disk space on the C: drive. Free at least 8 GB before retrying. A second cause is third-party antivirus software that locks system files. Temporarily disabling real-time protection can help, but turn it back on immediately after the reboot.
Disable the WebClient service#
The shortcut flaw is reachable through the WebClient service, which lets Windows treat network paths as local folders. Most home users never use this service. Open services.msc, find WebClient, open its properties, set Startup type to Disabled, and stop the service. This removes one remote attack path even before the patch lands.
Turn off automatic playback#
Windows can interpret certain file types as soon as a USB drive is inserted. Automatic Playback is the feature behind that behavior. The current exploit creates a shortcut on the drive, so disabling AutoPlay reduces the chance of accidental execution. In Windows 11, go to Settings, Bluetooth and devices, then AutoPlay. Set "Use AutoPlay for all media and devices" to Off.
Replace admin accounts with standard accounts#
The privilege elevation part of the attack matters less if your daily account is not an administrator. Create a standard user account for normal work and keep one administrator account with a separate long password. When Windows asks for administrator credentials during an install, type them in. Do not stay logged in as admin for browsing and mail.
Keep one restore point#
Out-of-band updates sometimes cause more problems than they solve. Before you install, create a restore point manually. In Windows 10 and 11, type "Create a restore point" in the search box, open the System Protection tab, select the system drive, and click Create. Name it with the date and the KB number. If the update breaks printing or network shares, you can roll back in a few minutes without losing documents.
Review the startup list#
A failed update can leave the boot process slow, not broken. Open Task Manager, choose Startup apps, and disable anything you do not recognize. The usual offenders are updater utilities that run with user-level permissions. They do not affect the operation of the main program, only its auto-update check. Removing them from startup is safe and makes the post-update reboot faster.
What the patch does and what it does not do#
The patch changes how Windows parses shortcut metadata, specifically the icon location fields. Attackers used those fields to run code in the context of the process that opened the folder. The fix adds a length check and blocks the malformed values. That removes the exploit path, but it does not clean machines that are already infected.
Users who see unexpected shortcuts on USB drives are advised to scan them with Microsoft Defender Offline. Open Windows Security, go to Virus and threat protection, and run a full scan. If the machine was on a shared network with other computers, scan those devices as well. There is no public list of indicators of compromise yet.
What to do on macOS and Linux#
The same class of flaw exists in other operating systems. macOS users should confirm that Gatekeeper is still enabled. Open Terminal and run "spctl --status." If it says "assessments disabled," turn it back on through System Settings, Privacy and Security, then Developer Mode. Linux distributions that use GNOME should check whether the desktop automatically mounts removable media. Most distributions ship with this disabled by default, but older setups may have it enabled from a previous configuration.
The longer-term change#
This incident is a reminder that operating system updates do more than add features. The monthly release cycle has gaps, and the gap between detection and patch can be days. For ordinary users, the practical change is to treat every USB drive and shared folder as untrusted. Set the file explorer to show known extensions, turn off hidden files, and do not open shortcuts from external storage unless the drive belongs to someone you trust.
Update time is also a good moment to check the firmware password on your laptop. Many recent Windows laptops ship with UEFI password protection disabled. Without that password, someone who steals the device can boot from USB and replace the operating system entirely. A user-level password does not stop that. The UEFI password, awkward as it is, does.
When to install#
If the emergency update appears in Windows Update, install it within the next hour. If it does not appear, do not download a standalone package from third-party sites. The only safe source is the Microsoft Update Catalog, and only when the KB number is confirmed. Until the update is available, the WebClient and AutoPlay changes above are the best protection.
For macOS and Linux users, the risk is lower today. Treat this as a maintenance window. Review your update settings, confirm that automatic updates are on, and check that you have a restore point or snapshot mechanism. The exploit changes, but the checklist stays the same.
More articles