February 24, 2016 By Larry Loeb 2 min read

Windows 10 performed a forced update to KB 3135173 on Feb. 9, resetting the default associations established on certain documents and making it impossible to change them back. Many users found this mandatory update caused major problems and could have a negative impact on overall security.

A User Moans

After rebooting the machine following the update, one user on Windows 10 Forums noted that the Action Center started to issue constant pop-up alerts stating, “An app default was reset. An app caused a problem with the default setting for .avi files so it was reset to Films & TV,” although the file extensions would vary to include MP4s, PDFs and more. The user also said that custom context menu items for file types were deleted.

“I started manually changing the associations back to the way I had them,” the user wrote on the forum. “However, each time I finished making a change, within seconds the Action Center would fire the same message as before at me for the file type I’d just changed and it would be reset back to the MS default again.”

InfoWorld reported that this has happened to other users, as well. The changelog for this update doesn’t mention that anything like this should be happening, leaving many to wonder whether it’s a bug of some kind.

Microsoft acknowledged the situation but had no solutions yet. “We are aware of this issue that some customers are experiencing and are actively working to resolve it,” a spokesperson told Security Intelligence.

A Possible Solution

Ramesh Srinivasan at the Winhelponline blog figured out a way to stop Microsoft Edge, Photos, 3D Builder, Zune Music and Zune Video from taking over file associations for various file types through a registry edit.

Changing the registry file does not impair the functionality of the apps after the edit is applied. Several other industry experts have endorsed this registry-based approach for rectifying the problem, at least in the short term.

InfoWorld noted that there is an alternative way to deal with this, reporting that some users uninstalled the update and blocked it from running again with the help of a Windows utility tool.

Bigger Problems With Windows 10

A forced update to an operating system is expected to not display this type of behavior. As long as Microsoft makes bug fixes and security updates that are rolled into one nonoptional package, Windows 10 users cannot take only the part of an upgrade that fits their needs — and they have to deal with the consequences.

More from

Passwords, passkeys and familiarity bias

5 min read - As passkey (passwordless authentication) adoption proceeds, misconceptions abound. There appears to be a widespread impression that passkeys may be more convenient and less secure than passwords. The reality is that they are both more secure and more convenient — possibly a first in cybersecurity.Most of us could be forgiven for not realizing passwordless authentication is more secure than passwords. Thinking back to the first couple of use cases I was exposed to — a phone operating system (OS) and a…

DOD establishes Office of the Assistant Secretary of Defense for Cyber Policy

2 min read - The federal government recently took a new step toward prioritizing cybersecurity and demonstrating its commitment to reducing risk. On March 20, 2024, the Pentagon formally established the new Office of the Assistant Secretary of Defense for Cyber Policy to supervise cyber policy for the Department of Defense. The next day, President Joe Biden announced Michael Sulmeyer as his nominee for the role.“In standing up this office, the Department is giving cyber the focus and attention that Congress intended,” said Acting…

Unpacking the NIST cybersecurity framework 2.0

4 min read - The NIST cybersecurity framework (CSF) helps organizations improve risk management using common language that focuses on business drivers to enhance cybersecurity.NIST CSF 1.0 was released in February 2014, and version 1.1 in April 2018. In February 2024, NIST released its newest CSF iteration: 2.0. The journey to CSF 2.0 began with a request for information (RFI) in February 2022. Over the next two years, NIST engaged the cybersecurity community through analysis, workshops, comments and draft revision to refine existing standards…

Topic updates

Get email updates and stay ahead of the latest threats to the security landscape, thought leadership and research.
Subscribe today