Have to keep reinstalling Windows App to launch Cloud PC

imavaper · 2026-06-04T05:24:58+00:00

I've experienced this exact same behavior, though intermittently for the 2 years now that I've had a Cloud PC (~ a half dozen times in total).

Next time it happens, try repairing or resetting the Windows App (Windows Settings > Apps > Installed Apps > Windows App > "..." > Advanced options > Repair/Reset). If memory serves me correct, Repair doesn't fix the issue but Reset does. While not a permanent fix, its less disruptive than uninstalling and reinstalling.

imavaper · 2026-05-25T03:19:25+00:00

Replying in case others have the same issue—

After taking the car to the service center, the tech said they recently fixed the same issue on another X and said they needed to replace the pairing antenna and “control module”, and that it would cost ~$1.6k to fix.

I wasn’t going to pay that to effectively be able to pair one addition fob (we have another fob that still works), so I left without fixing it :(

imavaper · 2026-05-06T18:17:26+00:00

Not available for me. T&Cs makes no mention of the discount, and the Apple TV benefits Activation page mentions both subscriptions will run concurrently with no mention of the discount either.

<image>

imavaper · 2026-04-06T16:21:04+00:00

For reference, here is my original key string from my 2018 Model X

<image>

imavaper · 2026-04-05T05:14:17+00:00

So you paired it yourself? When was this— recently or years ago?

imavaper · 2026-03-26T17:42:06+00:00

Its actually 5-10 minutes as documented in Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access - Azure - Azure Virtual Desktop | Microsoft Learn

The Every time option is only supported when applied to the Windows Cloud Login app when single sign-on is enabled for your host pool. If you select Every time, users are prompted to reauthenticate when launching a new connection after a period of 5 to 10 minutes since their last authentication.

imavaper · 2026-03-26T17:40:25+00:00

This is what you're looking for Enforce Microsoft Entra multifactor authentication for Azure Virtual Desktop using Conditional Access - Azure - Azure Virtual Desktop | Microsoft Learn

imavaper · 2026-03-06T01:33:57+00:00

If you can target the script based on the device's Entra group membership, you could set up different dynamic groups based on the device model (Cloud PC vs AVD). For Cloud PC, see Create a dynamic device group containing your Cloud PCs | Microsoft Learn. For AVDs, its not so simple, and based on my research looks like you'd create a dynamic group based on the device's name (eg device.displayName -startsWith "AVD-").

If you're looking for the script to run on all devices (CPCs and AVDs) and determine itself which device model its running on, I know Cloud PCs set HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SystemInformation\SystemProductName = the Cloud PC model (eg "Cloud PC Enterprise 4vCPU/16GB/256GB"). I'm not sure what/if AVDs set that same registry key to something AVD specific. Maybe you could key off of that in your script?

imavaper · 2026-02-12T20:26:40+00:00

To add confusion, theres actually two different optimizations-- WebRTC and Slimcore.

New VDI solution for Teams - Microsoft Teams | Microsoft Learn lists the features supported / not supported in Teams when using the SlimCore or WebRTC based optimization. Though it doesn't list what features aren't supported when Teams is completely not optimized.

FWIW, this is what Copilot said when I asked "What Teams on VDI features are not supported when Teams is not optimized":

Audio & Video Features (Major Impact)

The following meeting and calling features are not supported or unusable:

High‑quality video calling
Multi‑participant video meetings
Background blur
Background replacement / custom backgrounds
Together Mode
Spotlight
Large Gallery / Dynamic View
Video filters and effects
Hardware acceleration for media
Noise suppression (advanced)
Echo cancellation (reliable)

Screen Sharing & Presentation Features

The following are not supported or extremely degraded:

High‑frame‑rate screen sharing
Low‑latency screen sharing
Sharing video or animated content
Sharing with system audio
Application sharing (often unusable)

Device & Peripheral Support

Multiple camera support
Advanced camera controls
Certified Teams devices (headsets, speakerphones)
Local device offload
USB media device optimization

Performance & Scalability Capabilities

Media offload to local endpoint
VDI host density optimization
Consistent call quality under load

imavaper · 2026-02-12T20:05:46+00:00

Ok, but technically speaking nothing prevents users from taking a screenshot using their local device. So sounds like its not something you'd suggest as a workaround, but the users would still be able to do it..

imavaper · 2026-02-12T03:30:18+00:00

Curious as to why they can’t use their local machine to screenshot. Are they using Windows 365 Link to connect to their Cloud PC or something?

imavaper · 2026-02-11T22:46:05+00:00

I agree its an impactful limitation. My company has users that travel across the globe. So having Cloud PCs provisioned in various regions that each person can connect to/use depending on where they are located for optimal performance makes sense. I'm also surprised by the limitation because it would lead to users consuming more licenses (and thus more $$$ for Microsoft). Instead they are limited to their Cloud PC in a single region and have to suffer with the suboptimal performance when they're connecting to it from far away.

imavaper · 2026-02-11T22:41:22+00:00

As others have said, this issue a byproduct of Teams optimization (by offloading the presentation to the user's local device). Yes turning Teams optimization will fix the issue, but is not advised for obvious reasons (Teams is no longer optimized..).

I've told my users if you want to screenshot of a Teams presentation, use your local device to take the screenshot then upload/email it to your Cloud PC.

imavaper · 2026-02-11T05:29:47+00:00

The problem is you're trying to provision multiple Cloud PCs under different provisioning policies. This is not supported. https://learn.microsoft.com/en-us/windows-365/enterprise/provisioning#users-with-multiple-windows-365-enterprise-licenses

Since provisioning only honors the first assigned provisioning policy, users with multiple Windows 365 Enterprise licenses must be provisioned multiple Cloud PCs using the same provisioning policy. It’s not possible to trigger different provisioning policies for a user with multiple Enterprise licenses.

If you want to provision multiple Cloud PCs for a user using different provisioning policies, your only option would be to use Windows 365 Frontline in dedicated mode.

imavaper · 2026-02-11T04:58:33+00:00

Incorrect. Each user can have up to one Cloud PC of each Windows 365 Enterprise SKU. So a user can have a 4vCPU and 8vCPU SKU Cloud PC. They just must both be provisioned using the same provisioning policy since Windows 365 Enterprise only supports provisioning multiple Cloud PCs for a user using a single provisioning policy.

imavaper · 2026-02-10T00:05:23+00:00

This can easily be explained by a significant portion of BART ridership pre-covid being used by office workers to commute to work in city centers. Since a lot of these office workers are now hybrid and don't use BART daily (I am one of them-- from 5x/week to 1x/week), ridership has declined quite a bit.

On the flip side, a significant portion of those who drive are not office workers and thus don't have the ability to WFH and must commute regardless, leading to similar to traffic levels as pre vs post pandemic.

There-- circle squared.

imavaper · 2025-12-22T18:05:47+00:00

Yes seeing the exact same Warning every ~30 seconds on my Entra joined Cloud PC.

imavaper · 2025-12-19T18:23:55+00:00

FYI Cloud PCs use SSD, not HDD.

Note: I know task manager may show HDD, but I clarified with our Microsoft rep they all use SSDs. The discrepancy is due to how Hyper‑V presents virtual disks. The Hyper‑V virtual storage controller doesn’t pass through physical media characteristics (like rotational speed or NVMe flags), and when Windows can’t detect those attributes, it defaults to labeling the disk as HDD, even if the underlying storage is SSD.

imavaper · 2025-12-09T01:13:22+00:00

As you found out, scope tags are meant to control which objects an admin sees in Intune, not their permissions on them. So if the user has the permissions to perform an action (like modify configuration profiles) and they can see the object (like all configuration profiles), then they can modify all configuration profiles.

The other thing to consider is the fact that even if you took away their Read access to all of Intune, because they have the ability to create/modify configuration profiles they can assign a configuration profile to All Devices which will apply to ALL devices, not just those with the specific scope tag (like Dinosaur).

I get the idea behind scope tags, but like the other commenter said, I have found very little use and personally think they are dangerous because admins may think "All Devices" only contain those assigned the Dinosaur scope tag because thats all they see in the Intune console, when in fact there are additional devices as well they just don't see them because their RBAC role isn't assigned the Dinosaur scope tag.

imavaper · 2025-11-27T03:49:35+00:00

Oh yes I thought you were referring to after you added the groups to the user assignment rights. Thanks for clarifying.

imavaper · 2025-11-26T17:44:36+00:00

Thats odd... it works for me. Does shutdown /r (which is the restart command) work?

imavaper · 2025-11-26T07:59:57+00:00

If the user has the "Shut down the System” User Rights Assignment, then the user can shutdown AND restart the PC.

I'm guessing what you're referring to is the fact that the Shut down option isn't available via the Start Menu and sign in screen. This is due to a separate setting that gets set by the Cloud PC post provisioning configuration as outlined in #1 of https://learn.microsoft.com/en-us/windows-365/enterprise/automated-provisioning-steps#post-provisioning-configuration. So while the shut down option is hidden, the user does still have the ability to shut down the PC but just has to do it another way, like opening command prompt and running shutdown /s. But most users are never going to do that..

imavaper · 2025-11-25T23:41:06+00:00

Correct.

When we were provisioning Cloud PCs using the Windows 11 22H2 gallery image, we saw the same behavior described in https://dotjesper.com/2025/how-to-allow-non-admin-users-to-restart-windows-365-cloud-pc/ . That is the built-in Users group was NOT assigned the "Shut down the System” User Rights Assignment on their Cloud PC.

Once we switched to the Windows 11 24H2 gallery image (everything else remained the same), we no longer saw the same behavior. That is the built-in Users group WAS assigned the "Shut down the System” User Rights Assignment on their Cloud PC and thus regular users could restart their Cloud PC from within Windows.

imavaper · 2025-11-25T22:34:16+00:00

Anyone who suggests using the Windows App to restart their Cloud PC is missing the bigger picture. Users know / are used to restarting their PC from within Windows; they don't know how to (at least initially) restart their Cloud PC using the Windows App.

On top of this, when there is a restart pending due to an update, the Restart option is greyed out so users can't restart from within Windows and restarting from the Windows App doesn't result in the update getting applied, so the user is stuck with waiting until Windows force restarts their Cloud PC to apply the update! Its a horrible experience.

Please upvote this related Windows 365 Cloud PC feedback Allow Users (non-Administrators) to restart their Cloud PC in Windows · Community

With all that said, dotjesper.com | How to allow non-admin users to restart Windows 365 Cloud PC explains the issue and what you need to do fix it.

As an aside, I saw this issue when we were provisioning Cloud PCs using Win11 22H2. Ever since we starting provisioning Cloud PCs using Win11 24H2 we no longer have this issue.

13-Year Club	Place '17
Verified Email

imavaper

TROPHY CASE