The latest Windows 10 update breaks Windows Media Player and Win32 applications in general



[ad_1]

Part of the Cydnidae group, these are a type of shield bug. These two are apparently about to produce a number of additional shield bugs.

Part of the Cydnidae group, these are a type of shield bug. These two are apparently about to produce a number of additional shield bugs.

jacinta lluch valero (jaclluch on Flickr)

The major data loss bug that interrupted the rollout of the Windows 10 October 2018 update, version 1809, can be fixed, but it turns out that there are many other strange problems with this version.

As Paul Thurrott noted, the update also breaks the search bar in Windows Media Player when reading "specific files".

It's the kind of bug that lets me scratch my head, wondering what has changed to break such a thing and why. The different and old stacks of Windows media are certainly complicated animals, but we do not know what the October 2018 update has even changed in this area. At least this time, it does not appear that the bug was reported before the actual release of 1809, although it is difficult to draw a definitive conclusion given the difficulty of finding anything either in the Feedback Hub bug report tool. Microsoft promises to fix the bug, but the schedule is vaguely unlimited: it will be "in a future release".

Another bug also appears in the "how did this happen" category: some Win32 programs can not be set as the default program for a given file type. For example, if you want certain files to always be open in Notepad, for example, you currently have no chance. A solution to this problem is promised by the end of the month. The definition of default program associations is something that has existed in Windows for about 20 years, so it is alarming that it is broken. These bugs will continue to draw attention to how Windows 10 is developed.

In addition, he continues to complain that Windows 10 version 1809 does not work with iCloud and that computers with the iCloud client are blacklisted to prevent them from receiving update 1809. It is not immediately known who is coming back the fault: it could be Microsoft, but it is also possible that Apple is to blame.

[ad_2]
Source link