CO-Release Build 22000.160 out to Dev and Beta Channel KB5005189

CrazyKats 19,415 Reputation points Volunteer Moderator
2021-08-19T17:00:15+00:00

Live in W.U.

Windows Insider program | Program announcements and registration | Communications and announcements

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.

0 comments

181 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Drew - 810 Reputation points
    2021-08-27T04:36:43+00:00

    Checked Store Updates & look what was there, WWEP. BUT it is (still) not visible in the Apps list.

    Cheers,
    Drew![](https://learn-attachment.microsoft.com/api/attachments/17175ab9-edde-4947-b334-549bac95bea1?platform=QnA

    Was this answer helpful?

    0 comments
  2. Anonymous
    2021-08-27T05:14:06+00:00

    Checked Store Updates & look what was there, WWEP. BUT it is (still) not visible in the Apps list.

    Image

    Cheers,
    Drew

    Same as I showed you yesterday, and if you click on open nothing happens...

    Image

    The only way you see that it is in the system is with the PowerShell command that lists all the names:

    Get-AppxPackage -allusers | Select Name, PackageFullName

    Get-AppxPackage MicrosoftWindows.Client.WebExperience -allusers | Select Name, PackageFullName

    Image

    Was this answer helpful?

    0 comments
  3. Drew - 810 Reputation points
    2021-08-27T06:14:46+00:00

    Yes, of course, I recall. It wasn't there when I looked/checked yesterday, found it there just today. Strange mysterious behaviour with this one. The thing updates, can be 'found' that it's 'somewhere' in the OS, yet look in Apps & it's not there. Where's Waldo❔🤔😂

    And speaking of strange, dig this... I put those command lines in myself and of course saw the results you show & mention using Powershell. BUT before that I stuck them in Windows Terminal Preview and had a slew of red text with Line 1 saying Access denied. AND then (just now) did the same in Windows Terminal and it worked.

    I'll stick with Windows Terminal for things henceforth, not Windows Terminal Preview. I never could manage to have Preview do all stuff it is supposed to be able to do, anyway.

    Now that I think about it, Preview shocked & surprised me when it did that with something else just recently. That time I when to Powershell, never tried (plain) Windows Terminal that time.

    Cheers,
    Drew![](https://learn-attachment.microsoft.com/api/attachments/93f23e84-b119-4053-87dd-30ad1f870fa8?platform=QnA

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Anonymous
    2021-08-27T16:24:27+00:00

    Drew,

    Worked fine with Windows Terminal Preview or Windows Terminal if I select Windows PowerShell in settings.

    It gets the red messages with the PowerShell App 7.1.4. See Below:

    Was this answer helpful?

    0 comments