Say Hello to Yet Another Windows 10 Issue… Microsoft May Just Have Broken File Associations with a Buggy Update

Author Photo
Nov 7
15Shares
Submit

Another week, another Windows 10 bug to report. The re-release of the October 2018 Update (or what should now be called a November Update) is yet to begin, but it appears Microsoft is dealing with a growing number of problems that are plaguing older versions, as well. The company is having a hard time dealing with Windows 10 bugs lately, and there is a fresh headache to add to that growing list of issues.

New reports suggest that the entire file association system is messed up after a cumulative update was sent out last month. Apparently, the operating doesn’t let you select certain applications as your default options. The issue was tested by the folks at HTG who report that after testing the issue on multiple machines running Windows 10 April 2018 Update, they can confirm that every PC has this problem.

one-netbook-one-mix-2-yoga-windows-10-pocket-pcRelated Tiny Windows 10 Pocket PC Complete With Backlit Keyboard and Yoga Moves Goes on Sale

“It affects some applications, but not others,” the publication reported. “For example, Windows 10 won’t let you make Adobe Photoshop or Notepad++ a default application for images or text files. But you can make other applications, like IrfanView, VLC, or Google Chrome, your defaults.”

Windows ignores your choice when you try setting Notepad++ as the default app for .txt files in Windows 10’s Settings app and chooses Notepad as the default.

The issue also occurs when you right-click to select “Open With” and then choose “Always Use This App” to make a third party app as your default choice. While the file will be opened in the chosen app at the time, the operating system will then forget to choose it as the default option.

Some users report that the bug is also present in Windows 10 1809

The bug appears on PCs running Windows 10 April 2018 Update Build 17134.345 (KB4462919) which was issued on October 9. It is unclear if the cumulative update sent out on October 24th addressed the problem. Some users report that they are also experiencing this issue on the latest Windows 10 October 2018 Update.

While we await the re-release of Windows 10 version 1809, it is still to be seen how Microsoft rethinks its development strategy to avoid such massive issues that have been reported in the past few weeks.

– Does Microsoft actually listen to its unpaid testing community?

Submit