Microsoft admits recent Windows 10 updates messed up the taskbar for some users – but a fix is coming

Microsoft has acknowledged that there’s a bug introduced by recent Windows 10 updates that can break a piece of taskbar functionality – but the good news is a fix is in the works.

The problem is evident for some Windows 10 users when right clicking on a pinned app on the taskbar, when instead of seeing the usual context-sensitive jump list menu – that allows access to common features, like opening recent files – they get something entirely useless.

What Windows 10 produces instead is the ‘Open with…’ menu (that facilitates choosing which app you want to open a file with). That’s not only unhelpful but also confusing, frankly, though Windows Latest, which spotted this, notes that the bug only affects a small set of Windows 10 users – and it only happens with some apps, not all of them.

So, this isn’t something you’re likely to encounter, but if you do, it’s a rather annoying issue. Furthermore, it affects a wide range of recent updates for Windows 10 – not just the latest June cumulative update, but also the May cumulative update (and that month’s optional update), and the optional update for April too.

Windows Latest reports that Microsoft has pinpointed a fix and the company has indicated that the resolution will be included in a future update for Window 10 22H2.


Analysis: A quick fix, with any luck

Hopefully, with the fix identified, implementing it shouldn’t be a difficult task and we might see the cure in next month’s cumulative update. Indeed, if that’s the case, we’ll actually get it before the July update, as it will be in the optional update for June, which is a preview of the former. That should be here in not much more than a week, in fact – though there’s no guarantee the fix won’t take longer, of course.

In case you missed it, what’s interesting with Windows 10 is that Microsoft is not just fixing and patching the OS, but is actively developing it again, adding new features and recently resurrecting the Beta channel to test them. That’s despite the End of Life date for Windows 10 coming ever closer – the OS runs out of support in October 2025, in case you’d forgotten. So it won’t be that long before you need to start exploring the options you have in that regard.

You might also like…

TechRadar – All the latest technology news

Read More

Microsoft finally exorcises digital poltergeist that messed with desktop icons and stopped some users from getting Windows 11 23H2

Remember that really strange bug where Windows 11 caused havoc with multi-monitor setups, shuffling desktop icons around, or even moving them onto different screens?

Well, the good news is Microsoft has now fixed this (but the not-so-great news is that it isn’t remedied for Windows 10 users, not yet – we’ll come back to that shortly).

Affected Windows 11 PCs were seeing icons being moved about on the desktop, or seemingly randomly shifted to their other monitors in a highly confusing fashion. Rather like the digital equivalent of a poltergeist possessing your system and causing mischief.

The problem was first spotted in Windows 11 back in November 2023, with the root cause being Copilot – and this led to Microsoft putting a block (a so-called compatibility hold) on rolling out the AI assistant to those with multiple monitors attached to their PC. (And furthermore, there was a block on the Windows 11 23H2 upgrade, for those who hadn’t yet migrated to that version – as it introduces Copilot).

However, all that’s now lifted as the issue has been resolved, as Neowin spotted.

Microsoft updated its known issues with Windows 23H2 (in the release health dashboard) to say that: “This issue was resolved on the service-side for Windows 11, version 23H2 and Windows 11, version 22H2 on devices with updates released January 9, 2024 or later. Non-managed consumer Windows devices with no other compatibility hold should now have Copilot for Windows available. The safeguard hold has been removed as of February 7, 2024.”


Analysis: Ghost in the machine

A service-side tweak means that Microsoft has applied the fix on its end, so there’s no actual update or tinkering that needs to happen with your Windows 11 PC. The fix is just there, and the compatibility hold on Windows 11 23H2 is lifted, so those who’ve been stuck without 23H2 or Copilot should now be able to upgrade just fine.

However, Microsoft observes that it may take up to 48 hours for 23H2 to be offered to your computer. Restarting the PC and manually checking for updates may help to prompt Windows to discover the upgrade.

This is true for Windows 11 PCs previously blocked from 23H2, and also Windows 10 users who wanted to upgrade their device to Windows 11 23H2. The twist here, though, is this icon-flinging bug isn’t actually resolved with Windows 10, if you want to stick with the older OS rather than migrate to Windows 11.

If you recall, Windows 10 users were also affected, and blocked from getting Copilot (when it was subsequently rolled out to them). And sadly, that’s still the case, so those with multiple monitors running Windows 10 still won’t get the AI assistant. With the problem solved in Windows 11, though, presumably it won’t be long before it’s also cured for those staying on Windows 10.

Microsoft updated the Windows 10 release health dashboard to note that: “We are working on a resolution for this issue on Windows 10, version 22H2 and will provide an update in an upcoming release.”

You might also like…

TechRadar – All the latest technology news

Read More

New Windows 11 update fixes a seriously frustrating bug that messed with AMD GPUs

A bug that’s been frustrating Windows 11 users with AMD graphics cards (and CPUs to an extent) has been fixed in the latest update for Microsoft’s OS – or mostly fixed, anyway, going by reports.

This glitch was brought in with the Moment 4 update (it was first seen in the preview of that upgrade), and it messed with AMD profile settings. Every time affected users restarted their PC, those GPU settings (and reportedly CPU settings too, in some instances, like overclocking) went back to their defaults.

The good news is that the Windows 11 update for November (which began rolling out last week) cured this issue, albeit with some caveats.

As Windows Latest reports, the bug has been squashed according to its own testing. The tech site has also been talking to a selection of users hit by the bug and the majority said that this new patch from Microsoft fixed things – however, a few observed that their profile was still being reset.

It appears there are still minor gremlins kicking about, perhaps, though it should be noted that for the fix to work, as well as the November update for Windows 11, you also need to be running AMD’s Adrenalin graphics driver version 23.10.2.

Another slight caveat, too: the November update that resolves this issue has some vexing problems itself.


Analysis: A thornier problem for some?

This is a nasty bug. Having your settings reset and having to redo any customization from scratch after every single PC restart is going to get very annoying, very quickly. Especially if you’ve done a lot of tweaking on your AMD system.

Seeing the fix arrive is great news, although there’s the slight catch of apparently not everyone getting the benefit. Windows Latest doesn’t make it clear if those who found the bug still present after the latest Windows 11 update were using the mentioned version of AMD’s GPU driver (v23.10.2), but presumably they were, as the site would’ve surely clarified that if not.

The tech site suggests that those continuing to be affected may be suffering a profile reset from another cause other than Windows 11 updates.

Whatever wrinkles are left in the solution, if any, Microsoft will hopefully iron them out quickly – although the software giant hasn’t actually confirmed the presence of this fix in the new update.

You might also like

TechRadar – All the latest technology news

Read More