Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update troubleshoot-windows-365-boot.md #4596

Merged
merged 2 commits into from
Sep 16, 2024
Merged

Update troubleshoot-windows-365-boot.md #4596

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5709b58
Update troubleshoot-windows-365-boot.md
kev-out Jul 28, 2024
3b48224
Update troubleshoot-windows-365-boot.md
ErikjeMS Sep 16, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 8 additions & 2 deletions windows-365/enterprise/troubleshoot-windows-365-boot.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,8 +40,14 @@ If the user can't access the Cloud PC from the Windows 365 Boot physical device,
1. Check to see if you can sign in to the Cloud PC from either:
- The browser at windows365.microsoft.com.
- The Windows 365 app on another (non-Windows 365 Boot) device.
2. If you can log into the Cloud PC from either method, then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md).
3. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device.
2. If a user has more than one Cloud PC, make sure they have selected a default Cloud PC to use each time they sign in. To set this default:
- Navigate to https://windows365.microsoft.com.
- In the card for the Cloud PC you want to set as default, select the ellipses (...) > Settings.
- In the **Integrated experiences** tab, under **Boot to this Cloud PC**, select **Connect while signed into device**.
- Select **Save**.
3. If you can sign into the Cloud PC from the app or web, and a default Cloud PC has been set, then there's an issue with the Windows 365 Boot physical device. In this case, confirm that the physical device is correctly configured and has the requisite software versions. For more information, see [Windows 365 Boot physical device requirements](windows-365-boot-physical-device-requirements.md).
4. Admins can try to manually click on **Device sync** to get the policies delivered faster on the device. Users can try to restart the device.


## Physical device registry key configuration

Expand Down