This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Live in W.U.
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
Hi Sibro,
I know, it does not fail on a clean install, only on upgraded systems. It was that way from the beginning.
Sorry, I forgot. 🤦♂️
They fixed it with Dev though, it started working with a recent build even on a machine that was upgraded from Win 10.
Hi Sibro,
I know, it does not fail on a clean install, only on upgraded systems. It was that way from the beginning.
Sorry, I forgot. 🤦♂️
This bug is easy to reproduce on machines upgraded from 19043.1266 to 22000.194:
System shortcut is missing in Win + X.
Now the bug is also out on public build 22000.194. Just Upgraded 2 machines from 21H1 and got the same issue.
I just finished clean installing a VMware VM with official 22000.194 (ISO edition)
There's no bug, both Terminal & System are there
Hi Sibro,
I know, it does not fail on a clean install, only on upgraded systems. It was that way from the beginning.
This bug is easy to reproduce on machines upgraded from 19043.1266 to 22000.194:
System shortcut is missing in Win + X.
Now the bug is also out on public build 22000.194. Just Upgraded 2 machines from 21H1 and got the same issue.
I just finished clean installing a VMware VM with official 22000.194 (ISO edition)
There's no bug, both Terminal & System are there
This bug is easy to reproduce on machines upgraded from 19043.1266 to 22000.194:
System shortcut is missing in Win + X.
Now the bug is also out on public build 22000.194. Just Upgraded 2 machines from 21H1 and got the same issue.