Skip to content

Commit d5ebf27

Browse files
Merge pull request #19424 from madakeva/docs-editor/known-issues-1768578578
Update known-issues.md
2 parents c26680d + a81a775 commit d5ebf27

1 file changed

Lines changed: 11 additions & 1 deletion

File tree

autopilot/known-issues.md

Lines changed: 11 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Windows Autopilot known issues
33
description: Be informed about known issues that might occur during Windows Autopilot deployment. # RSS subscription is based on this description so don't change. If the description needs to change, update RSS URL in the Tip in the article.
4-
ms.date: 01/13/2026
4+
ms.date: 01/16/2026
55
ms.collection:
66
- M365-modern-desktop
77
- highpri
@@ -34,6 +34,16 @@ This article describes known issues that can often be resolved with configuratio
3434
3535
## Known issues
3636
37+
### Local Autopilot Reset can’t be triggered by local administrator when you deny access from network
38+
39+
**Date added:** January 16, 2026
40+
41+
When a device is configured with an Intune policy that sets **Deny access to this computer from the network** for the local account, the local Windows administrator account can't start a local Windows Autopilot Reset.
42+
43+
This issue affects scenarios where administrators rely on the local administrator account to trigger local Autopilot Reset on a device (for example, from the Windows sign-in screen or after local sign-in). As a workaround, remove the **Deny access to this computer from the network** setting for the local account, or exclude devices that require local Autopilot Reset from this policy. After the device syncs the updated policy, local Autopilot Reset works.
44+
45+
This issue is under investigation.
46+
3747
### Devices don't get quality updates during Microsoft Entra hybrid joined deployments
3848
3949
Date added: *January 13, 2026*

0 commit comments

Comments
 (0)